accessibility-agents — Claude Code skill: WCAG 2.2 AA audit routing
accessibility-agents is a Claude Code skill that routes accessibility checks to specialists and combines findings in a WCAG 2.2 AA report.
MIT 215 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill accessibility-agents -a claude-codeWhat accessibility-agents does
Accessibility is the first thing a model drops when it writes UI code. This package puts the check into the loop: six routers (accessibility-lead, web-accessibility-wizard, document-accessibility-wizard, markdown-a11y-assistant, developer-hub, github-hub) match a task to a named specialist and merge the results.
Specialists cover ARIA, keyboard handling and focus, forms, contrast, modals, live regions, tables, cognitive load, i18n, mobile UI, email and data visualisation. Scanners for Office, PDF and ePub sit alongside a markdown helper. Reports come from structured findings rather than the model's memory.
npx skills add brings the skills and nothing more. The hooks that hold back edits to user-facing files until the lead signs off, and the MCP server behind the scanners, arrive with the Claude plugin route or with node scripts/install.mjs. Routers look specialists up by name, so the package goes in as a whole.
What it helps with
- run a checkout form against WCAG 2.2 AA before committing
- confirm a modal traps focus and closes from the keyboard
- find accessibility faults in PDF, ePub and Office files
- repair alt text and heading order across markdown docs
- turn a scanner report into tracker tickets
Example prompts for the agent
- Run
accessibility-leadoversrc/pages/checkout.tsxand tell me what to fix first. - Audit every page in
sitemap.xmlwithweb-accessibility-wizard. - Check
docs/guide.pdfandreport.docxusingdocument-accessibility-wizard.
How to install accessibility-agents
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill accessibility-agents -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-agents/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-agents/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill accessibility-agents -a codex2Manually: put the files in place
.agents/skills/accessibility-agents/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill accessibility-agents -a cursor2Manually: put the files in place
.cursor/skills/accessibility-agents/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/accessibility-agents2Manually: put the files in place
.github/skills/accessibility-agents/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill accessibility-agents -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/accessibility-agentsManually: put the files in place
.devin/skills/accessibility-agents/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill accessibility-agents -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about accessibility-agents
How do I install accessibility-agents in Claude Code?
Run npx skills add podo/design-agent-skills --skill accessibility-agents -a claude-code. The skill lands at ~/.claude/skills/accessibility-agents/SKILL.md.
What does accessibility-agents do?
It routes accessibility work to specialist skills — web UI, full-site audits, Office/PDF/ePub files, markdown, GitHub workflows — and merges their findings into a WCAG 2.2 AA report.
Does npx skills add install the hooks and scanners?
No, it brings the skills only. The edit-blocking hooks and the scanner MCP server come with the Claude plugin route (/plugin marketplace add Community-Access/accessibility-agents, then /plugin install accessibility-agents@community-access) or with upstream's node scripts/install.mjs.
Source text
SKILL.md · MIT
--- name: accessibility-agents description: | WCAG 2.2 AA enforcement as a package of Agent Skills: router skills for web UI, full-site audits, Office/PDF/ePub documents, markdown, desktop and Python tooling, and GitHub workflows dispatch specialist, helper and reference skills by name. triggers: - "accessibility agents" - "Community Access" - "PDF accessibility" - "document accessibility" - "accessibility lead" das: type: package category: accessibility-quality upstream: "https://github.com/Community-Access/accessibility-agents" version: latest install: false --- # accessibility-agents > Catalogue stub — full package: [Community-Access/accessibility-agents](https://github.com/Community-Access/accessibility-agents) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** This package installs 108 skills (`accessibility-lead`, `web-accessibility-wizard`, `document-accessibility-wizard`, `markdown-a11y-assistant`, `developer-hub`, `github-hub`, `a11y-core`, `a11y-tool-builder`, `accessibility-regression-detector`, `accessibility-statement`, `actions-manager`, `alt-text-headings`, `analytics`, `aria-specialist`, `ci-accessibility`, `cognitive-accessibility`, `compliance-mapping`, `contrast-master`, `contributions-hub`, `cross-document-analyzer`, `cross-page-analyzer`, `daily-briefing`, `data-visualization-accessibility`, `design-system-auditor`, `desktop-a11y-specialist`, `desktop-a11y-testing-coach`, `document-csv-reporter`, `document-inventory`, `email-accessibility`, `epub-accessibility`, `epub-scan-config`, `excel-accessibility`, `forms-specialist`, `i18n-accessibility`, `insiders-a11y-tracker`, `issue-tracker`, `kb-accessibility-rules`, `kb-ci-integration`, `kb-cognitive-accessibility`, `kb-data-visualization-accessibility`, `kb-design-system`, `kb-document-scanning`, `kb-email-accessibility`, `kb-framework-accessibility`, `kb-github-a11y-scanner`, `kb-github-analytics-scoring`, `kb-github-scanning`, `kb-github-shared-instructions`, `kb-github-workflow-standards`, `kb-help-url-reference`, `kb-legal-compliance-mapping`, `kb-lighthouse-scanner`, `kb-markdown-accessibility`, `kb-media-accessibility`, `kb-mobile-accessibility`, `kb-office-remediation`, `kb-path-instructions`, `kb-playwright-testing`, `kb-python-development`, `kb-report-generation`, `kb-severity-mapping`, `kb-testing-strategy`, `kb-web-scanning`, `kb-web-severity-scoring`, `keyboard-navigator`, `lighthouse-bridge`, `link-checker`, `live-region-controller`, `markdown-csv-reporter`, `markdown-fixer`, `markdown-scanner`, `media-accessibility`, `mobile-accessibility`, `modal-specialist`, `notifications-manager`, `nvda-addon-specialist`, `office-remediator`, `office-scan-config`, `pdf-accessibility`, `pdf-remediator`, `pdf-scan-config`, `performance-accessibility`, `playwright-scanner`, `playwright-verifier`, `powerpoint-accessibility`, `pr-review`, `projects-manager`, `python-specialist`, `release-manager`, `repo-admin`, `repo-manager`, `scanner-bridge`, `screen-reader-lab`, `security-dashboard`, `tables-data-specialist`, `team-manager`, `template-builder`, `testing-coach`, `text-quality-reviewer`, `wcag-aaa`, `wcag-guide`, `wcag3-preview`, `web-component-specialist`, `web-csv-reporter`, `web-issue-fixer`, `wiki-manager`, `word-accessibility`, `wxpython-specialist`); checking the first. - Global: `f=~/.agents/skills/accessibility-lead/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/accessibility-lead/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `accessibility-lead`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/accessibility-agents ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add Community-Access/accessibility-agents -g -y ``` **Project:** ```bash npx skills add Community-Access/accessibility-agents -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Claude Code plugin route:** ``` /plugin marketplace add Community-Access/accessibility-agents /plugin install accessibility-agents@community-access ``` **Heads-up** - **License:** MIT <!-- das:install:end --> ## Invoke after install Describe the problem; six router skills pick the specialists and hand work to them by name, so install the whole package, not single skills. - Skill name: `accessibility-lead` — before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates - Skill name: `web-accessibility-wizard` — a full site or app audit rather than one change - Skill name: `document-accessibility-wizard` — Word, Excel, PowerPoint, PDF or ePub files - Skill name: `markdown-a11y-assistant` — markdown documentation - Skill name: `developer-hub` — Python, wxPython, desktop apps, NVDA add-ons, accessibility tooling - Skill name: `github-hub` — issues, pull requests, releases, projects, actions, security, teams, wikis - Trigger phrases: "accessibility agents", "Community Access", "PDF accessibility", "document accessibility", "accessibility lead" ## What it does Models forget accessibility while generating code; this package routes the work to the right specialist and merges the findings. The six routers dispatch many specialist, helper and reference skills (ARIA, keyboard, focus, forms, contrast, modals, live regions, tables, cognitive load, i18n, mobile, email, data visualisation, Office/PDF/ePub scanning, markdown audits) by name. Reports are rendered from structured findings rather than from memory. `npx skills add` installs the skills only. Upstream's extras (hooks that block edits to user-facing files until the accessibility lead has reviewed, plus an MCP server that supplies the scanners) come with the Claude Code plugin route or upstream's own `node scripts/install.mjs`. ## When NOT to use - Single-file audits where a lighter tool suffices — use `fixing-accessibility` - Quick contrast check only — use `color-expert` - A single WCAG 2.2 audit pass without the router and specialist machinery — use `wcag-audit-patterns`
© podo · MIT · podo/design-agent-skills