Agent skill · data analytics · sickn33
accessibility-compliance-accessibility-audit
Audit pages and user journeys against a declared WCAG scope. Use when identifying keyboard, screen-reader, focus or contrast barriers and planning verified remediation.
Why this skill is useful
Provides domain-specific knowledge on WCAG compliance and detailed remediation strategies that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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. Instructions Confirm scope (platforms, WCAG level, target pages, key user journeys). Run automated scans to collect baseline violations and coverage gaps. Perform manual checks (keyboard, screen reader, focus order, contrast). Map findings to WCAG criteria, severity, and user impact. Provide remediation steps and re-test after fixes. If detailed procedures are required, open resources/implementation-playbook.md. Example Request: “Audit keyboard use in our checkout staging flow against WCAG 2.2 AA.” Output: Record the exact staging URL and states tested. Inspect tab order, visible focus, field labels, validation errors and checkout completion without a pointer. Link each observed barrier to the applicable criterion and evidence; mark screen-reader and unvisited-state checks as pending. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/accessibility-compliance-accessibility-audit--a6341f