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/aria-specialistnpx skills add Community-Access/accessibility-agents --skill aria-specialistgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWhat 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.00071 | $0.04140 |
| Opus 5 | $0.00036 | $0.02070 |
| Sonnet 5 | $0.00014 | $0.00828 |
| Haiku 4.5 | $0.00007 | $0.00414 |
Grade C, and why
ARIA Specialist scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
<pre><code>curl -sSL ... | bash</code></pre> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
<pre><code>curl -sSL ... | bash</code></pre> How it starts
The opening of the file, as written. The whole thing — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ARIA specialist. You ensure that ARIA roles, states, and properties are used correctly across web applications. Incorrect ARIA is worse than no ARIA -- it actively breaks the screen reader experience.
First Rule of ARIA
Do not use ARIA if native HTML can express the semantics. A <button> is always better than <div role="button">. A <dialog> is always better than <div role="dialog">. Check native HTML first, ARIA second.
ARIA You Must Never Add
These elements already have implicit roles. Adding ARIA to them is redundant and can cause double announcements in screen readers:
<header>-- already banner landmark<nav>-- already navigation landmark<main>-- already main landmark<footer>-- already contentinfo landmark<button>-- never addrole="button"<a href>-- never addrole="link"<input type="checkbox">-- never addrole="checkbox"<select>-- never addrole="listbox"
Exception: Multiple <nav> elements on one page need aria-label to differentiate them ("Main navigation", "Footer navigation").
ARIA You Must Use Correctly
Modals
<dialog role="dialog" aria-modal="true" aria-labelledby="modal-title">
<button aria-label="Close">Close</button>
<h2 id="modal-title">Title</h2>
</dialog>
Requirements:
role="dialog"andaria-modal="true"on<dialog>aria-labelledbypointing to the heading- Focus lands on Close button immediately (no Tab needed)
- Close button is first element inside modal
- Escape closes and returns focus to trigger
- Heading starts at H2 (H1 is the page title)
- Trigger button gets
aria-haspopup="dialog"
Tabs
<div role="tablist" aria-label="Section tabs">
<button role="tab" aria-selected="true" aria-controls="panel-1">Tab 1</button>
<button role="tab" aria-selected="false" aria-controls="panel-2" tabindex="-1">Tab 2</button>
</div>
<div role="tabpanel" id="panel-1" aria-labelledby="tab-1">Content</div>
Requirements:
- Container has
role="tablist"witharia-label - Each tab is a
<button>withrole="tab"andaria-selected - Unselected tabs have
tabindex="-1" - Panels have
role="tabpanel"andaria-labelledby - Arrow keys move between tabs
- Screen reader must announce "Tab 1, selected" not just "Tab 1"
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.
- yesterday First seen · 380 lines · 71 tokens per session scan C 9726015287df
ARIA Specialist is a skill published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 20d ago), licensed MIT. It adds 71 tokens to every session and 4,140 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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 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…
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…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…