UX/UI design / DIJION
Reviewing a mobile flow with a screen reader: from labels to tasks
A task-based review of accessible names, navigation order and announcements that distinguishes manual checks from automated coverage.
Labels on every icon do not prove that a flow works with a screen reader. Focus order can be confusing, an error may go unheard or closing a modal may lose context. Follow an illustrative editing task from entry to saved result. Assess whether the information needed for decisions is available, rather than reading isolated labels alone.
Write down the task and starting state
Choose a concrete task such as changing a name, recovering from validation and saving instead of testing accessibility in general. Record account, data and initial screen state. Android’s accessibility testing guidance includes automated and manual approaches. A tool reporting no issue does not establish that the whole task is completable with a screen reader.
Make names, roles and states work together
Scroll the table horizontally to see all columns.
| Element | Information needed | Warning sign |
|---|---|---|
| Icon button | Its action | Only an asset filename is announced |
| Expandable selector | Selected value and state | Missing expanded/collapsed state |
| Invalid field | Problem and recovery | Error disconnected from its field |
Listen to order independently of visual position
Information presented in one visual row may be separated widely in screen-reader navigation. Make a card’s title, status and action understandable together. Inspect unnecessary stops on decorative content. Record how much navigation a large list or repeated menu requires before reaching the main task; being technically readable is not the entire experience.
Communicate changes without unnecessarily stealing focus
Listen to what happens when saving starts, an error arrives and the operation completes. Moving focus to the beginning for every change can lose the working position. A genuine context change such as opening a dialog may require focus management. Record announcement timing, repetition and relationship to the task as separate observations.
Leave a reproducible finding
- Record device, operating system, app and screen-reader versions.
- Complete the task using screen-reader navigation.
- Separate expected information from the actual announcement.
- After a fix, repeat error, dialog and success paths.
This is a manual task-review plan; one session is not a conformance certification. The outcome should identify specific lost information or blocked actions that a team can investigate and fix.