Protocol
Choose the status message before the announcement
A changed screen is not always a status message. First identify the information and whether the user's context changes.
Before you use it
- Use when
- A background action changes status but assistive-technology users receive no useful signal.
Keep this limit in mind
- Not every update deserves an alert. Repeated progress announcements can overwhelm the information they were meant to reveal.
Current editorial reading
Separate feedback from a new place to work
A status message reports an outcome, waiting, progress or an error without changing the user's context. An export tool's completion notice beside the form can qualify while focus stays in place. An error dialog that takes focus and an options panel opening are different cases: check the dialog or control's own accessibility, rather than adding an alert by habit. WCAG 4.1.3 does not require new feedback for every change.
Make ordinary feedback available with its meaning
For non-urgent updates, WAI describes a role=status container that exists before the message arrives. Where this pattern fits, put the update and the context needed to understand it inside that container. If the whole phrase needs announcing, WAI advises explicit aria-atomic=true because some environments do not apply the role's atomic default. In an export tool, hearing 'Two files ready' is useful; hearing only 'Two' leaves the result unclear. This is one implementation pattern, not the only allowed technique.
Test the experience, not an announcement count
Record the browser, assistive technology and settings; trigger the change while doing another part of the task. Check access to the meaningful update and unnecessary interruptions. Useful progress feedback may be intermittent, and assistive technology may delay or suppress it according to user preferences. 'Spoken exactly once' is not the criterion. This check complements actionable error wording in 1104; it does not certify the whole interface.
Take it with you
Leave a test record: what changed, why it is a status message, how its meaning is exposed, and what happened in the tested setup.
Sources and evidence (3)
What we checked
SC 4.1.3 concerns programmatically determinable status information that can be presented without taking focus.
Normative scope, not a mandate for one spoken announcement or a complete conformance test.
Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, 12 December 2024 · SC 4.1.3; glossary: status message
Ordinary expansion and focus-taking dialogs fall outside this status-message criterion; timing can reflect user preferences.
Selected guidance qualifies the earlier once-only instruction. Other accessibility requirements remain applicable.
Understanding Success Criterion 4.1.3: Status Messages · Intent; Benefits; Status message examples; Examples of changes that are not status messages; Other uses of live regions or alerts
The ARIA22 pattern establishes the status container before an update and retains meaningful context within it.
The role defines atomic updates by default; WAI recommends explicit aria-atomic=true where the whole message is needed because support differs. This optional technique still needs testing in the intended environment.
ARIA22: Using role=status to present status messages · Description; Tests, Procedure 1–3
Editorial sources (3)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingChoose the status message before the announcement
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaInclude the people whose access needs your tests missUseful with this idea
Make the error show the next repairUseful with this idea
Make non-essential interaction motion optional
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
WCAG 4.1.3 addresses status messages that assistive technology can present without receiving focus.
Not every interface change is a status message; excessive or urgent announcements can be disruptive.
Understanding Success Criterion 4.1.3: Status Messages · Success criterion and intent.
All sources (1)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details