- Success Criterion 4.1.3
- Conformance level AA
Character Counter That Updates Only Visually While Typing
4.1.3 — Status Messages
Scenario
Setting
A ticket marketplace's seat-selection map
What’s wrong
Character counters/quota warnings updating visually only.
Example
Consider a ticket marketplace's seat-selection map: character counters/quota warnings updating visually only.
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. The practical effect on a ticket marketplace's seat-selection map: they can't complete the task without extra help.
How to test
Watch a character counter or quota warning update while typing, with a screen reader running: if there's no announcement as it changes, 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 ticket marketplace's seat-selection map 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