- Level
- AA
- Since
- WCAG 2.1
4.1.3 Status Messages
Messages that report a result, a wait, progress or an error without moving focus must be marked up so that a screen reader can announce them.
/ What it requires
A status message is a change in content that is not a change of context and that tells the user about the success or result of an action, the waiting state of an application, the progress of a process, or the existence of errors. Sighted users notice "18 results", "Saved" or "5 errors on page" appear at the edge of their view. A screen reader user hears nothing unless the message is exposed through a role or property, such as role="status", role="alert" or an aria-live region, so that assistive technology can present it without the message receiving focus.
The scope is narrow. Content that arrives with a change of context, such as an error in a dialog that takes focus, is already announced and is out of scope. So is content shown or hidden by a component the user operates, such as an accordion or a tab, which 4.1.2 covers, and new content that is not a status, such as the list of search results itself or extra questions added to a form. The criterion does not ask authors to create messages, only to expose the ones they show. W3C notes that other programmatic means, including direct calls to accessibility APIs, also count.
/ How pages fail it
- A search updates in place and writes "No results returned" into a plain div, so a screen reader user does not hear it.
- A toast saying "Saved" is appended to the end of the body with no role="status" or aria-live and fades out after three seconds.
- Adding an item to the cart changes a badge from 0 to 1 inside a span that is not a live region.
- An inline validation message appears above a field when the field is left, outside any live region.
- The script that shows a message creates the live region at the same moment it writes the text into it, so some browser and screen reader combinations announce nothing.
/ How to check it yourself
- Trigger each dynamic message: search and filters, add to cart, save, a form submitted with and without errors, a file upload, any loading indicator.
- Note whether focus moves. If focus stays where it was and text appears, the text is a status message.
- Inspect the element that holds the message in the developer tools. It or an ancestor needs role="status", role="alert", role="log", aria-live="polite" or "assertive", or an output element, and the region should be in the DOM before the message is written into it.
- Repeat the action with NVDA in Firefox or Chrome, or with VoiceOver on a Mac, and listen for the message without moving focus.
- Check that what is announced makes sense on its own, for example "3 items in cart" rather than "3".
/ How to fix it
- Put an empty container with role="status" into the page when it loads, and write the message into it when the result is ready.
- Use role="alert" only for errors and warnings that matter now, because it interrupts. Use role="status", which is polite, for results and confirmations.
- For a cart counter or a result count, put the whole phrase into the region, or set aria-atomic="true" on it, so the screen reader says "3 items" and not "3".
- For a running series of updates, such as chat messages or the steps of a long process, use role="log".
- In a component framework, render one live region in the layout and send messages to it, instead of mounting a new region together with each toast.
/ What our scanner checks
One check is filed here, live-region-missing, and it runs only in our browser extension, never in the anonymous site scan. With Watch page on, a MutationObserver records element nodes added to the page; a visible one with up to 400 characters of text, outside any aria-live, status, alert or log region, that looks like a message by its class, its id or its brevity, is reported. The form drill does the same for messages that become visible when a field is left. Text changed inside an existing element goes unseen, any aria-live value counts as announced, including "off", and nothing listens to what a screen reader says.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Do search results need a live region?
The results do not, but the status around them does. W3C says the list of results is not a status message, while a short text such as "18 results returned" or "No results returned" is one when it appears without taking focus. That text belongs in an element with role="status".
Should I use role="alert" or role="status"?
role="status" for results, confirmations and progress, which a screen reader announces once it has finished what it is saying. role="alert" for errors and warnings that matter now, because it interrupts. W3C names role="alert" or aria-live="assertive" on content that is not important and time-sensitive as a common mistake.
Is a message in a modal dialog a status message?
No. A dialog that takes focus is a change of context, and the move of focus already makes a screen reader announce it, so 4.1.3 does not apply. The criterion is level AA and was added in WCAG 2.1, so an audit against WCAG 2.0 does not include it.
