- Success Criterion 4.1.3
- Conformance level AA
Autosave ‘Saved’ Indicator With No Live Announcement
4.1.3 — Status Messages
Scenario
Setting
A subscription box service's account settings
What’s wrong
Form "Saved" / autosave indicators with no live announcement.
Example
Here's what happens on a subscription box service's account settings: form "Saved" / autosave indicators with no live announcement.
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. On a subscription box service's account settings, this barrier means they hit a dead end with no way forward.
How to test
Trigger an autosave with a screen reader running: if the 'Saved' indicator updates silently with no announcement, 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 subscription box service's account settings 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
- 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