A11y + Performance Audit
Goal
Catch and fix a11y/perf regressions that betray shallow implementations.
When to use
- •Before release.
- •After big UI changes.
- •Heavy motion/effects present.
Minimal inputs (ask only if missing)
- •Key flows.
Procedure (MUST)
- •a11y: keyboard, focus, labels, error messaging, contrast, reduced motion.
- •perf: remove heavy blur, avoid layout thrash, list strategy.
- •Document findings and fixes.
Outputs (MUST produce)
- •
docs/a11y_perf_audit.md. - •Implemented fixes.