4.1.3 Status Messages

When page content updates without a page reload, screen reader users do not know about the change unless they are told. If a user adds an item to a basket and a 'Added to basket' message appears, a sighted user sees it. A screen reader user misses it entirely unless it is programmatically announced.

This criterion requires that status messages (confirmations, errors, loading states, and other updates) are communicated to assistive technologies without requiring the user to move focus to the message.

The mechanism for this is ARIA live regions: containers with aria-live, role="status", or role="alert" attributes that cause screen readers to announce their contents when they change.

Use role="status" and aria-live="polite" for non-urgent messages that should be announced at the next opportunity, such as 'Item added to basket' or 'Search results updated'.

Use role="alert" or aria-live="assertive" for urgent messages that should interrupt immediately, such as error summaries or security warnings.

For loading states, announce when loading begins and when it completes: 'Loading results...' then 'Results loaded.'

Ensure the live region element exists in the DOM before content is inserted into it. Injecting the element and populating it at the same time often causes screen readers to miss the announcement.

• Form validation error summary that appears visually but has no role="alert" to announce it to screen readers
• 'Added to basket' confirmation that appears as a toast notification with no ARIA live region
• Search results that update without any announcement that new results are available
• Loading spinner that appears with no accessible loading announcement

Focus movement is sometimes used to communicate status, but this criterion specifically covers cases where focus does not move. If focus is moved to an error summary when a form is submitted, that is a valid approach, but it does not satisfy this criterion for status messages that appear without a focus change.

Not every update needs to be announced. Purely decorative changes, updates to content the user is not currently interacting with, and changes the user explicitly triggered (and therefore expects) may not need live region announcements.