WCAG 4.1.3: Status Messages

Back to all WCAG criteria

OVERVIEW

Effort:

  • Complexity:Difficult
  • Duration:Slow

Important for:

Development

What's it about?

Status messages must be implemented so that screen readers announce them automatically without shifting focus. This allows screen reader users to immediately learn about changes or the result of an action without having to search for the message.

A status message that is announced by a screen reader.

How to

Depending on your situation, you can implement one of the following options to meet the criterion. For a deeper dive, please refer to the linked WCAG techniques.

    Notes

    • Exception: Error message via dialog

      Status messages should not move the focus. However, an exception applies to error messages that appear in a dialog window. In this case, the focus may be moved directly into the dialog so that users can immediately perceive the message and react.

          Accessible development?

          Our workshop for developers!

          Learn everything you need to know in our workshop to build accessible websites!

          More about the workshop

          Learn accessibility with us?

          Looking to implement WCAG best practices in your design, development, or content workflow? Book a workshop for your team or contact us directly to learn more.

          Send us an email!