aria-live-regions

# ARIA Live Regions Accessibility Skill > **Canonical source**: `examples/ARIA_LIVE_REGIONS_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when implementing any dynamic content updates announced to assistive technologies. **Only load this skill if the project contains dynamic content updates.** --- ## Core Mandate Live regions make dynamic status information available to screen reader users without moving keyboard focus — they are useful for concise updates (a result count, a saved confirmation, progress information). **Live regions are not a general notification system.** They do not replace visible content, native HTML, focus management, or a control's programmatic state. Poorly timed or excessive announcements can be missed, duplicated, reordered, or disruptive. Prefer visible status messages — they also help magnification users, cognitive/learning-disabled users, and anyone who wouldn't otherwise notice a change elsewhere on the page. Use native HTML and programmatic control state (e.g., `aria-expanded`) *before* reaching for a live region. --- ## Severity Scale (this skill) | Level | Meaning | |---|---| | **Critical** | Dynamic content change conveys no information to AT; user cannot complete task | | **Serious** | `assertive`/`role="alert"` used for non-urgent updates, interrupting mid-sentence; live region not exposed before the update it must report | | *...