liveBook · Manning

Status role

As explained in Architecting Accessibility

The ARIA status role identifies a live region for non-urgent updates that should not interrupt the current announcement.

A screen-reader user can miss a visual-only update, such as a completed upload. A container with role="status" makes its updates available to assistive technology as well as visible on screen. section 3.4.4

Use status for non-urgent updates: it behaves as a polite live region, so announcements wait until the screen reader is idle. It also implies aria-atomic="true". Save role="alert" for urgent messages; frequent or unnecessary announcements can cause confusion and fatigue. section 6.1.7 section 3.4.4

<div role="status"> #A
  File uploaded #B
</div>

This status region displays “File uploaded” and communicates the update to assistive technology. section 3.4.4

How Architecting Accessibility covers it

How deep it goes
Defines polite, atomic behavior and cautions against unnecessary announcements, while noting inconsistent support for removed-content announcements.
Examples
Uses file uploads, cart additions, saved changes, and processing-to-success toasts as status messages.
What you can do after
Apply it to announce useful non-urgent updates while avoiding noisy, rapidly changing messages.
How it connects
Connects ARIA live regions with aria-live, aria-atomic, screen readers, alert, and toast notifications.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.