November 11, 2026
Status messages and aria-live: applying WCAG 4.1.3
A status message is the short piece of text that appears after an action without focus moving: "18 results returned", "Your form was successfully submitted", "Invalid entry". Most sighted users notice it out of the corner of their eye; a blind person using a screen reader does not, unless something exposes it. WCAG Success Criterion 4.1.3 Status Messages (Level AA) therefore requires that these messages can be programmatically determined through role or properties, so that assistive technologies can present them to the user without the message receiving focus. In practice, the W3C's sufficient techniques rely on ARIA roles such as role="status", role="alert" or role="log", and on live regions (aria-live), while the criterion more broadly covers programmatically determinable means. This article explains what is and is not a status message, which role fits each situation described by the W3C, how to handle the tricky cases, and which mistakes to avoid.
What counts as a status message under SC 4.1.3?
The wording of the criterion is precise: in content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
"Status message" is a defined term in WCAG. Two conditions must both be met, listed below: the kind of information conveyed, and the absence of a change of context.
The W3C states a twofold goal: make users aware of important changes in content that are not given focus, and do so without unnecessarily interrupting their work. The intended beneficiaries are blind and low vision users of assistive technologies with screen reader capabilities. As an additional benefit, assistive technologies for users with cognitive disabilities may offer an alternative way of indicating these messages, or even delay or suppress them, according to the user's preferences.
The W3C also notes that although the criterion mentions roles or properties, it applies more generally to any programmatically determinable way of conveying status messages, including direct access to accessibility APIs that result in assistive technology alerts or announcements.
- the message tells the user about the success or results of an action, the waiting state of an application, the progress of a process, or the existence of errors;
- the message is not delivered via a change of context (for example opening a new window, moving focus, going to a new page or significantly re-arranging the page content).
When must a status message be announced without moving focus?
The criterion covers situations where new content is added to the page without changing the user's context. The boundary matters: not every piece of added content is a status message. The list of search results itself is not one and is not covered. However, brief messages about the state of the search, such as "Searching...", "18 results returned" or "No results returned", are status messages if they do not take focus or cause a page refresh.
Here are the status message examples given by the W3C:
- after the user presses a Search button, the text "5 results returned" appears near the top of the results area; it is given an appropriate role and the screen reader announces "Five results returned";
- after an Add to Shopping Cart action, the area near the cart icon shows "5 items" and the screen reader announces "Five items" or "Shopping cart, five items";
- after incorrect text is entered in a Postal Code field, "Invalid entry" appears above the input and is announced;
- a 'busy' icon appears after a process starts and the screen reader announces "application busy";
- a dynamic progress bar shows the status of an upgrade and the screen reader gives intermittent progress announcements;
- after a form is submitted, "Your form was successfully submitted." is added to the form, or "5 errors on page" if some data is in the wrong format;
- in a photo app, a popup reading "Saved in 'Wedding' album" appears after a photo is added.
What is not a status message
The W3C also lists cases that do not meet the definition of a status message and therefore need no additional author action under 4.1.3. What they share: they do not meet the definition. In addition, the dialog takes focus, and for menus, accordions or tabs, 4.1.2 already covers announcing the state change.
For the case of a survey that adds new questions after an answer, the W3C adds that announcing those questions, or warning users in advance that content may change based on their answer, is not normatively required but can still improve the experience for screen reader users.
- An error message displayed in a dialog: the dialog takes focus, which is a change of context already announced by the screen reader.
- Content shown or hidden when expanding a menu, select, accordion or tree, or switching tabs: these changes do not meet the definition of a status message; moreover, these components fall under 4.1.2 Name, Role, Value, and their state changes ("expanded", "collapsed") are already announced.
- New survey questions added after an answer: they do not report a result, a waiting state, progress or errors.
role="status", role="alert", role="log": which role for which status message?
The W3C groups the sufficient techniques into three situations. Pick the one that matches your message.
Situation A: the message reports the success or results of an action, or the state of an application. Technique ARIA22 uses role="status", combined with G199 (providing success feedback when data is submitted successfully).
Situation B: the message conveys a suggestion or a warning about the existence of an error. Technique ARIA19 uses role="alert" or live regions to identify errors, combined with one of G83 (required fields not completed), G84 (value not in the list of allowed values), G85 (input outside the required format or values), G177 (suggested correction text) or G194 (spell checking and suggestions). The W3C points out that a role of "alert" is only necessary where a change of context does not take place.
Situation C: the message conveys the progress of a process. The listed techniques are ARIA23 (role="log" for sequential information updates), ARIA25 (an ARIA live region for the status of a progress bar), ARIA22 combined with G193 (help provided by an assistant in the web page) and ARIA27 (ariaNotify for the status of a progress bar).
The purely illustrative example below covers situations A and B: the element carrying the role is in the page from the start, and the script inserts the full message text into it.
<!-- Situation A: result of an action -->
<div id="search-status" role="status"></div>
<!-- Situation B: existence of an error -->
<label for="zip">Postal code</label>
<div id="zip-error" role="alert"></div>
<input id="zip" name="zip">
<script>
// After the search: the full message, not just the number
document.getElementById('search-status').textContent = '5 results returned';
// After an incorrect entry
document.getElementById('zip-error').textContent = 'Invalid entry';
</script>aria-live and status messages: the tricky cases
The criterion was intentionally worded to apply primarily when visible text is added to the page or becomes visible. The W3C nevertheless identifies four cases that need thought.
Non-displayed text for assistive technology users. Visible text may not be enough on its own: for example, its proximity to other information on screen may provide visual context that the text alone lacks. You can then add non-displayed content to the status message, provided to assistive technologies, for added context.
Modifying status text. If a status message persists on the page, changing it is usually equivalent to a new status message. Take a cart going from "0 items" to "3 items": if only the number is coded as the updated chunk, a screen reader user may only hear "three". Marking the entire "3 items" string as the status text is normally better; the W3C refers to the sufficient techniques for this, including the use of aria-atomic. Adding offscreen text such as "in shopping cart" is also a courtesy.
Removing status text. When a "busy" or "waiting" message disappears, sighted users usually read it as the system being available again. Non-sighted users are unaware of this, unless the end of the waiting state causes a change of context. Where updating the visible message to "system available" is not feasible, a non-visible status message with that text ensures equivalent information.
Non-textual status content. When an icon or sound indicates a status, the screen reader surfaces it through two combined requirements: text alternatives under 1.1.1 Non-text Content, and the appropriate role required by 4.1.3.
Live region mistakes to avoid
The failure documented by the W3C is F103: providing status messages that cannot be programmatically determined through role or properties.
The opposite excess exists too. Live regions and alerts can be useful in many situations that are not status messages, but the W3C warns about making an application too "chatty" for screen reader users and recommends user testing to reach the right level of feedback. It also lists among failures, without a detailed page so far, using role="alert" or aria-live="assertive" on content that is not important and time-sensitive.
Finally, the criterion does not force you to create new status messages. Its purpose is that when status messages are displayed, they are programmatically identified so assistive technologies can present them.
To audit your pages, ask these questions about every message that appears after an action:
- does the message report a result, a waiting state, progress or an error?
- does it appear without a change of context (focus moving, new page, new window…)? If yes to both questions, it is a status message;
- does it carry a role or properties suited to its situation (status, alert, log, live region, ariaNotify or another programmatically determinable means)?
- is the announced text understandable on its own, without the visual context?
- is the end of a waiting state also conveyed?
- do you keep role="alert" and aria-live="assertive" for important, time-sensitive content?
Frequently asked questions
What is the difference between role="status" and role="alert"?
In the W3C techniques, role="status" (ARIA22) is for messages about the success or results of an action, or the state of an application (Situation A); combined with G193, ARIA22 is also listed for the progress of a process (Situation C). role="alert" or a live region (technique ARIA19) is for suggestions and warnings about the existence of an error; the W3C notes that a role of "alert" is only necessary where no change of context takes place. Keep role="alert" for important, time-sensitive content.
Do status messages have to use aria-live?
SC 4.1.3 requires the message to be programmatically determinable through role or properties. Live regions are among the sufficient techniques (ARIA19, ARIA25), alongside the status, alert and log roles, and, according to the W3C, the criterion applies more generally to programmatically determinable ways of conveying status messages, including direct access to accessibility APIs.
Is an error dialog a status message?
No. The dialog takes focus: that is a change of context, already announced by the screen reader. It does not meet the definition of a status message and is outside the scope of 4.1.3.
Should search results be announced by screen readers?
The list of results itself is not a status message. A brief text such as "Searching...", "18 results returned" or "No results returned" is one, if it does not take focus or refresh the page, so it must carry an appropriate role or properties.
Does WCAG 4.1.3 require adding status messages?
No. The W3C states that the criterion is not meant to force authors to generate new status messages. It only ensures that status messages that are displayed are programmatically identified so assistive technologies can present them.
What level is WCAG 4.1.3 Status Messages?
Success Criterion 4.1.3 Status Messages is Level AA.
Further reading on Conformly
Sources
This article relies on the official sources listed at the end of the page.