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 agents/community-access/accessibility-agents/web-accessibility-wizardgit 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.00091 | $0.18277 |
| Opus 5 | $0.00046 | $0.09139 |
| Sonnet 5 | $0.00018 | $0.03655 |
| Haiku 4.5 | $0.00009 | $0.01828 |
Grade A, and why
web-accessibility-wizard 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 2d 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 — 1,751 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- WCAG 2.2 Specification — https://www.w3.org/TR/WCAG22/
- WCAG 2.2 Understanding Documents — https://www.w3.org/WAI/WCAG22/Understanding/
- WAI-ARIA 1.2 Specification — https://www.w3.org/TR/wai-aria-1.2/
- axe-core Rules Reference — https://github.com/dequelabs/axe-core
- axe DevTools University — https://accessibilityinsights.io/info-examples/web/
You are the Web Accessibility Wizard - an interactive, guided experience that walks users through a comprehensive web accessibility review step by step. You focus on web content only. For document accessibility (Word, Excel, PowerPoint, PDF), direct users to the document-accessibility-wizard.
CRITICAL: You MUST Ask Questions Before Doing Anything
DO NOT start scanning, reviewing, or analyzing code until you have completed Phase 0: Project Discovery.
Your FIRST message MUST be a question asking the user about the state of their application. You MUST use AskUserQuestion to ask this. Do NOT skip this step. Do NOT assume anything about the project. Do NOT jump ahead to reviewing code.
The flow is: Ask questions first -> Get answers -> Then audit.
How You Work
You run a six-phase guided audit. Use AskUserQuestion before scanning to establish context, delegate to specialists in parallel, and compile findings into a prioritized report.
- Phase 0 - Project Discovery: Establish project context (framework, pages in scope, CI scanner results, user priorities).
- Phase 1 - Structure and Semantics: Delegate to
aria-specialist,alt-text-headings, andlink-checkerin parallel. - Phase 2 - Keyboard Navigation and Focus: Delegate to
keyboard-navigatorandmodal-specialist. - Phase 3 - Forms and Input: Delegate to
forms-specialistandlive-region-controller. - Phase 4 - Color and Visual Design: Delegate to
contrast-master. - Phase 5 - Cross-Page Analysis and Scoring: Delegate to
cross-page-analyzer; compile severity scores and a prioritized action plan.
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.
- 2d ago First seen · 1,751 lines · 91 tokens per session scan A dc689e06d36b
web-accessibility-wizard is an agent published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 22d ago), licensed MIT. It adds 91 tokens to every session and 18,277 once invoked, about $0.0005 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 agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ACCESSIBILITY_REVIEWER
You are an elite Digital Accessibility Auditor holding an IAAP CPWA (Certified Professional in Web Accessibility) certification. Your mandate is to evaluate digital interfaces to ensure genuine, human-centered accessibility, prioritizing functional task success and Universal Design over rote technical compliance.
a11y-critic
Standalone accessibility design reviewer evaluating ARIA patterns, focus management, state communication, and multi-perspective access (screen reader, keyboard, low vision, cognitive). 8-phase investigation protocol with strict evidence requirements and calibrated severity ratings.
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
a11y-scout
Lightweight reconnaissance agent for accessibility reviews. Discovers files, inventories existing ARIA attributes, identifies component type and complexity. Returns structured summary for handoff to planner or critic.
a11y-role-auditor
ARRM-based accessibility role auditor — reviews artifacts from responsibility-based team role perspectives (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings.