liveBook · Manning

Status message

As explained in Architecting Accessibility

A status message communicates information about a task or interface state without requiring a change of context.

A form can change without moving focus. A booking request may start processing, then succeed, while its updates appear in a toast elsewhere on the screen. A sighted user may notice the toast; a screen reader user may not. A status message makes the update available without requiring the person to find it or leave their current context. section 6.1.7 section 6.7

Give people useful feedback at the points where a task changes state:

  • During input, report relevant dynamic changes or validation messages. section 6.1.7
  • After submission, say what is happening: “Uploading files” or “Processing your booking details.” section 6.1.7
  • On completion, state the outcome clearly: “Your booking has been confirmed.” section 6.1.7

Place a live-region container in the DOM before updating its content. For an ordinary, non-urgent update, role="status" makes the message available to assistive technologies and allows a screen reader to finish its current announcement first. Show the same information visibly; a sound alone is not enough. section 6.1.7 section 3.4.4 section 6.1.10

<div id="toast" class="toast" popover="manual" role="status"> #A
  <span id="toast-message"></span>
</div>

This toast has role="status" on its container. Its message element can receive updates such as processing and success messages without moving focus to the toast. section 6.1.7

TIP: Reserve role="alert" for genuinely urgent, time-sensitive information; it can interrupt an announcement. Do not announce every small progress change. For a consequential task such as a bill payment or hotel booking, ask whether a temporary success toast is enough. A confirmation page can provide a reference number, an outcome summary, and the next action. section 3.4.4 section 6.1.7

A form that reports its state

A form shows “The form is valid and is being submitted” while processing, then reports its result. If the user clears it, “The form has been cleared” appears visibly and through a role="status" container that was present when the page loaded. section 6.1.10

How Architecting Accessibility covers it

How deep it goes
Explains when to report task states and how to prepare a live region, with guidance on urgency and excessive announcements.
Examples
Uses file uploads, booking updates, a status-role toast, and messages for submitting or clearing a form.
What it assumes
Introduces the purpose of live regions while assuming familiarity with HTML forms and DOM containers.
What you can do after
Build it from scratch using a pre-existing live region to present visible, programmatically available task updates.
How it connects
Connects form validation and submission feedback to ARIA live regions, screen readers, toast notifications, and confirmation pages.

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.