Writing Accessible Status Messages
Writing Accessible Status Messages translates the WCAG status-message purpose into a bounded content-writing guide while leaving ARIA implementation mechanics outside the page.
Write status messages that clearly communicate important results, progress, waiting states, or errors when those updates need to be understood without moving focus.
Key details
Important caveats
Scope Boundary
This guide covers message content; technical live-region implementation remains a separate engineering concern.
Further guidance
Content
Use concise wording that tells users what changed or what state the process is in.
Purpose
Status wording should make important dynamic outcomes understandable without depending on a focus change.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Understanding Success Criterion 4.1.3: Status Messages — WCAG 2.2 (opens in a new tab)World Wide Web Consortium (W3C) · W3C WCAG 2.2 Understanding guidance for status messages that communicate results, waiting states, progress or errors without unnecessary focus changes.