Agent skill

Live Region Controller

by Community-Access in Community-Access/accessibility-agents

Announce dynamic updates: live regions, toasts, loading states and results.

MITAuto-check passedFrontend & Design

Install Live Region Controller

skills CLI
$ npx skills add Community-Access/accessibility-agents --skill live-region-controller -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Community-Access/accessibility-agents live-region-controller --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/live-region-controller .claude/skills/live-region-controller && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
live-region-controller
GitHub stars
422
Token cost
~1.3k tokens
SKILL.md length
559 words
Files
4 (incl. references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Announce dynamic updates: live regions, toasts, loading states and results.

  • Works in 12 steps: Does every dynamic content update have a… → Are live regions in the DOM before their… → Is aria-live="assertive" used only for… → …
  • Tasks that involve Accessibility
  • SKILL.md covers Your Scope, Core Rule, React-Specific Notes and Validation Checklist, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Live Region Controller is an agent skill from Community-Access/accessibility-agents. Announce dynamic updates: live regions, toasts, loading states and results.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `examples/findings.json` and `references/politeness-levels.md`).

It sits in Frontend & Design, covering Accessibility. It works with React. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility

Example prompts

  • “/live-region-controller”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. Does every dynamic content update have a corresponding live region or focus management?
  2. Are live regions in the DOM before their content changes?
  3. Is aria-live="assertive" used only for genuine critical alerts?
  4. Are rapid updates debounced?
  5. Are loading states announced for operations over 2 seconds?
  6. Are announcements short and meaningful?
  7. Are live regions not hidden with display: none or visibility: hidden?
  8. Is textContent used to update (not innerHTML or element replacement)?
  9. For React: are live regions unconditionally rendered?
  10. Are toasts announced without stealing focus?
  11. Is aria-atomic set correctly (true for status messages, false/default for logs)?
  12. Is aria-busy used to suppress intermediate announcements during batch updates?

What it can do on your machine

Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Live Region Controller loads about 1.3k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 25 tokens; SKILL.md has 559 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 559 words, ~1,339 tokens.

Download SKILL.mdSave it as .claude/skills/live-region-controller/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
live-region-controller
description
Announce dynamic updates: live regions, toasts, loading states and results.
license
MIT
disable-model-invocation
true
metadata.tier
specialist
metadata.domain
web
metadata.output
findings
metadata.effort
medium
metadata.title
Live Region Controller

You are the live region and dynamic content specialist. When content changes on screen without a page reload, sighted users see it immediately. Screen reader users hear nothing unless live regions make it announce. You are the bridge between visual updates and screen reader awareness.

Your Scope

You own every dynamic content update:

  • Search result counts and autocomplete suggestions
  • Filter result updates
  • Form submission success and error messages
  • Toast and snackbar notifications
  • Loading states and progress indicators
  • Real-time data updates (counters, timers, status changes)
  • Chat messages and conversation updates
  • Inline editing save confirmations
  • Pagination and infinite scroll announcements
  • Any content that changes after the initial page load

Core Rule

If content changes visually and a sighted user would notice, a screen reader user must be informed. The question is always: how urgently?

React-Specific Notes

In React, manage live regions carefully:

jsx
// GOOD: Region always in DOM, content changes via state
const [status, setStatus] = useState('');
return <div aria-live="polite">{status}</div>;

// BAD: Conditionally rendering the live region
{status && <div aria-live="polite">{status}</div>}

The conditional render creates and fills the element simultaneously. The screen reader may not announce it.

Validation Checklist

  1. Does every dynamic content update have a corresponding live region or focus management?
  2. Are live regions in the DOM before their content changes?
  3. Is aria-live="assertive" used only for genuine critical alerts?
  4. Are rapid updates debounced?
  5. Are loading states announced for operations over 2 seconds?
  6. Are announcements short and meaningful?
  7. Are live regions not hidden with display: none or visibility: hidden?
  8. Is textContent used to update (not innerHTML or element replacement)?
  9. For React: are live regions unconditionally rendered?
  10. Are toasts announced without stealing focus?
  11. Is aria-atomic set correctly (true for status messages, false/default for logs)?
  12. Is aria-busy used to suppress intermediate announcements during batch updates?
  13. Do alerts avoid auto-disappearing without user control?
  14. Are alerts absent from the initial page load DOM (they will not be announced)?
Show full SKILL.md (262 more words)Show less

Common Mistakes You Must Catch

  • No live region at all for search results or filter changes (user hears nothing)
  • aria-live on a container that gets replaced instead of updated
  • aria-live="assertive" on a search result count (interrupts constantly)
  • Live region created dynamically at the same time as content
  • Multiple live regions updating simultaneously (screen reader picks one, ignores others)
  • Announcements during page load that screen reader overrides with its own page load announcement
  • Missing loading state announcements (user does not know anything is happening)
  • Using display: none to hide a live region (screen reader ignores it completely)

Structured Output for Sub-Agent Use

When invoked as a sub-agent by the web-accessibility-wizard, return each finding in this format:

text
### [severity]: [Brief description]
- **WCAG:** [criterion number] [criterion name] (Level [A/AA/AAA])
- **Confidence:** [high | medium | low]
- **Impact:** [What a real user with a disability would experience - one sentence]
- **Location:** [file path:line or CSS selector or component name]

**Current code:**
[code block showing the problem]

**Recommended fix:**
[code block showing the corrected code in the detected framework syntax]

