a11y-perf-audit

To audit UI components for accessibility and performance regressions, run a formal procedure that checks keyboard navigation, focus management, contrast, reduced motion, and expensive render paths. It outputs findings and recommended fixes published to docs/a11y_perf_audit.md.

An accessibility audit for UI components includes checks for keyboard navigation, focus management, labels, error messaging, contrast, and reduced motion. It identifies regressions in these areas and outputs recommended fixes in a formal markdown report.

To identify expensive renders and layout thrash in your UI, run a performance audit that detects list rendering inefficiencies and expensive render paths. It applies a formal procedure to document performance regressions and recommend fixes.

You should run an accessibility and performance audit on your UI before release and after major UI changes. This timing ensures new regressions in keyboard navigation, contrast, or expensive render paths are detected and fixed before users are impacted.

The a11y-perf-audit procedure requires no specific dependencies or components to run. It applies a formal procedure directly to your UI components to detect accessibility and performance regressions and output a markdown report.

The best way to document accessibility and performance fixes for reproducibility is to publish audit findings and applied changes to docs/a11y_perf_audit.md. This formal report guides implementation and ensures the workflow is reproducible.