Development & Code COMMUNITY New

Accessibility

You let Claude audit your website against WCAG 2.2 and fix the barriers it finds directly in the source code, followed by a fresh check.

Level ●● Intermediate
Saves manual lookup of WCAG criteria and the search for affected components
Version v2.0
Updated 2026-11-13
Available in: claude-codecoworkclaude-desktop

What is Accessibility?

Accessibility is a skill for Claude that audits and improves the accessibility of web interfaces according to WCAG 2.2. It builds on the four WCAG principles perceivable, operable, understandable and robust, and on the Lighthouse accessibility audits. For each topic it provides code examples with a broken and a corrected version, covering alt text, color contrast, focus styles, keyboard access, captions and reduced motion.

When a rendered page is available, the skill starts with a Lighthouse audit, using 'lighthouse_audit' when Chrome DevTools MCP is present. Failed audit nodes tell it which component or template is affected. It then reads the accessibility tree via 'take_snapshot' for names, roles, states and headings, walks through the flow with the keyboard, fixes the source and runs the check again. Without these tools it falls back to Lighthouse CLI or axe.

The skill suits frontend teams, agencies and anyone who needs to bring web projects to conformance level AA, which the skill describes as a legal requirement in many jurisdictions. For live audits you need a rendered page and ideally Chrome DevTools MCP. The skill makes clear that automated tools only catch part of the barriers and that a Lighthouse score of 100 does not mean WCAG conformance.

Who it is for

Frontend developers, agencies and product teams who want to build and audit web interfaces against WCAG 2.2 with fewer barriers.

Use cases

  • Before a relaunch you have the home page and forms checked for missing alt text, weak contrast and keyboard traps.
  • A client requires WCAG AA conformance, and you want to fix the findings per component in a traceable way.
  • After a design update you verify that focus outlines, skip links and modal dialogs still work with the keyboard.

What Accessibility does

Evidence-based audit workflow

Lighthouse audit, narrowing down via failed audit nodes, accessibility tree snapshot, keyboard test, fix in the source and a repeat of the same checks.

Chrome DevTools MCP integration

With Chrome DevTools MCP the skill uses 'lighthouse_audit' for the audit and 'take_snapshot' for the accessibility tree, with snapshot mode for logged-in sessions.

WCAG 2.2 quick reference

A reference file lists the success criteria by level A, AA and AAA, including the criteria new in version 2.2 on obscured focus, target size and dragging movements.

Copy-ready code patterns

Ready-made patterns for focus trapping in modal dialogs and for skip links, plus guidance on the native dialog element and visible focus outlines.

Contrast and target sizes

Tables with minimum contrast ratios for AA and AAA and the rule of 24 by 24 CSS pixels for interactive targets, with 44 by 44 as a comfortable recommendation.

Say this to activate the skill

"Run an a11y audit on this page.""Check my site for WCAG compliance.""Improve keyboard navigation in this form.""Make this component accessible for screen readers."

Install

npx skills add addyosmani/web-quality-skills --skill accessibility

The command installs the original version from the author's repository (Vercel skills CLI, needs Node.js), add -g for all projects. We do not host a copy: updates come straight from the author. Need help with setup? How to install skills →

Figures with source and date

GitHub stars
≈ 3,100
Installs
69,884
On skills.sh since
20 Jan 2026
Last change in the repository
24 Aug 2026
Licence
MIT

As of 13 Nov 2026. Sources: GitHub, skills.sh. The figures change daily; we show the state of our last lookup.

Checked automatically

Version 2.0, checked on 13 Nov 2026.

  • Automated check on 2026-11-13 (revision afa8da9): 3 files in the skill folder read by pattern search. It found no hidden characters, no instructions to override rules, no download-and-run and no access to credentials.

Independent checks on skills.sh, as of 13 Nov 2026

Gen Agent Trust Hub Pass
Socket Pass
Snyk Pass

Full results on skills.sh ↗

Good to know

  • Live audits require a rendered page. Without Chrome DevTools MCP the skill falls back to Lighthouse CLI or axe.
  • According to the skill, a Lighthouse score of 100 does not prove WCAG conformance, so manual keyboard testing is still needed.
  • The check is an automated pattern search, not a security guarantee, and reads the skill folder only. The command always installs the author's current version; later versions have not been reviewed by us.

Frequently asked questions about Accessibility

What is Accessibility?

Accessibility is a skill for Claude that audits web pages for barriers based on WCAG 2.2 and the Lighthouse audits and applies fixes in the source code. It comes from the web-quality-skills repository by addyosmani.

How do I install Accessibility?

You install Accessibility with the command 'npx skills add addyosmani/web-quality-skills --skill accessibility'. Claude then uses the skill when you ask for an a11y audit or WCAG compliance, for example.

Is Accessibility free?

Accessibility is released under the MIT license. You can use, adapt and include the skill in your own projects freely.

Who is Accessibility for?

Accessibility is for anyone building websites or web apps who needs to find and fix barriers according to WCAG 2.2, such as frontend teams, agencies and product teams with AA requirements.

Does Accessibility replace a manual audit?

No, Accessibility does not replace a full audit. The skill itself notes that automated tools only detect part of the barriers, so it combines them with keyboard tests and a look at the accessibility tree.

Which tools does Accessibility use?

Accessibility works preferably with Chrome DevTools MCP and its 'lighthouse_audit' and 'take_snapshot' functions. If these are not available, the skill uses Lighthouse CLI or axe and runs the same manual checks.

Share this skill

About this skill

Accessibility comes from addyosmani and is an open-source project maintained by its author and community.

Author: addyosmani / github.com. Source: github.com/addyosmani/web-quality-skills/tree/main/skills/accessibility. Licence: MIT.

Curated by Collective Brain, an AI and automation digital agency from Hamburg, together with WhiteFox Automations. More vetted skills in the skills catalog.

Working in Germany, Austria or Switzerland? We help teams roll out Claude, in English or German.

Want this skill tailored to your team?

Accessibility is a strong starting point. A skill gets really powerful once it knows your workflows, templates and tone of voice. We build custom skills for teams, from analysis to rollout, and connect them to our work in AI consulting.

Request a custom skill →