Summary
The original 001-wcag-aa-compliance spec called for a "real-time dev feedback dashboard" — an overlay during dev that flags a11y violations live. Per the #21 next-session primer, this was deferred as "probably overkill for v0.0.x — defer to v0.1.0 or beyond."
Filing as a follow-up here so the work isn't forgotten when v0.1.0 (or a fork-driven need) makes it relevant.
Implementation sketch
- Dev-only useEffect in a high-level provider that runs
axe.run(document, { resultTypes: ['violations'] }) on a debounced timer or after each route change
- Floating panel in a corner of the viewport listing current violations with: rule name, target element selector, impact level, link to axe-rules docs
- Click-to-highlight: clicking a violation outlines the target element in the page
- Strictly dev-only —
process.env.NODE_ENV === 'development' gate; never bundles into production
Out of scope for v0.0.x
Refs
Summary
The original 001-wcag-aa-compliance spec called for a "real-time dev feedback dashboard" — an overlay during dev that flags a11y violations live. Per the #21 next-session primer, this was deferred as "probably overkill for v0.0.x — defer to v0.1.0 or beyond."
Filing as a follow-up here so the work isn't forgotten when v0.1.0 (or a fork-driven need) makes it relevant.
Implementation sketch
axe.run(document, { resultTypes: ['violations'] })on a debounced timer or after each route changeprocess.env.NODE_ENV === 'development'gate; never bundles into productionOut of scope for v0.0.x
Refs