Status messages

[md84419]

WCAG2.2 clause 4.1.3 says:
(Level AA)
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.

There are two guidance notes to accompany section 4.1.3:

• https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html
• https://www.w3.org/WAI/WCAG22/quickref/#status-messages

Recently, GitHub have updated their guidance to note that the use of toasts and snackbars are considered an anti-pattern. They aren't the first - many other technology companies already have similar guidelines about the use of transient floating notifications or floating ephemeral messages.

I'd therefore like to propose a tightening of the equivalent WCAG3 section:

Requirement:

Ensure status messages are perceivable.

1. Users must be able to perceive and review status messages for long enough to understand them and take action.
2. Such messages must be programmatically determined by and presented to assistive technologies, without receiving focus.
3. Such messages must be perceivable and actionable by users (including Sign Language users (issue Clarifying and Enhancing Requirements for Sign Language and Subtitles in WCAG 3.0 #325)), through assistive technologies.

Applies when:

Presenting status messages.

Except when:

• the change is already fully visible and self-evident within the interface without additional messaging; and
• the information is accessible by another, persistent, mechanism.

Notes

Note1: Examples of anti-patterns: Use of:

• toasts
• snackbars
• other transient floating notifications or floating ephemeral messages

Note2: Inline, ideally persistent, status messages are preferred.
Note3: Examples of programmatically determined include through role or properties. See notes 5 & 6 for further information.
Note4: This requirement is consistent with, for instance, Gov.UK Design System, US Digital Service guidelines, and guidelines from multiple technology vendors.
Note5: https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html
Note6: https://www.w3.org/WAI/WCAG22/quickref/#status-messages