Add keyboard shortcuts or keyboard navigation (Talon users)

Resolved 💬 2 comments Opened Apr 21, 2026 by Mark-Phillipson Closed Jul 1, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary: The app lacks keyboard shortcuts and full keyboard navigation/focus management, making it effectively unusable for keyboard-only and voice-control users (e.g., Talon). This blocks accessibility workflows and prevents power-user productivity.

Steps to reproduce:

  1. Open the app (web or desktop).
  2. Attempt to navigate using Tab/Shift+Tab, arrow keys, or common shortcuts (e.g., Ctrl/Cmd+K).
  3. Observe that focus is missing/unreliable and there are no keyboard shortcuts for common actions.

Expected:

  • Logical tab order and visible focus styles for all interactive elements.
  • A set of keyboard shortcuts (or configurable keybindings) for common actions.
  • Proper ARIA roles/labels and screen-reader compatibility.

Actual:

  • Many controls are only mouse-clickable; no documented or discoverable shortcuts; focus is difficult or impossible to reach.

Impact:

  • Blocks users relying on keyboard or voice-control (accessibility barrier).
  • Prevents automated/keyboard-driven workflows used by many developers.

Suggested fixes:

  • Add keyboard focusability and logical tab order.
  • Implement configurable keyboard shortcuts and document them.
  • Ensure ARIA roles, focus indicators, and screen-reader testing.
  • Add an accessibility/keyboard-mode for power users.

Labels: accessibility, a11y, keyboard-shortcuts, bug, accessibility-blocker

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #17552
  • #17530
  • #18207
  • #17114
  • #17350

Powered by Codex Action

etraut-openai contributor · 1 month ago

This feature request hasn't received enough upvotes, so it is being closed automatically. If you still feel this feature is needed, please open a new feature request with an updated title and description.