Robust / 4.1 Compatible
4.1.3Status Messages
Level AAConvey status changes -- "Saved", "3 results found" -- to assistive technology without moving the user's focus, typically via a live region (aria-live, role="status", etc.). A common technique is to place the container in the DOM ahead of time and insert the message into it, since some browser/screen-reader combinations won't reliably announce text added to an element that appears at the same moment. Notifications that involve an actual change of context, such as a full page reload, fall outside this criterion.
Specification updated
- Enhancement#5079(opens in a new tab)4.1.3: Mention ariaNotify and add new technique ARIA27
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(10)
Show all (10)
- ARIA19: Using ARIA role=alert or Live Regions to Identify Errors(opens in a new tab)waic.jp(opens in a new tab)
- ARIA22: Using role=status to present status messages(opens in a new tab)waic.jp(opens in a new tab)
- ARIA23: Using role=log to identify sequential information updates(opens in a new tab)waic.jp(opens in a new tab)
- G83: Providing text descriptions to identify required fields that were not completed(opens in a new tab)waic.jp(opens in a new tab)
- G84: Providing a text description when the user provides information that is not in the list of allowed values(opens in a new tab)waic.jp(opens in a new tab)
- G85: Providing a text description when user input falls outside the required format or values(opens in a new tab)waic.jp(opens in a new tab)
- G177: Providing suggested correction text(opens in a new tab)waic.jp(opens in a new tab)
- G193: Providing help by an assistant in the web page(opens in a new tab)waic.jp(opens in a new tab)
- G194: Providing spell checking and suggestions for text input(opens in a new tab)waic.jp(opens in a new tab)
- G199: Providing success feedback when data is submitted successfully(opens in a new tab)waic.jp(opens in a new tab)
Advisory Techniques(2)
Normative References
- Success Criterion 4.1.3 Status Messages — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Status Messages — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.