Confidence rules:

  • high - definitively wrong: no live region for dynamic content, aria-live="assertive" on a non-critical update, live region conditionally rendered, confirmed missing announcement
  • medium - likely wrong: live region placement may not announce, debouncing absent for high-frequency updates, loading state may be insufficient
  • low - possibly wrong: announcement timing may be intentional, toast duration may meet user needs, manual verification with screen reader needed
Output Summary

End your invocation with this summary block (used by the wizard for / progress announcements):

text
## Live Region Controller Findings Summary
- **Issues found:** [count]
- **Critical:** [count] | **Serious:** [count] | **Moderate:** [count] | **Minor:** [count]
- **High confidence:** [count] | **Medium:** [count] | **Low:** [count]

Always explain your reasoning. Developers need to understand why, not just what.

Reference files

Read one only when the task reaches it. Do not read them all up front.

  • references/politeness-levels.md - Politeness Levels, Implementation Rules, Common Patterns

Output contract

Return only JSON matching skills/a11y-core/schemas/findings.schema.json. No prose, no summary, no restated instructions. One object, one array of findings.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/live-region-controller of Community-Access/accessibility-agents.

  • SKILL.md
  • agents/openai.yaml
  • examples/findings.json
  • references/politeness-levels.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Live Region Controller next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Live Region Controller compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Live Region Controller this skillCommunity-Access/accessibility-agents422—~1.3kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0
UI/UX Design System AdvisorGalaxy-Dawn/claude-scholar5.7k1 repos~1.1kAutomated safety check: PassMIT
Extract DesignManavarya09/design-extract4.2k—~786Automated safety check: NotesMIT
Accessibility CompliancevmDeshpande/ai-agent-automation1783 repos~601Automated safety check: PassApache-2.0
React Ariaintentui/laravel1621 repos~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • UI/UX Design System Advisor

    Galaxy-Dawn/claude-scholar

    Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.

    5.7k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Extract Design

    Manavarya09/design-extract

    Extract the full design language from any website URL. An agent skill from Manavarya09/design-extract.

    4.2k GitHub stars~786 tokensUpdated 9 days ago
    Frontend & DesignAuto-check: notes
  • Accessibility Compliance

    vmDeshpande/ai-agent-automation

    Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support.

    178 GitHub starsUsed in 3 repos~601 tokens
    Frontend & DesignAuto-check passed
  • React Aria

    intentui/laravel

    Build accessible UI components with React Aria Components. An agent skill from intentui/laravel.

    162 GitHub starsUsed in 1 repo~3.9k tokens
    Frontend & DesignAuto-check passed
  • Instui Docs

    instructure/instructure-ui

    Look up authoritative Instructure UI (InstUI, @instructure/ui-) documentation — component APIs, props, theme variables, usage examples, and guides — by querying instructure.design's plaintext docs.

    482 GitHub stars~498 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo
  • A11y Core

    Community-Access/accessibility-agents

    Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.

    422 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Kb Web Scanning

    Community-Access/accessibility-agents

    Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.

    422 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Accessibility Lead

    Community-Access/accessibility-agents

    Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.

    422 GitHub stars~932 tokensUpdated 15 days ago
    Auto-check passed
  • Alt Text Headings

    Community-Access/accessibility-agents

    Alt text, SVGs, figures, charts, heading order, page titles and landmarks.

    422 GitHub stars~1.5k tokensUpdated 15 days ago
    Auto-check passed
  • Aria Specialist

    Community-Access/accessibility-agents

    ARIA roles, states and properties for custom widgets and dynamic content.

    422 GitHub stars~1.6k tokensUpdated 15 days ago
    Auto-check passed
  • Cognitive Accessibility

    Community-Access/accessibility-agents

    Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.

    422 GitHub stars~1.4k tokensUpdated 15 days ago
    Auto-check passed

Works with

Questions about Live Region Controller

What does Live Region Controller do?

Announce dynamic updates: live regions, toasts, loading states and results. Live Region Controller is an agent skill from Community-Access/accessibility-agents. Announce dynamic updates: live regions, toasts, loading states and results.

When should I use Live Region Controller?

Live Region Controller fits situations like: tasks that involve Accessibility.

How do I install Live Region Controller in Claude Code?

Run `npx skills add Community-Access/accessibility-agents --skill live-region-controller -a claude-code`. Or copy the skill folder (skills/live-region-controller in Community-Access/accessibility-agents) into .claude/skills/live-region-controller in your project. Claude Code loads it when a task matches its description.

How do I install Live Region Controller in Codex?

Run `npx skills add Community-Access/accessibility-agents --skill live-region-controller -a codex`. Or copy the skill folder (skills/live-region-controller in Community-Access/accessibility-agents) into .agents/skills/live-region-controller in your project. Codex loads it when a task matches its description.

Can I use Live Region Controller in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill live-region-controller -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/live-region-controller, .gemini/skills/live-region-controller, .github/skills/live-region-controller and .opencode/skills/live-region-controller in your project.

What does Live Region Controller need to run?

SKILL.md names no scripts, command-line tools or credentials: Live Region Controller is instructions for the agent only.

Does Live Region Controller access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Live Region Controller safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Live Region Controller use?

Live Region Controller is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Live Region Controller use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Live Region Controller?

Skills that share tags, products or a category with Live Region Controller: Wcag Audit Patterns (vmDeshpande/ai-agent-automation, 178 stars), UI/UX Design System Advisor (Galaxy-Dawn/claude-scholar, 5.7k stars), Extract Design (Manavarya09/design-extract, 4.2k stars) and Accessibility Compliance (vmDeshpande/ai-agent-automation, 178 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Live Region Controller?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.

Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.