- Success Criterion 4.1.3
- Conformance level AA
- W3C reference F103
Status Update Shown Visually but Never Wired for Screen Readers
4.1.3 — Status Messages
Scenario
Setting
A news outlet's article page
What’s wrong
Status updates ('Saved', 'Loading', '5 results') appear on screen but aren't wired as status messages — screen readers stay silent.
Example
A tester reviewing a news outlet's article page finds this: status updates ('Saved', 'Loading', '5 results') appear on screen but aren't wired as status messages — screen readers stay silent.
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. On a news outlet's article page specifically, they can't complete the task without extra help.
How to test
Trigger a status update (save, search, error) and check DevTools: if there's no role="status"/aria-live region wired to it, it won't be announced automatically.
How to fix
Wrap the status area in role="status" (code that makes updates announced)/aria-live (code that makes screen readers announce updates) so updates are announced automatically.
Outcome
Fixed, a visitor to a news outlet's article page can 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)
- Technique Related technique (opens in a new tab)
Related scenarios
- 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
- Live Region Whose Content Loads Before It’s Ready to Announce