On this page:
There are different situations where a status message need to be shown in a way that screen readers understand. For example:
These messages need to be conveyed to users without disturbing the user’s position on a page.
Screen reader announcements (using ARIA Live regions for the Web, for example) should be used to inform screen reader users of these events without disrupting their position on the page.
4.1.3 Status Messages: 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. (Level AA)
See the W3C’s detailed explanation of this guideline with techniques and examples.
A sighted person can quickly see status messages on a page, and then go back to what they were doing or reading. Moving focus to a message can be disruptive for screen reader users, users of speech recognition software and keyboard only users.
If focus is always moved to the message users with cognitive impairments may also be confused by unpredictable focus changes.
The following are different situations you will need to cover:
When a status message tells the user something is successful or is the results of an action. This can also be used for a state change when part of a page updates:
You can use these following techniques:
Use the ARIA role=”status” to present status messages in combination with the technique Providing success feedback when data is submitted successfully.
NOTE: There may be times when the best user experience is to move focus to a message, such as an error, as a part of form validation etc. See the GDS’ Error Summary component and guidance for an example.
Use the following techniques:
Use ARIA role=”alert” or Live Regions to Identify Errors in combination with any of the following:
role="progressbar" can be used but may not be enough on its own (depending on support by browsers and assistive technologies). For some examples of
progressbar role see:
You can use the following techniques:
aria-live="assertive"on content which is not important.