Skip to content

[UI/UX Design] Design a 2FA recovery-email fallback confirmation flow #511

Description

@thlpkee20-wq

Description

When a user loses their 2FA device, a recovery-email fallback must be secure yet accessible. Design a flow that verifies the recovery email, throttles requests, and clearly communicates progress and cooldowns.

Requirements and context

  • Must be accessible (WCAG 2.1 AA), responsive, and documented in the design system
  • Should be consistent with existing patterns and easy to review
  • Relevant code: src/components/TwoFactorSetup.tsx
  • Cooldown must show a countdown in plain language

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b uiux/2fa-recovery-email-flow
  • Implement changes
    • Design the request-code screen and code-entry screen
    • Specify throttling and cooldown UI
    • Draft the "still can't access" support link
  • Validate accessibility and responsive assumptions

Test and commit

  • Run checks
    • npm run lint and component/visual tests
  • Cover edge cases
    • Repeated requests, expired codes, screen reader flow
  • Include screenshots/before-after and accessibility (axe) notes

Example commit message

design: 2fa recovery email flow

Guidelines

  • Minimum 95 percent test coverage
  • Clear documentation
  • Timeframe: 96 hours

Metadata

Metadata

Assignees

Labels

Stellar WaveStellar Wave issue batch

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions