AI Skill MartBrowse skillsPromptsProgramsLearnWhat is a Skill?
 
← Back to list

Web Accessibility (a11y) Audit

Audits and fixes web accessibility against WCAG 2.2 with an evidence-led Lighthouse + keyboard workflow.

Design & UIIntermediate★ 3,057⑂ 266AI score 9/10Last updated: Aug 24, 2026

What it does

  • Evidence-led audit loop: run a live Lighthouse accessibility audit (lighthouse_audit via Chrome DevTools MCP), use failing rendered nodes to localize the offending component, fix the source, then re-run the same audit.
  • Accessibility-tree review: inspect names, roles, states, landmarks and heading structure with take_snapshot, plus manual keyboard walkthroughs of the affected flow.
  • WCAG 2.2 coverage: POUR principles, A/AA/AAA levels, alt text patterns, a contrast ratio table, :focus-visible, focus-not-obscured (2.4.11), 24×24px target size (2.5.8), dragging alternatives (2.5.7), redundant entry (3.3.7) and accessible authentication (3.3.8) — each with code snippets.
  • Testing kit: npx lighthouse, axe CLI commands, a manual checklist (VoiceOver/NVDA/TalkBack, 200% zoom, high contrast, reduced motion) and issues ranked critical/serious/moderate.

Who it's for

  • Front-end developers who need to fix real a11y defects in code, not just read guidelines
  • Teams under legal WCAG AA obligations (government, finance, education, e-commerce)
  • Designers and QA who want contrast, focus and touch-target rules with concrete thresholds

Example uses

  1. "Run an a11y audit on this page" → Lighthouse run, failing nodes mapped to components, patches for missing alt text and low contrast.
  2. "Keyboard users get trapped in our modal" → apply the focus-trap pattern or switch to the native <dialog> element.
  3. "Does our login meet WCAG 2.2?" → checks paste-enabled password fields, passkey/email-link alternatives (3.3.8) and redundant entry (3.3.7).

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/addyosmani/web-quality-skills/HEAD/skills/accessibility/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on AI Skill Mart.
Copy the skills/accessibility folder from the GitHub repo addyosmani/web-quality-skills into my ~/.claude/skills/accessibility/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/addyosmani/web-quality-skills.git /tmp/web-quality-skills && mkdir -p ~/.claude/skills && cp -r /tmp/web-quality-skills/skills/accessibility ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/addyosmani/web-quality-skills.git
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r web-quality-skills/skills/accessibility ~/.claude/skills/
  5. Confirm the references/ folder (A11Y-PATTERNS.md, WCAG.md) came along — the guide links to those files.
  6. Restart Claude Code and try a prompt like "do an a11y audit of this page" or "make this component keyboard accessible".
  7. Optional: for live audits, connect Chrome DevTools MCP, or install tooling with npm i -g @axe-core/cli and use npx lighthouse.
View source on GitHub ↗License: MIT