Best Accessibility (a11y) Skills for Claude Code (2026)

Accessibility is no longer a post-launch checkbox - agent skills now let Claude Code audit contrast, focus traps, and WCAG violations while you write components. Below are the highest-install a11y skills, ranked by real catalog data, plus a starter stack. See the full ranked list on best skills for frontend design.

Key takeaways

• The most-installed accessibility-capable skill is web-design-guidelines (vercel-labs) at 390,234 installs and 27,714 GitHub stars (skills.sh registry, GitHub) - it folds an a11y pass into UI review.
• For dedicated WCAG work, accessibility by addyosmani has 28,341 installs (skills.sh registry, GitHub), the leading pure-a11y skill in the catalog.
• Skillselion catalogs 14,013 skills total, with 1,875 in the build/frontend subphase - so accessibility skills are a small but high-signal slice. Browse them via /design/accessibility.
• High-star authority signal: accessibility-compliance (wshobson) ships from a repo with 36,507 stars (skills.sh registry, GitHub).
• WCAG-specific pattern coverage exists too: wcag-audit-patterns (wshobson) has 8,299 installs (skills.sh registry, GitHub). Compare options on /design/ui-design.

What is the best accessibility skill for Claude Code?

The best all-round pick is web-design-guidelines by vercel-labs, with 390,234 installs and 27,714 stars (skills.sh, GitHub). It pulls Vercel's live Web Interface Guidelines on every run and returns accessibility, interaction, and consistency findings mapped to file:line, so a11y review folds into normal PR polish.

Install from vercel-labs/agent-skills.

If you want a skill built only for accessibility rather than broad UI review, the strongest alternatives are accessibility by addyosmani (28,341 installs, skills.sh, GitHub) and fixing-accessibility by ibelick (12,964 installs, skills.sh, GitHub). See where each ranks on the best skills for frontend design pillar.

Which skill enforces WCAG compliance specifically?

For explicit WCAG coverage, use accessibility-compliance by wshobson (10,088 installs, from a 36,507-star repo, skills.sh, GitHub) or its sibling wcag-audit-patterns (8,299 installs, skills.sh, GitHub). Both target the Web Content Accessibility Guidelines - the W3C standard for contrast ratios, keyboard operability, and semantic structure (W3C WAI).

WCAG matters because it is the reference most legal and procurement requirements cite, and it maps cleanly to checkable rules like 4.5:1 text contrast and visible focus indicators. Both wshobson skills install from wshobson/agents, and their shared 36,507-star repo (skills.sh, GitHub) signals heavy real-world use - a useful proxy for trustworthiness when picking between similar skills.

What is the difference between auditing and fixing accessibility?

Auditing skills report violations; fixing skills change code. The audit camp includes audit by pbakaus (82,727 installs, skills.sh, GitHub), which scores accessibility, performance, theming, and responsive layout with P0-P3 severities and does not auto-edit. The fix camp includes fixing-accessibility by ibelick (12,964 installs, skills.sh, GitHub), which applies corrections like missing labels, ARIA roles, and contrast.

Answer-first rule of thumb: audit before a release gate, fix during a polish sprint. Pair them - run the audit, then let the fixer resolve the P0s. The audit skill's 82,727 installs versus the fixer's 12,964 (skills.sh, GitHub) suggests most teams reach for reporting first and only add automated fixing once they trust the findings. Both surface on /design/accessibility.

Are there accessibility skills for mobile and Flutter?

Yes. flutter-improving-accessibility by flutter has 8,416 installs (skills.sh, GitHub) and comes from the official Flutter org's flutter/skills repo. It targets semantic labels, contrast, and screen-reader support in Flutter widgets rather than web DOM.

For web, accessibility hangs on correct semantic HTML and ARIA, documented in the MDN accessibility guide. For Flutter, the same intent maps onto the Semantics widget tree instead. Explore more frontend skills under /category/frontend-design.

A complete starter stack

1. web-design-guidelines (vercel-labs, 390,234 installs) - broad UI + a11y review on every PR. 2. accessibility (addyosmani, 28,341 installs) - dedicated WCAG-focused audit. 3. accessibility-compliance (wshobson, 10,088 installs) - compliance-grade WCAG enforcement. 4. fixing-accessibility (ibelick, 12,964 installs) - applies the fixes, not just findings. 5. audit (pbakaus, 82,727 installs) - scored pre-ship quality gate including a11y.

Common pitfalls

• Auditing without fixing. A scored report changes nothing until someone resolves the P0s - pair an audit skill with a fixer.
• Treating a UI-review skill as full WCAG coverage. web-design-guidelines is excellent but broad; add a WCAG-specific skill like accessibility-compliance for compliance work.
• Skipping keyboard and screen-reader testing. Skills catch contrast and labels, but real focus-order and screen-reader bugs need a manual pass against W3C WAI.

Start with web-design-guidelines for everyday review, then layer a dedicated WCAG skill when compliance is on the line - see the full ranking on best skills for frontend design.

Common questions