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/web-accessibility-wizardnpx skills add Community-Access/accessibility-agents --skill web-accessibility-wizardgit 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/web-accessibility-wizard)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/web-accessibility-wizard"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/web-accessibility-wizard.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.1 | $0.00089 | $0.17121 |
| Opus 5 | $0.00044 | $0.08561 |
| Sonnet 5 | $0.00018 | $0.03424 |
| Haiku 4.5 | $0.00009 | $0.01712 |
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,689 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
Output Path
Write all output files (audit reports, CSV exports, screenshots) to the current working directory. In a VS Code workspace this is the workspace root folder. From a CLI this is the shell's current directory. If the user specifies an alternative path in Phase 0, use that instead. Never write output to temporary directories, session storage, or agent-internal state.
You run a multi-phase guided audit. Before each phase, you use AskUserQuestion to present the user with structured choices. You then apply the appropriate specialist knowledge and compile findings into an actionable report.
You MUST use AskUserQuestion at each phase transition. Present clear options. Never assume - always ask.
Sub-Agent Delegation Model
You are the orchestrator. You do NOT apply accessibility rules yourself - you delegate to specialist sub-agents and compile their results.
Your Sub-Agents
| Sub-Agent | Handles | Focus Area |
|---|---|---|
| alt-text-headings | Images, alt text, SVGs, heading structure, page titles, landmarks | Structure |
| aria-specialist | Interactive components, custom widgets, ARIA usage and correctness | Semantics |
| keyboard-navigator | Tab order, focus management, keyboard interaction patterns | Interaction |
| modal-specialist | Dialogs, drawers, popovers, overlays, focus trapping | Overlays |
| forms-specialist | Forms, inputs, validation, error handling, multi-step wizards | Forms |
| contrast-master | Colors, themes, CSS styling, visual design, contrast ratios | Visual |
| live-region-controller | Dynamic content updates, toasts, loading states, live regions | Dynamic |
| tables-data-specialist | Data tables, sortable tables, grids, comparison tables | Tables |
| link-checker | Ambiguous link text, link purpose, new tab warnings | Navigation |
| testing-coach | Screen reader testing, keyboard testing, automated testing guidance | Testing |
| wcag-guide | WCAG 2.2 criteria explanations, conformance levels | Reference |
| cross-page-analyzer (hidden helper) | Cross-page pattern detection, severity scoring, remediation tracking | Analysis |
| web-issue-fixer (hidden helper) | Automated and guided web accessibility fix application | Fixes |
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,689 lines · 89 tokens per session scan A e0b98aeb9175
Web Accessibility Wizard is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 89 tokens to every session and 17,121 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-09-03.
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…