VOCABULARY / ENTRY
Status Message
status-message
A content change that briefly reports the result of an action, a waiting state, or the existence of errors without changing the user's context, and that assistive technology can announce without receiving focus.
Recognizing it
- Appears right after the action, brief and tied to a specific object
- Does not cover content or take focus; the main content stays usable
- Carries a clear success, error, or informational meaning
Concept boundary
A status message reports an outcome or state only. It does not carry continuously quantified progress (that is the determinate progress bar) and does not block the current task to demand a response (that is the modal dialog). Toast and snackbar are presentation variants of it, not separate concepts.
When to consider it
- An action has completed or failed and people need a one-line confirmation
- The feedback does not require an immediate response or decision
- Content on the same page updates but the current task should not be interrupted
When to be cautious
- An error must be handled before continuing, yet the message dismisses itself
- Quantified, ongoing progress needs to be reported
- People must make an irreversible decision
Tradeoff
Non-blocking feedback keeps the task flowing, but briefly shown messages are easy to miss, and frequent announcements feel noisy to screen reader users.
Conditional rules · Editorial advice
Related entries
The progress bar expresses completed work during the process; the status message reports the final outcome.
Use a non-blocking status message when no response is needed; escalate to a modal dialog only when a decision or confirmation is required.
A status message keeps information at the periphery of attention, one way calm technology is realized at the micro-interaction level.
Sources and what they support
The Level AA criterion requires that status messages be programmatically determinable through role or properties so assistive technology can present them without receiving focus; a status message is defined as a non-context change reporting the success or result of an action, a waiting state, progress, or the existence of errors.
Retrieved: 2026-09-15 · Archived 2026-09-21An alert displays a brief, important message without interrupting the task and must not affect keyboard focus; alerts that disappear automatically and overly frequent interruptions should be avoided.
Retrieved: 2026-09-15Distinguishes action-required messages from passive ones: the former should interrupt and require handling before dismissal, while the latter suit an unobtrusive nonmodal popover that may disappear automatically.
Retrieved: 2026-09-15Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
No operable specimen yet; the illustration is editorial. A product must still verify that screen readers actually announce the message, how long it persists, keyboard reachability of the action button, and behavior under reduced motion.
{
"states": [
"hidden",
"success",
"info",
"error"
],
"a11y": [
"Announce through a live region without moving focus",
"Use status for general states and alert for errors needing immediate attention; avoid being too chatty"
],
"motion": "The slide-in may be simplified to a fade; appear instantly when reduced motion is enabled"
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.