Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →WCAG 2.2 Success Criterion 4.1.3 is a Level AA requirement for making qualifying status messages programmatically identifiable so assistive technologies can present them without moving focus. It does not require announcing every changed element, nor does it turn unchanged page text into a live update. The key is to identify messages about action outcomes, waiting states, progress, or errors—and choose semantics and announcement urgency that suit the message.
What WCAG 4.1.3 requires
WCAG 2.2 Success Criterion 4.1.3, “Status Messages,” says: “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.” It is a Level AA criterion in the W3C Recommendation dated 12 December 2024. Read the normative criterion.
As an Amazon Associate I earn from qualifying purchases.
In practical terms, when a qualifying message appears or changes without taking focus, its role or properties need to make its status identifiable to assistive technology. The user should not have to navigate to the message just to discover the update.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWhat counts as a status message—and what does not
A status message communicates the result of an action, an application’s waiting state, process progress, or the existence of an error, without changing context. Examples include a brief “18 results returned” message after a search, a cart count after adding an item, a submission confirmation, or an intermittent progress update. The full set of search results is content, not itself a status message. W3C’s Understanding document explains the scope and examples.
#1 Best Overall
- Unchanged text: A static block that has not changed is not a live-region event. SC 4.1.3 does not require authors to invent messages or announce all text on a page.
- Focus or context change: If an update moves focus or opens a new context that takes focus, the user is already alerted to the change; that situation is outside this criterion’s specific scope. For example, an error presented in a dialog that takes focus is not a 4.1.3 status message.
- Control state: A control changing between states such as expanded and collapsed is addressed through requirements for user-interface components, rather than by treating every such change as a status message.
- Arbitrary dynamic content: A changed region is not automatically a status message. Determine whether it communicates an action outcome, waiting or application state, progress, or an error.
Choose semantics to match the update
The roles are not interchangeable shortcuts. Consider the update’s purpose, urgency, whether it takes focus, and whether the whole message or only a changed part should be announced.
| Pattern | Best fit | Announcement behavior and cautions |
|---|---|---|
role="status" |
Routine action results or application-state updates, such as a search result count or cart confirmation. | WAI-ARIA 1.2 gives status implicit aria-live="polite" and aria-atomic="true". A polite update generally avoids interrupting the current task. W3C documents this as a sufficient technique. See technique ARIA22 and the WAI-ARIA 1.2 status role definition. |
role="alert" or an assertive live region |
Important, usually time-sensitive information that needs prompt attention, including certain errors. | Assertive announcements may interrupt other speech. Reserve them for genuinely urgent messages; W3C cautions against using alert or aria-live="assertive" for content that is not important and time-sensitive. See the WAI-ARIA 1.2 alert role definition. |
role="log" or progress-related techniques |
Sequentially updated content or process progress, where the user may benefit from updates as they occur. | Choose a pattern according to the content’s meaning and desired feedback. W3C groups log and progress techniques with the examples for status-message types; these techniques are not the only possible ways to meet the technology-neutral criterion. See W3C’s status-message guidance. |
Implement a routine update with role="status"
For an ordinary result or state update, a status container is a sensible starting point. Put the semantic role in the markup before the dynamic message is inserted:
Rank #2
- Core Functionality: This color test book provides a comprehensive and user-friendly color chart designed specifically for early detection of color deficiency, facilitating timely intervention and safer driving assessments
- Material and Design: Crafted from stable, lightweight, and durable materials, this test book offers convenience and longevity for repeated use in various settings
- Language and Accessibility: Designed in english to ensure easy understanding and accurate self-administration of the color test book by english-speaking users, enhancing usability and testing accuracy
- Portability and Storage: Compact dimensions of approximately 3.81 by 3.34 by 0.11 inches and lightweight construction make this test book highly portable and easy to store for use in clinics, schools, or at home
- Practical Application: Ideal for use in various scenarios such as driver screening, vision examinations, and color deficiency assessments, this color test book integrates multiple test charts to support thorough visual evaluations
<div id="search-status" role="status" aria-atomic="true"></div>When a search completes, update the container’s text:
document.getElementById("search-status").textContent = "18 results returned.";W3C’s ARIA22 example uses the same essential pattern: <div role="status" aria-atomic="true">5 results returned.</div>. aria-atomic="true" indicates that the complete contents should be announced, rather than only a changed fragment. Although WAI-ARIA specifies an implicit atomic value for status, ARIA22 advises setting it explicitly because some environments may not treat the role as atomic by default.
Make sure the text gives enough context to be useful on its own. For example, a cart count can say what changed, and a progress update can identify the process it describes. Avoid repeating the same information through multiple live regions.
Put the role in place before the update
Assistive technology needs to be able to detect the change as it happens. If JavaScript first inserts a message and only then adds live-region semantics, the update may not be announced. W3C failure technique F103 describes this timing problem and a case in which results are visible but a screen-reader user hears nothing until manually navigating to them. Read failure technique F103.
For server-rendered content, the role can be present when the page loads. For client-side updates, keep the live-region element in the document with its semantics already set, then change its contents when the message is ready.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Test the announcement, not just the markup
Valid-looking ARIA does not guarantee that the update is exposed or useful in a user’s actual browser and assistive-technology combination. Verify that a representative user can receive the message without moving focus and that it is announced at a suitable time.
- Trigger the action that produces the message using the normal interface.
- Keep focus where the action left it; do not navigate to the message.
- Use a representative screen reader and browser for the product’s target audience to check whether the update is detected, what text is announced, and whether it interrupts other speech.
- Check repeated updates, including whether content is announced once, in useful context, and without unnecessary repetition.
W3C’s F103 procedure includes checking whether assistive technology detects and exposes the update. The appropriate combinations depend on the product; there is no single markup check that replaces this evaluation.
Keep feedback useful rather than chatty
Live regions can provide helpful feedback beyond cases strictly covered by SC 4.1.3, but announcing every small change risks making an application “chatty.” Too many interruptions can obscure more important information. Tune what is announced, how much is announced, and how urgent it sounds through user testing. W3C explicitly recommends testing to find the appropriate level of feedback. See W3C’s guidance on status messages and feedback.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
