-
Notifications
You must be signed in to change notification settings - Fork 21
4.1.3
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.
When something creates a status message, and it does not receive focus or change the context
A status message is a "change in content that is not a change of context, and that provides information to the user on the success or results of an action, on the waiting state of an application, on the progress of a process, or on the existence of errors".
If content informs the user about something that has dynamically changed without a page reload or changing the focus, that content or its status needs to be programmatically determined (for example, read out by screen readers).
To check status messages, use a screen reader. Use NVDA, because JAWS or VoiceOver try to fix things and will not expose all issues with this Success Criterion.
Do something that triggers a status message, such as waiting for news ticker item, submitting an empty form or filtering search results.
Then check:
- the screen reader announces a message
You can also manually check the code of a status message with the browser's inspector.
Check if status messages have attributes such as role=status or role=alert or role=log or aria-live.
Trigger status messages and check that they are announced by a screen reader.
It’s okay if only part of a message is read as long as the core meaning is conveyed.