Skip to main content
skill CX Codex

accessibility-audit · owl-listener — Claude Code skill: WCAG audits

Audits an existing interface against WCAG and reports issues with severity, impact, and remediation steps.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code
Open on GitHub

What accessibility-audit does

This skill audits an existing design or implementation against WCAG 2.2. It looks for barriers related to perception, keyboard access, predictable behaviour, semantic markup, and ARIA.

Each finding includes a description, interface location, WCAG criterion, severity, impact, remediation steps, and code examples. Issues use the Critical, Major, Minor, and Enhancement ratings.

Check static and interactive states across devices and browsers, then test with assistive technologies. This skill is the wrong choice for planning future sessions with disabled users; use accessibility-test-plan instead.

What it helps with

  • find access barriers in an existing interface
  • rate the severity of WCAG issues
  • link an issue to its WCAG criterion
  • prepare remediation steps with code examples
  • review interface states for assistive technology

Example prompts for the agent

  • Run accessibility-audit on the current interface and list WCAG issues.
  • Use accessibility-audit on this form, including severity and remediation steps.
  • Audit the page's interactive states with accessibility-audit.

How to install accessibility-audit

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code

2Manually: put the files in place

~/.claude/skills/accessibility-audit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/accessibility-audit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about accessibility-audit

How do I install accessibility-audit in Claude Code?

Run npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code, then run npx skills add Owl-Listener/designer-skills --skill accessibility-audit -a claude-code again. The skill file is at ~/.claude/skills/accessibility-audit/SKILL.md.

What does accessibility-audit do?

It audits an existing interface against WCAG 2.2. The report includes issue details, impact, severity, remediation steps, and code examples.

Is accessibility-audit for planning assistive-technology research sessions?

No. Use accessibility-test-plan when planning future sessions with disabled users.

Source text

SKILL.md · MIT
---
name: accessibility-audit
description: Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
---
# Accessibility Audit
You are an expert in digital accessibility, WCAG guidelines, and inclusive design.
## What You Do
You conduct thorough accessibility audits identifying barriers and providing remediation guidance.
## WCAG 2.2 Principles (POUR)
- **Perceivable**: Text alternatives, captions, adaptable content, color contrast
- **Operable**: Keyboard access, time limits, no seizures, navigation, input modalities
- **Understandable**: Readable, predictable, input assistance
- **Robust**: Assistive tech compatibility, semantic markup, ARIA
## Severity Ratings
1. Critical — blocks access entirely
2. Major — significant difficulty
3. Minor — inconvenience with workarounds
4. Enhancement — beyond compliance improvement
## Issue Format
Description, location, WCAG criterion, severity, impact, remediation steps, code examples.
## Best Practices
- Test with real assistive technologies
- Include users with disabilities when possible
- Audit across devices and browsers
- Check static and interactive states
- Prioritize by severity and user impact

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Frontend and UI →

accessibility-audit by other authors comes first.

From the same set111

theming-system Designs a three-layer token architecture to support brand variants, color modes, and interface density in a single component library. CX Codex +1 2,100installs journey-map This skill maps one persona's end-to-end experience: stages, touchpoints, emotions and pain points. Useful when you're improving something that already exists. CX Codex +1 2,100installs component-spec This skill writes a full spec for one design-system component: anatomy, variants, states, accessibility and usage rules. Useful when a library grows and the API needs pinning down. CX Codex +1 2,100installs design-principles Helps teams define actionable design principles to resolve recurring product debates. Useful when the same decisions keep getting relitigated. CX Codex +1 2,100installs ux-writing Writes microcopy, error messages, empty states and CTAs. Useful when the words themselves are the deliverable. CX Codex +1 2,200installs critique-typography Audits typography on a rendered screen: scale usage, readability, consistency and token compliance. Useful during UI review. CX Codex +1 2,000installs version-control-strategy Defines version control strategies for design files, component libraries, and tokens. It helps teams stop chaotic file history and establish clear release routines. CX Codex +1 2,000installs critique-visual-hierarchy This skill reviews a rendered screen across four dimensions and tells you where the eye actually lands. Useful when attention goes to the wrong place. CX Codex +1 2,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor