wcag-ai-skill — Claude Code skill: what it does, how to install
The wcag-ai-skill skill turns WCAG 2.2 criteria into working guidance for design, implementation, accessibility checks, remediation, and conformance docs. Use it across a project’s accessibility workflow.
MIT 244 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill wcag-ai-skill -a claude-codeWhat wcag-ai-skill does
The skill helps teams apply WCAG 2.2 from design through reporting. Ask for design requirements or implementation guidance, review content, plan accessibility tests, map out fixes, or draft conformance documentation. It produces guidance, requirements, acceptance criteria, and test plans. It does not generate ready-to-use components or provide legal certification.
Its scope goes beyond an audit or a single accessibility check. It covers the workflow from setting requirements to documenting conformance, unlike wcag-audit-patterns, which focuses on auditing and testing. The skill supports Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
For Claude Code, run npx skills add podo/design-agent-skills --skill wcag-ai-skill -a claude-code. The installed file is at ~/.claude/skills/wcag-ai-skill/SKILL.md. A quick contrast check is outside its focus, so this is a broader tool than that task requires.
What it helps with
- turn WCAG 2.2 criteria into web design requirements
- write acceptance criteria for frontend implementation
- review content against accessibility requirements
- plan accessibility testing and remediation
- prepare WCAG conformance documentation
Example prompts for the agent
- Draft WCAG 2.2 requirements for a new sign-up form.
- Create an accessibility test plan and acceptance criteria for this page.
- Turn these accessibility findings into a remediation plan and conformance docs.
How to install wcag-ai-skill
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill wcag-ai-skill -a claude-code2Manually: put the files in place
~/.claude/skills/wcag-ai-skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wcag-ai-skill/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill wcag-ai-skill -a codex2Manually: put the files in place
.agents/skills/wcag-ai-skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill wcag-ai-skill -a cursor2Manually: put the files in place
.cursor/skills/wcag-ai-skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/wcag-ai-skill2Manually: put the files in place
.github/skills/wcag-ai-skill/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill wcag-ai-skill -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/wcag-ai-skillManually: put the files in place
.devin/skills/wcag-ai-skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill wcag-ai-skill -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 wcag-ai-skill
How do I install wcag-ai-skill in Claude Code?
Run npx skills add podo/design-agent-skills --skill wcag-ai-skill -a claude-code. The skill file will be at ~/.claude/skills/wcag-ai-skill/SKILL.md.
What does wcag-ai-skill do?
It turns WCAG 2.2 criteria into guidance for design, frontend implementation, and content review. It can also help plan tests and fixes, and prepare conformance documentation.
Does wcag-ai-skill provide components or legal certification?
No. It produces guidance, requirements, acceptance criteria, and test plans; it does not supply ready-made components or legal certification.
Source text
SKILL.md · MIT
--- name: wcag-ai-skill description: | Turns WCAG 2.2 into practical guidance for web design, frontend implementation, content review, accessibility QA, remediation planning, and conformance documentation. Different focus from wcag-audit-patterns — covers the full WCAG guidance workflow from design through documentation. triggers: - "WCAG 2.2 guidance" - "wcag-ai-skill" - "Raze Systems" - "WCAG conformance docs" - "accessibility remediation" das: type: skill category: accessibility-quality upstream: "https://github.com/Raze-Systems/wcag-ai-skill" upstream_path: ".agents/skills/wcag-2.2/SKILL.md" version: latest --- # wcag-ai-skill > Catalogue stub — full skill: [Raze-Systems/wcag-ai-skill](https://github.com/Raze-Systems/wcag-ai-skill) <!-- 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?** Upstream names this skill `wcag-22`, so it installs next to this pointer (the pointer is not replaced). - Global: `f=~/.agents/skills/wcag-22/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/wcag-22/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `wcag-22`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/wcag-ai-skill ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add Raze-Systems/wcag-ai-skill --skill wcag-22 -g -y ``` **Project:** ```bash npx skills add Raze-Systems/wcag-ai-skill --skill wcag-22 -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Heads-up** - **License:** AGPL-3.0 (copyleft; stated in the README and SKILL.md, the repo has no LICENSE file) <!-- das:install:end --> ## Invoke after install - Skill name: `wcag-22` - Trigger phrases: "WCAG 2.2 guidance", "Raze Systems", "WCAG conformance docs", "accessibility remediation" ## What it does Translates WCAG 2.2 success criteria into practical, actionable guidance across the full accessibility workflow: web design (what to spec), frontend implementation (how to code it), content review (what writers need to know), accessibility QA (how to test), remediation planning (how to fix issues), and conformance documentation (how to report). It produces guidelines, requirements, acceptance criteria, and test plans, not ready-made components or legal certification. Different from `wcag-audit-patterns`, which focuses on the audit/testing phase. ## When NOT to use - Quick contrast checks — use `fixing-accessibility` for targeted color contrast fixes - Automated Lighthouse-style performance audits — use `addyosmani-quality`
© podo · MIT · podo/design-agent-skills