audit-a11y

To check React components for WCAG AA contrast and screen-reader issues, a static analysis audit scopes the UI surface, detects missing ARIA patterns via grep, resolves theme tokens to compute contrast ratios, and reports structural defects for design review.

Fixing keyboard navigation and focus gaps in JSX routes involves scoping the audit surface, auto-correcting deterministic defects like converting clickable divs to buttons, and reporting complex focus-management issues around modals for manual resolution.

You can detect missing accessible names and input label associations without a browser by applying static reads and grep-based pattern matching to React/JSX structures to find problematic ARIA patterns and semantic gaps.

This accessibility audit does not use axe-core or browser engines, relying entirely on static analysis and grep-based pattern matching to evaluate ARIA patterns, keyboard semantics, and theme token contrast ratios.

You should avoid automated fixes for accessibility defects when problems are structural rather than deterministic, such as complex focus management around dialogs or contrast ratio failures, which require human design review decisions.

To audit a UI route for missing live-region attributes and keyboard reachability, provide the target file or surface, and the phased workflow scopes the audit surface, categorizes findings, applies safe deterministic fixes, and reports structural issues.