diff --git a/docs/plans/2026-11-07-issue-4-keyboard-screen-reader-a11y.md b/docs/plans/2026-11-07-issue-4-keyboard-screen-reader-a11y.md new file mode 100644 index 0000000..18119d1 --- /dev/null +++ b/docs/plans/2026-11-07-issue-4-keyboard-screen-reader-a11y.md @@ -0,0 +1,65 @@ +# Plan: Layer toggles, stress slider, and feature popup are not keyboard or screen reader accessible (issue #4) + +Risk tier: Medium. Stateful UI interaction (focus management, keyboard events) that unit tests cover only in jsdom, and it alters existing behavior (popup now takes focus, Escape closes it). Changes are confined to two components, their tests, and one stylesheet, with no API or store contract change. + +Domain skills: +- superpowers:test-driven-development: invoke. +- chrome-devtools-mcp:a11y-debugging: invoke for the live drive (accessibility tree, focus, Tab order). +- vercel-react-best-practices: not applicable because no data fetching, bundle, or render performance work; one small focus effect only. +- frontend-design: not applicable because no new visual design; only focus indicators matching the existing accent token. +- dataviz, django, fastapi, expo, payments, email: not applicable because none of that is touched. + +## Acceptance criteria + +1. Every layer toggle (Airports, Sea Ports, and Heatmap when supported), the stress slider, and the popup close button are in the Tab order and operable from the keyboard: Space toggles a layer checkbox, arrow keys move the slider, Enter and Space activate the close button. +2. Each of those controls, and the popup dialog itself, shows a visible `:focus-visible` indicator (2px solid outline in `var(--accent)`, not clipped or covered by its container) that meets WCAG 2.4.7 and 2.4.11. `.stress-slider` no longer removes the focus indicator without replacement. +3. Accessible names and roles: each layer toggle is a native checkbox named "