Accessibility Engineering guides an agent through auditing an existing page or component for WCAG 2.2 AA conformance. It runs pinned axe-core and pa11y scans, adds keyboard, screen reader and visual checks by hand, and remediates each verified violation.
The skill treats automated results as a smoke test. A finding is confirmed in the browser before it is fixed, and the root cause in the markup is fixed before any ARIA is added.
What You Get
- A four-phase workflow: route new UI work elsewhere, run automated audit, test manually, fix violations
- A script that merges axe-core and pa11y results into one JSON report grouped by severity
- A manual checklist covering keyboard, screen reader, contrast, zoom, forced colors and focus visibility
- A verification checklist to confirm the work is finished
Common Use Cases
- Auditing a page before a release
- Triaging axe-core or pa11y output
- Fixing reported keyboard or screen reader problems
- Checking color contrast and touch target size
What Makes It Unique
The skill is scoped to auditing and remediation of existing interfaces and sends construction work to the frontend-ui-engineering skill. Its script pins tool versions and exits with an error when a scan fails, so a partial run is never reported as a clean pass. It also states that screen reader checks must name a browser and assistive technology pair or be recorded as untested.
Under The Hood
The SKILL.md loads when an accessibility audit is requested. The agent runs npx to fetch pinned versions of @axe-core/cli and pa11y and points them at a URL, usually a local dev server, which needs network access. The audit-a11y.sh script writes reports to a temporary folder, parses them with node and prints structured JSON. The skill links to a shared accessibility checklist and an auditor persona in the repository.