- Success Criterion 4.1.3
- Conformance level AA
Chat Typing Indicator With No Programmatic Status Update
4.1.3 — Status Messages
Scenario
Setting
A photo-sharing app's upload screen
What’s wrong
Chat "typing…" or new-message indicators without programmatic status (where they don't take focus).
Example
A QA pass on a photo-sharing app's upload screen turns this up: chat "typing…" or new-message indicators without programmatic status (where they don't take focus).
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. On a photo-sharing app's upload screen, that means they have to work around the barrier just to continue.
How to test
Trigger a chat 'typing…' indicator or new-message notification with a screen reader running: if it's not announced and doesn't take focus either, 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
With the fix in place on a photo-sharing app's upload screen, they get the same outcome as everyone else.
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