The 12 December 2024 WCAG 2.2 Recommendation classifies SC4.1.3, Status Messages, as Level AA. In markup-based content, qualifying status messages must expose programmatically determinable role or property information so assistive technology can present them without giving the messages focus.

A qualifying status message informs the user about action results, an application waiting state, process progress, or errors without changing context. W3C’s informative Understanding guide excludes dialogs that take focus, distinguishes brief search-status notifications from complete search-result listings, and explains that not all content or control-state changes qualify. The criterion requires accessible communication; it does not prescribe a particular ARIA technique.

Sources:
- [W3C WCAG 2.2 Recommendation, SC4.1.3](https://www.w3.org/TR/2024/REC-WCAG22-20241212/#status-messages)
- [W3C Understanding Status Messages](https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html)

Status messages conveyed without receiving focus

Users must be able to interpret content reliably, including those using assistive technologies.

New York University

The Web Content Accessibility Guidelines (WCAG) is a global standard for web content accessibility, with documents explaining how to make web content more accessible for those with disabilities.  Web content refers to text, images, and sounds, as well as code or markup.  In the WCAG 2.0 and 2.1 Documents, there are guidelines included based on these four principles: “perceivable, operable, understandable, and robust.”

Web Content Accessibility Guidelines (WCAG)

https://www.w3.org/WAI/standards-guidelines/wcag/

Web Content Accessibility Guidelines

Information and user interface components must be presented to users in a way that they can perceive - interfaces should be designed so that it is easier for people to see and hear it, as well as providing alternatives for text, time-based media, and other content for people with disabilities.

WCAG - Perceivable

Users must be able to navigate through and operate the interface.  It cannot require an interaction that the user is unable to perform.  This means that designs should ways to help users navigate, and should include making all of the functionality available from a keyboard.

WCAG - Operable

Users must be able to understand the content and operation of the interface.  The web pages should operate in predictable ways, and the content should be readable and easy to understand.

Learn Before

Related

Learn After