Web Accessibility Wizard
Guided WCAG 2.2 audit of a web app or site, phase by phase, with severity scores, a written report and optional fixes.
Install
/plugin marketplace add Community-Access/accessibility-agentsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Community-Access/accessibility-agents --skill web-accessibility-wizardgit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/web-accessibility-wizard ~/.claude/skills/web-accessibility-wizardPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
You run a full, guided accessibility audit of a web application and produce a scored report someone can act on. You are the long form; `accessibility-lead` is the short form for a single change. Web content only: Office and PDF files go to `document-accessibility-wizard`, markdown to `markdown-a11y-assistant`. ## Ask before you scan Do not start scanning. Run Phase 0 first and get answers. An audit aimed at the wrong pages, the wrong framework or the wrong conformance target wastes the whole run. `references/phase-0-discovery.md` has the questions and the framework-specific follow-ups; page discovery, crawling and the axe CLI commands are in `kb-web-scanning`. If the scanner tools are not available, ask for the results from axe or Accessibility Insights, use only what you are given, and never say you scanned, ran or opened anything you did not. ## Phases Read the reference for a phase when you reach it, not before. | Phase | What happens | Read | |---|---|---| | 0 | Discovery: scope, framework, conformance target, tooling present | `references/phase-0-discovery.md` | | 1 to 8 | Domain checks, one specialist each, dispatched in parallel | `references/phases-1-8-domain-checks.md` | | 9 to 10 | Testing advice, severity scoring, behavioural testing with Playwright | `references/phases-9-10-testing.md` | | 11 | Report, scorecard and handoffs | `references/phase-11-report-template.md` |
Details
- Skill name
web-accessibility-wizard- Repository
- Community-Access/accessibility-agents
- Path
skills/web-accessibility-wizard/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Web Accessibility Wizard skill do?
Guided WCAG 2.2 audit of a web app or site, phase by phase, with severity scores, a written report and optional fixes.
How do I install the Web Accessibility Wizard skill?
Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Web Accessibility Wizard popular?
It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.
Related skills
A11y Core
449Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.
A11y Tool Builder
449Community-Access/accessibility-agents
Build accessibility scanners, rule engines, parsers and report generators.
Accessibility Lead
449Community-Access/accessibility-agents
Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.
Web Component Specialist
449Community-Access/accessibility-agents
Custom elements and shadow DOM: ElementInternals, cross-shadow ARIA, focus.
Performance Accessibility
449Community-Access/accessibility-agents
Lazy loading, skeletons, layout shift and loading states for AT users.
Web Issue Fixer
449Community-Access/accessibility-agents
Internal helper: apply approved web accessibility fixes to source.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.