accessibility-compliance-accessibility-audit — Claude Code skill
The accessibility-compliance-accessibility-audit skill audits pages and user journeys against a chosen WCAG scope. It helps find keyboard, screen-reader, focus, and contrast barriers before remediation is verified.
MIT 1 installs ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -a claude-codeWhat accessibility-compliance-accessibility-audit does
The skill reviews pages and user journeys against the WCAG edition and level supplied for the audit. It gathers baseline results from automated scans, then checks keyboard use, screen-reader behavior, focus order, and contrast in the target environment. Findings are linked to WCAG criteria, severity, and user impact.
The report keeps tested coverage, untouched journeys, and unfinished manual checks visible. After a fix, the skill guides a repeat test of the failed interaction. Detailed procedures are available in resources/implementation-playbook.md. Access to the UI, design artifacts, or content is required; missing access or scope limits the audit rather than proving conformance.
What it helps with
- audit pages against a declared WCAG level
- find barriers in keyboard-only navigation
- inspect focus order and visible focus
- map findings to WCAG criteria
- retest a failed journey after remediation
Example prompts for the agent
- Audit our checkout staging flow against WCAG 2.2 AA, including completion without a pointer.
- Check the target pages with keyboard navigation and a screen reader, then inspect focus order and contrast.
- Create an accessibility report with WCAG criteria, user impact, remediation steps, and retest coverage.
How to install accessibility-compliance-accessibility-audit
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -a claude-code2Manually: put the files in place
~/.claude/skills/accessibility-compliance-accessibility-audit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessibility-compliance-accessibility-audit/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -a codex2Manually: put the files in place
.agents/skills/accessibility-compliance-accessibility-audit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -a cursor2Manually: put the files in place
.cursor/skills/accessibility-compliance-accessibility-audit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/accessibility-compliance-accessibility-audit2Manually: put the files in place
.github/skills/accessibility-compliance-accessibility-audit/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/accessibility-compliance-accessibility-auditManually: put the files in place
.devin/skills/accessibility-compliance-accessibility-audit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -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-compliance-accessibility-audit
How do I install accessibility-compliance-accessibility-audit in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill accessibility-compliance-accessibility-audit -a claude-code, then check ~/.claude/skills/accessibility-compliance-accessibility-audit/SKILL.md.
What does accessibility-compliance-accessibility-audit do?
It reviews pages and user journeys within a declared WCAG scope. Automated scan results are combined with manual checks for keyboard access, screen readers, focus, and contrast, followed by remediation and retesting guidance.
What does this skill need before an audit?
Provide the WCAG edition and level, target pages and journeys, an authorized test environment, and access to the UI or content. A missing scope or inaccessible interface limits the audit.
Source text
SKILL.md · MIT
--- name: accessibility-compliance-accessibility-audit description: "Audit pages and user journeys against a declared WCAG scope. Use when identifying keyboard, screen-reader, focus or contrast barriers and planning verified remediation." risk: safe source: community date_added: "2026-02-27" --- # Accessibility Audit and Testing Assess the supplied pages and user journeys against the agreed WCAG edition and level. Record observed barriers, actual test coverage, remediation priorities and unresolved manual checks; automated scans alone do not establish conformance. ## Use this skill when - Auditing web or mobile experiences for WCAG compliance - Identifying accessibility barriers and remediation priorities - Establishing ongoing accessibility testing practices - Preparing compliance evidence for stakeholders ## Do not use this skill when - You only need a general UI design review without accessibility scope - The request is unrelated to user experience or compliance - You cannot access the UI, design artifacts, or content ## Context Combine automated evidence with keyboard, screen-reader, focus and contrast inspection in the actual target environment. Keep untested journeys and incomplete checks visible. ## Requirements Use the supplied WCAG edition/level, target pages and flows, authorized test environment, available audit tools and representative interaction states. Missing scope or UI access is an explicit limitation, not a passing audit. ## Instructions - Confirm scope (platforms, WCAG level, target pages, key user journeys). - Run automated scans to collect baseline violations and coverage gaps. - Perform manual checks (keyboard, screen reader, focus order, contrast). - Map findings to WCAG criteria, severity, and user impact. - Provide remediation steps and re-test after fixes. - If detailed procedures are required, open `resources/implementation-playbook.md`. ## Example **Request:** “Audit keyboard use in our checkout staging flow against WCAG 2.2 AA.” **Output:** Record the exact staging URL and states tested. Inspect tab order, visible focus, field labels, validation errors and checkout completion without a pointer. Link each observed barrier to the applicable criterion and evidence; mark screen-reader and unvisited-state checks as pending. Propose a fix and repeat the failed interaction after the authorized change. Do not call the whole product compliant from one successful scan. ## Resources - `resources/implementation-playbook.md` for detailed audit steps, tooling, and remediation examples. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills