accessibility-audit

To audit frontend code for WCAG 2.2 Level AA compliance, run the accessibility-audit skill to scan pages, components, and forms, identifying global, structural, and interactive barriers. It provides a structured checklist and remediation guidance.

An accessibility audit checks headings, images, color contrast, keyboard focus, ARIA roles, and semantic structure. This surfaces global, structural, and interactive barriers that prevent users with disabilities from accessing content effectively.

Yes, you can audit dynamic interactions and forms by applying the skill to frontend pages and components. It identifies interactive barriers and provides actionable remediation guidance to ensure WCAG 2.2 Level AA compliance.

The best way to fix accessibility issues is to follow the structured step-by-step remediation guidance provided by the audit. This plan helps you systematically address identified barriers and improve usability for all users.

You need a valid SKILL.md frontmatter with name and description to run the accessibility audit. The skill provides Quick Start instructions to begin scanning your project codebase immediately.

Run an accessibility audit before a launch to catch blockers that impact pass/fail status. Aligning with The A11Y Project checklist, the audit identifies WCAG 2.2 Level AA gaps to improve usability for all users.