Robust · Level AA · Introduced in WCAG 2.1
WCAG 4.1.3: Status Messages
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
In markup-based content, status messages must have roles or properties that allow assistive technology to announce them without moving focus. Users need to hear results, progress and errors while continuing their task.
A practical example
A filter changes a product list from 40 items to 6. Keep focus in the filter and update a concise status region to “6 products found,” rather than making the entire results grid a live region.
How to check it
- Identify messages about results, progress, waiting states and errors that do not receive focus.
- Inspect the message's semantic role or live-region properties and trigger a real update.
- With a screen reader, verify a timely, concise announcement while focus stays where the user expects.
What can be missed
Not every content update is a status message. Avoid assertive announcements for routine updates and prevent repeated or excessively long announcements that interrupt the task.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.