Accessibility Compliance Accessibility Audit

This does what it says: runs accessibility audits against your web or mobile UI to catch WCAG compliance issues. You give it scope (which pages, which WCAG level, which user flows), and it walks through automated scans plus manual keyboard and screen reader checks, then maps findings to specific criteria with severity and remediation steps. It's built for teams that need to document compliance or fix barriers before launch, not just get general design feedback. The playbook resource suggests it has detailed procedures for tooling and retesting, which is helpful if you're setting up repeatable audit practices. Solid if accessibility is a hard requirement and you need structured findings, less useful if you're just curious whether your color contrast passes.

skills.sh installs: 513
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill accessibility-compliance-accessibility-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

Accessibility Audit and Testing

Assess the supplied pages and user journeys against the agreed WCAG edition and level. Record observed barriers, actual test coverage, remediation priorities and unresolved manual checks; automated scans alone do not establish conformance.

Use this skill when

Auditing web or mobile experiences for WCAG compliance
Identifying accessibility barriers and remediation priorities
Establishing ongoing accessibility testing practices
Preparing compliance evidence for stakeholders

Do not use this skill when

You only need a general UI design review without accessibility scope
The request is unrelated to user experience or compliance
You cannot access the UI, design artifacts, or content

Context

Combine automated evidence with keyboard, screen-reader, focus and contrast inspection in the actual target environment. Keep untested journeys and incomplete checks visible.

Requirements

Use the supplied WCAG edition/level, target pages and flows, authorized test environment, available audit tools and representative interaction states. Missing scope or UI access is an explicit limitation, not a passing audit.