sdcorejs-review-accessibility-baseline

Perform a WCAG 2.1 Level AA accessibility audit by running automated probes like Lighthouse a11y, pa11y, and axe-core, then completing a manual POUR-mapped checklist to identify exact failure locations and SC references.

Your web UI fails keyboard navigation and screen reader checks due to missing semantics, focus traps, or broken focus order. A cross-track accessibility audit identifies these exact barriers using automated tools and manual verification.

axe-core and pa11y surface common automated failures, but they cannot catch all WCAG AA issues alone. You must also execute a manual verification plan covering screen reader announcements, keyboard order, and link meaning to ensure full compliance.

The best way to check WCAG 2.1 AA compliance pre-launch is running a cross-track baseline audit on the actual built page. This executes automated probes and 12 high-signal manual checks covering contrast, labels, errors, and reduced motion.

Lighthouse a11y works for post-overhaul regression checks by surfacing common accessibility failures. Combine it with pa11y, axe-core, and a manual POUR-mapped checklist to verify keyboard navigation and screen reader feedback remain intact.

Automated accessibility audit tools like axe-core and pa11y cannot detect manual failures such as focus traps, error announcements, or link meaning. They must be paired with a manual POUR-mapped checklist to identify all WCAG 2.1 Level AA barriers accurately.