How do you make a website ADA compliant with Claude Code?

ADA lawsuits target websites, and the technical yardstick courts use is WCAG. Claude Code can run that audit and fix the findings if you give it the right skills, starting with accessibility at 34,823 installs (skills.sh registry).

Key takeaways

• The accessibility skill by addyosmani leads the category with 34,823 installs and 2,470 GitHub stars (skills.sh registry, GitHub); the full field is ranked in the accessibility hub.
• ADA compliance for websites is judged against WCAG success criteria - the DOJ's own guidance points to WCAG as the reference standard (ada.gov).
• fixing-accessibility (14,306 installs, 3,598 stars) handles the remediation pass after the audit finds issues.
• accessibility-compliance (10,923 installs, 37,655 stars) turns the audit into a repeatable release gate.
• Anthropic ships its own reviewer: accessibility-review at 2,421 installs and 22,464 stars (skills.sh registry, GitHub).

What does ADA compliance actually require of a website?

The ADA itself names no technical standard for the web; in practice, US courts and the Department of Justice evaluate websites against WCAG, and the DOJ's small entity compliance guide points businesses to WCAG conformance. That makes the job concrete for developers: meet WCAG Level AA success criteria - perceivable, operable, understandable, robust - and document that you did. Everything below maps that requirement onto Claude Code skills.

What is the best skill for ADA and WCAG auditing?

accessibility by addyosmani is the best pick, with 34,823 installs and 2,470 GitHub stars (skills.sh registry, GitHub). Install it with:

npx skills add addyosmani/web-quality-skills

It audits pages against WCAG criteria - semantics, contrast, focus management, ARIA usage - and reports findings the way a human auditor would, per criterion. Strong alternatives: accessibility-compliance (10,923 installs) if you want the audit wired into an agent workflow, and Anthropic's accessibility-review (2,421 installs) for document and content review. The ranked list is on the best skills for frontend design pillar.

How do you fix the issues an audit finds?

Run a remediation skill against each finding rather than asking Claude Code to "make it accessible" in one shot. fixing-accessibility (14,306 installs, 3,598 stars, skills.sh registry, GitHub) is built for that loop: it takes a specific violation - missing labels, broken focus order, insufficient contrast - and patches the component without restyling it. Batching fixes per WCAG criterion keeps diffs reviewable and gives you the paper trail an ADA demand letter makes you wish you had.

How do you keep a site compliant after launch?

Make the audit a release gate, because compliance decays with every shipped feature. accessibility-compliance (10,923 installs, 37,655 stars) runs the check as part of an agent pipeline, and W3C's evaluation guidance recommends exactly this cadence: evaluate early, then re-evaluate on change. Teams that audit once a year discover a year of regressions at once. For component-level habits that prevent violations in the first place, the accessibility hub lists the adjacent skills.

Can automated checks alone make you ADA compliant?

No. Automated tooling catches the mechanical criteria - contrast ratios, missing alt text, label associations - but WCAG includes judgment calls like meaningful reading order and error-message clarity that need human review. The practical split: let skills like accessibility (34,823 installs) and accessibility-a11y (mindrally/skills, 2,157 installs) clear the mechanical layer, then spot-check flows with a keyboard and a screen reader. Skillselion lists 60,702 skills in its live catalog; the accessibility slice of the frontend design category is where the human-plus-agent workflow gets assembled.

A complete starter stack

• accessibility (34,823 installs) - the WCAG audit engine.
• fixing-accessibility (14,306 installs) - per-violation remediation.
• accessibility-compliance (10,923 installs) - the release gate.
• accessibility-review (2,421 installs) - content and document review from Anthropic.

Common pitfalls

• Auditing only the homepage - demand letters cite checkout flows, forms, and PDFs, which are exactly the pages teams skip.
• Fixing contrast with overlays or widgets instead of in the stylesheet; courts have seen the widget defense and it does not hold.
• Treating the audit as one-time - every feature release can regress focus order, and an annual audit finds a year of debt.

Audit against WCAG AA, fix per criterion, gate every release, and keep the records.

Common questions