Add keyboard shortcuts or keyboard navigation (Talon users)
Resolved 💬 2 comments Opened Apr 21, 2026 by Mark-Phillipson Closed Jul 1, 2026
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:
- Open the app (web or desktop).
- Attempt to navigate using Tab/Shift+Tab, arrow keys, or common shortcuts (e.g., Ctrl/Cmd+K).
- 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
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