- Success Criterion 4.1.3
- Conformance level AA
Single-Page App Route Change With No Announcement at All
4.1.3 — Status Messages
Scenario
Setting
A professional networking site's profile editor
What’s wrong
single-page app route/page change producing no announcement and no focus-management signal that the view changed.
Example
On a professional networking site's profile editor: single-page app route/page change producing no announcement and no focus-management signal that the view changed.
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. The practical effect on a professional networking site's profile editor: they have to work around the barrier just to continue.
How to test
Navigate to a new view in a single-page app with a screen reader running: if there's no announcement and no focus-management signal that the page changed, 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
That one change on a professional networking site's profile editor means they move past the barrier without workarounds.
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