# CS-50: Accessible account recovery

Category: Inclusion & everyday access
Level: Advanced
Suggested duration: 4–6 weeks

Original UXCharan practice scenario. Validate assumptions; do not present it as a commissioned client project.

## Problem
A hypothetical service depends on a single recovery channel that some users no longer have. Explore an understandable recovery journey with clear status and support handoff, using mocked verification rather than designing security policy.

## People to learn from
People recovering a fictional account without their usual device

## Core scope
- Identify recovery options
- follow a route
- track support

## Research questions
- How do users interpret recovery requirements?
- Where do they need reassurance or help?

## Edge cases
- Lost device
- unavailable channel
- attempt limit

## Specific artefact
A recovery journey and accessible form states

## Evaluation question
Can users identify a legitimate next step without exposing unnecessary personal data?

## Work to share
Problem and role; anonymised evidence; alternatives and rationale; task flow; prototype; accessibility considerations; testing findings; revisions and honest limitations.

## Request feedback
Share a viewable Figma, document or portfolio link with Saicharan on WhatsApp: https://wa.me/917093809350
Include CS-50, your name, project stage and your main feedback question. Confirm review scope, timing and any fee directly.

## Methods
- Research planning: https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service
- Research consent: https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research
- Design exploration: https://www.designcouncil.org.uk/resources/the-double-diamond/
- Usability testing: https://www.nngroup.com/articles/usability-testing-101/
- Accessible forms: https://www.w3.org/WAI/tutorials/forms/
- Portfolio storytelling: https://www.nngroup.com/articles/ux-design-portfolios/