What do I need to use Accessibility Audit?

What is being audited; Description or image; Target WCAG level; Known assistive technology users?; Platform.

Is Accessibility Audit free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Accessibility Audit

Q: How do I know the Accessibility Audit output is good?

The skill verifies itself against its own quality checks: Issues are mapped to specific WCAG criteria; Every critical issue has a specific fix recommendation; Quick wins are separated from larger fixes; Effort estimates are included for prioritisation.

🔵 Stable🕐 updated 2026-06-08 🔷 SkillSpec L3 pm-design

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

📚 Based on WCAG 2.2 — W3C

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“Audit this design for accessibility”“Check WCAG compliance for [screen/component]”“Give me an a11y audit of [UI description]”“What accessibility issues does this design have?”

What to give it

▸What is being audited — screen, component, full product, design spec

▸Description or image — of the UI

▸Target WCAG level — A / AA / AAA — default to AA, which is the legal standard in most jurisdictions

▸Known assistive technology users? — Yes/No — if yes, which: screen reader / switch access / voice control / magnification

▸Platform — Web / iOS / Android / Desktop app

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Issues are mapped to specific WCAG criteria

✓Every critical issue has a specific fix recommendation

✓Quick wins are separated from larger fixes

✓Effort estimates are included for prioritisation

✓Testing recommendations are included

⚠️ What it refuses to do

Do not rely solely on automated scanning tools — automated checks catch ~30% of issues; manual keyboard and screen reader testing is required

Do not label an issue "minor" simply because it only affects a small percentage of users — for those users it may block all access

Do not add ARIA roles to fix broken semantics — use correct semantic HTML first; ARIA is a last resort

Do not confuse colour contrast of text with colour contrast of UI components — they have different minimum ratios (4.5:1 vs 3:1)

Do not audit only the happy path — error states, empty states, and loading states must also meet accessibility requirements

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="accessibility-audit"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Accessibility Audit is one of 1078 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog