aria-live-regionslisted

# 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 ARIA live regions announce dynamic content changes to screen reader users who would otherwise miss updates happening outside their current focus point. They are powerful and frequently misused. The most common errors are: 1. Using `assertive` when `polite` is correct (interrupts the user) 2. Injecting the live region dynamically (AT misses the initial announcement) 3. Announcing too much or too little 4. Using live regions as a substitute for proper focus management **Default to `polite`. Reach for `assertive` only when a delay would cause the user to take a wrong action.** --- ## Severity Scale (this skill) | Level | Meaning | |---|---| | **Critical** | Dynamic content change conveys no information to AT; user cannot complete task | | **Serious** | `assertive` used for non-urgent updates, interrupting screen reader mid-sentence; live region injected dynamically and missed by AT | | **Moderate** | Status updates absent; success/failure not announced; announcements too verbose | | **Minor** | Redundant announcements; live region content duplicates visib