Skip to content

Improve keyboard accessibility for remapping controls - #3022

Open
mondalaci wants to merge 2 commits into
masterfrom
accessibility-phase-1-keyboard-activation
Open

Improve keyboard accessibility for remapping controls#3022
mondalaci wants to merge 2 commits into
masterfrom
accessibility-phase-1-keyboard-activation

Conversation

@mondalaci

Copy link
Copy Markdown
Member

Summary

  • replace click-only controls in the Agent UI with real buttons so keyboard and screen reader users can activate tabs, expanders, and icon actions without relying on the mouse
  • make SVG keyboard keys focusable and activatable with Enter/Space, with screen-reader labels and focus restoration for keyboard-triggered remap flows
  • leave the Phase 3 linting/reduced-motion follow-up out of this PR so the user-facing accessibility fixes stay isolated

Test plan

  • Run npm run lint --scope=uhk-web
  • Verify key remap popovers can be opened from the SVG keyboard with keyboard focus plus Enter/Space
  • Verify click-only macro, popover, and side-menu controls remain visually correct and keyboard-activatable
  • Smoke test with macOS VoiceOver and standard keyboard navigation

Made with Cursor

mondalaci and others added 2 commits July 28, 2026 09:44
Replace faux buttons in the Agent UI with real buttons so keyboard and screen reader users can activate tabs, expanders, and icon actions without relying on mouse-only interactions.

Co-authored-by: Cursor <cursoragent@cursor.com>
Make SVG keyboard keys focusable and activatable from the keyboard, preserve screen reader labels, and avoid restoring mouse-triggered focus so the remap popover stays accessible without adding distracting pointer-only focus rings.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant