hatch3r-a11y-audit

You can run a WCAG AA accessibility audit by executing automated axe-core scans alongside manual checklist verification to identify and categorize usability barriers across keyboard navigation, contrast, ARIA semantics, and screen-reader support.

An automated axe-core accessibility scan checks for WCAG criteria violations and records them with severity mapping, identifying critical and major issues that require remediation across your web application routes and key components.

Automated accessibility testing cannot reliably catch all keyboard navigation and reduced motion issues, so a manual WCAG checklist audit is required to validate focus behavior, reduced-motion handling, and high-contrast support end-to-end.

To fix and verify WCAG AA accessibility violations, prioritize critical and major findings, implement remediations, and re-check using both automated axe scans and manual category-based verification steps until clean results are achieved.

You need manual WCAG checklist auditing alongside automated scans when validating requirements not reliably caught by automation, such as keyboard focus behavior, reduced-motion handling, and high-contrast support across application routes.

The definition of done for a WCAG AA accessibility audit requires clean critical and major automated axe scan results plus fully completed manual verification across all category-based checks for keyboard, contrast, ARIA, motion, and screen-reader behaviors.