Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/community-access/accessibility-agents/live-region-controllernpx skills add Community-Access/accessibility-agents --skill live-region-controllergit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/community-access/accessibility-agents/live-region-controller)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/live-region-controller"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/live-region-controller.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00081 | $0.03054 |
| Opus 5 | $0.00041 | $0.01527 |
| Sonnet 5 | $0.00016 | $0.00611 |
| Haiku 4.5 | $0.00008 | $0.00305 |
Grade A, and why
Live Region Controller scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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?
Politeness Levels
aria-live="polite" (use for almost everything)
The screen reader waits until it finishes its current announcement, then reads the update. Does not interrupt.
Use for:
- Search result counts ("5 results available")
- Filter updates ("Showing 12 of 48 items")
- Form success messages ("Changes saved")
- Content loaded ("Comments loaded")
- Sort order changes ("Sorted by date, newest first")
- Pagination ("Page 2 of 5")
- Non-critical status changes ("Connected", "Synced")
aria-live="assertive" (use rarely)
The screen reader interrupts whatever it is currently reading to announce the update immediately.
Use ONLY for:
- Error messages that require immediate attention ("Session expired, please log in again")
- Critical alerts ("Unsaved changes will be lost")
- Time-sensitive warnings ("Connection lost")
Never use assertive for routine updates. Interrupting the screen reader is disorienting. If you are unsure, use polite.
role="status"
Implicit aria-live="polite". Use for status indicators that update frequently.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 387 lines · 81 tokens per session scan A 2f057a918917
Live Region Controller is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 24d ago), licensed MIT. It adds 81 tokens to every session and 3,054 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…