Add keyboard and focus handling to one interactive component
A component that works with a mouse and traps or ignores a keyboard, fixed and covered by a keyboard-path test.
The ticket
Make one interactive component fully operable by keyboard, with visible focus.
Acceptance criteria
- Every action is reachable and operable by keyboard alone
- Focus is visible at each step and never lost
- Focus order follows the visual order
- A test drives the component by keyboard from start to finish
What lands as proof
A keyboard-driven test plus a screenshot showing the focus indicator at each step.
Why teams defer it
- Everyone on the team uses a mouse, so the gap is invisible during normal work.
- Retrofitting keyboard support often means rebuilding the component on semantic elements, which is more than the ticket looks like.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: make one interactive component fully operable by keyboard, with visible focus. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means keyboard-path test and a focus-visible screenshot, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.