accessibility-audit

To run an automated accessibility audit, configure the skill with explicit selectors and mode flags, define your target scope via sitemap or route list, and execute static checks, APCA contrast measurements, and axe-core WCAG scans.

APCA contrast measurement is a perceptual contrast algorithm used for accessibility audits to assess light and dark theme legibility across multiple UI surfaces, replacing traditional ratio calculations with perceptual accuracy.

Yes, the accessibility audit supports CI pipeline integration by producing a structured backlog with remediation guidance, allowing teams to automatically catch and resolve accessibility gaps during the development lifecycle.

Yes, you can scan specific routes by defining your target scope with a route list instead of a full sitemap, allowing the axe-core WCAG scan to tailor the accessibility audit to your specific project environment.

Static mode enforces naming and semantic HTML via A1-A8 checks, full mode combines static checks with APCA contrast and live axe-core scans, and wcag mode focuses exclusively on live axe-core WCAG scans with configurable rulesets.

Automated accessibility audits require explicit selectors and mode flags for configuration, meaning they cannot dynamically discover application states and must rely on a predefined target scope defined by sitemap or route list.