4.1.3 Status Messages
Official description of the success criterion
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.
What to do?
Ensure status messages are available to assistive technologies without receiving focus.
Why is it important?
Informs users of important changes without interrupting their workflow.
Common pitfalls
Not understanding what are status messages. According to WCAG definitions, status messages are a change of 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.
Using role="alert" or aria-live "assertive" on content which is not important and time-sensitive.
Providing status messages that are not read to screen readers.
How to test for it?
Test with a screen reader if status messages are delivered to the user.