code-check-accessibility-regression

Catching accessibility regressions in changed UI requires scanning only the modified TSX or JSX files for missing accessible names, mis-associated form labels, and unsafe keyboard interactions. This targeted diff scan avoids whole-app noise and prioritizes high-severity findings.

A dialog focus trap check flags custom dialogs that may incorrectly trap keyboard focus, ensuring safe screen reader navigation. It skips Radix or shadcn-style primitives to avoid false positives on established component libraries.

Yes, the accessibility audit works with changed files only by running grep-style detectors on the JSX or TSX diff. This avoids whole-app noise and provides faster feedback by prioritizing high-severity semantic and interaction failures.

Common screen reader failures in React include mis-associated form labels, missing accessible names, and unlabeled errors. The audit detects these by scanning changed files for proper label and error associations to mitigate a11y regressions.

To ensure keyboard navigation works without false positives, the scan flags clickable non-interactive elements and missing focus handling while skipping Radix or shadcn-style primitives. This enforces keyboard-safe interactions on custom UI mutations.