What WCAG 4.1.3 Requires
Important status messages, such as a search result count, a form success message, or a cart update, must be announced to screen reader users without requiring their focus to move, usually via an ARIA live region.
New to this criterion? Read our plain-English guide, WCAG 4.1.3 Status Messages Explained in Plain English, with examples and code.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Trigger a status update (submit a search, add an item to a cart) with a screen reader running and confirm the change is announced automatically.
Common Failures
- A "3 results found" message updates visually with no aria-live region, so screen reader users never hear it.
- A success toast notification appears and disappears with no announcement at all.
Related Criteria in Compatible
WCAG 4.1.3 Questions
What does WCAG 4.1.3 require?
Important status messages, such as a search result count, a form success message, or a cart update, must be announced to screen reader users without requiring their focus to move, usually via an ARIA live region.
Can AccessBell test WCAG 4.1.3 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 4.1.3?
Level AA, added in WCAG 2.1. Level AA is required to meet WCAG AA, the level referenced by the ADA, Section 508 and most accessibility laws.
Sources
- W3C: Understanding 4.1.3 Status Messages (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.