- Success Criterion 4.1.3
- Conformance level AA
Multi-Step Progress Update Never Exposed to Screen Readers
4.1.3 — Status Messages
Scenario
Setting
A coworking-space booking app
What’s wrong
Multi-step progress ("Step 2 of 4 complete") status changes not exposed.
Example
This shows up on a coworking-space booking app: multi-step progress ("Step 2 of 4 complete") status changes not exposed.
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. On a coworking-space booking app, this barrier means they are excluded from part of the experience.
How to test
Advance a multi-step process ('Step 2 of 4 complete') with a screen reader running: if the step change isn't announced, it fails.
How to fix
The status text must be wired as a live region (code that makes screen readers announce updates)/status role so screen readers announce it automatically without moving focus.
Outcome
Corrected, a coworking-space booking app now lets a visitor complete the task without extra help.
Who is affected
Screen-reader users who need spoken confirmation of saves, errors, and results.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Status Update Shown Visually but Never Wired for Screen Readers
- Cart Confirmation Toast With No Live Region Announcement
- Search Result Count That Updates Silently on Every Filter
- Autosave ‘Saved’ Indicator With No Live Announcement
- Loading Spinner With No Programmatic Busy or Status State
- Error Toast With No Alert Role and No Focus Movement