Keyboard shortcut

Problem Context

• Users repeat commands such as save, search, copy, format, open command palette, move focus, toggle panels, archive, export, or run tools.
• The product runs inside browsers, operating systems, text editors, assistive technologies, and international keyboard layouts that already own many key combinations.
• Commands may be global, page-scoped, editor-scoped, object-scoped, modal-scoped, or active only while a component has focus.
• Some users rely on keyboard-only work, switch control, screen readers, speech input, touch keyboards, remapped hardware keys, or platform shortcuts.

Selection Rules

• Choose keyboard shortcut when the design problem is accelerating one known command with a key combination, not helping users discover commands.
• Use command palette when users need searchable command discovery, ranking, recents, scope filtering, or fuzzy matching before execution.
• Use menu menubar when command organization, submenu hierarchy, disabled or checked state, and persistent desktop-style command grouping are the main concerns.
• Use toolbar when visible repeated commands near a view or selection matter more than memorized activation.
• Use undo or redo when the pattern is about edit-history semantics; keyboard shortcuts can invoke them but do not define their history behavior.
• Use focus traversal when the problem is predictable Tab order, roving focus, landmarks, or moving through interactive elements rather than executing commands.
• Prefer modifier chords for global commands and reserve single-character shortcuts for focused components or user-configurable expert modes.
• Provide visible alternatives for every primary workflow and every non-essential shortcut outcome.
• Avoid overriding browser, operating-system, assistive-technology, text-editing, and common platform shortcuts unless the app has a strong editor-like reason and a recovery path.
• Require confirmation, preview, undo, or delayed execution for shortcuts that delete, publish, send, spend money, change permissions, or affect other people.

Required States

• Visible command with shortcut hint.
• Shortcut help or command list state showing command name, key chord, platform variant, and scope.
• Global shortcut active state.
• Focused-component shortcut active state.
• Text field or editable-content suppression state.
• Enabled command state and disabled shortcut state with reason.
• Conflict detected state with browser, operating system, assistive technology, product, or custom shortcut map.
• Shortcut executed state with status feedback and focus preservation.
• Risky shortcut confirmation, preview, or undo state.
• Remap shortcut state and restore default state.
• Character-key shortcut off or focus-only state.
• International keyboard layout or platform variant state.
• Mobile or touch-keyboard state where shortcuts are supplemental and visible controls remain primary.

Interaction Contract

• A shortcut maps to one named command, focus target, or mode and uses the same command handler as visible controls.
• The key chord is platform-aware and formatted consistently wherever the command appears.
• The shortcut fires only in its declared scope and never while text entry, composition, screen reader commands, or browser-reserved behavior should own the key event.
• When the command is disabled, the shortcut is disabled too and the disabled reason is available through the same visible command surface.
• Shortcut activation reports success, pending, failure, undo, confirmation required, or conflict using visible and accessible status messaging.
• Shortcut hints, help, menus, toolbars, and command palette rows stay synchronized with the same command registry.
• Users can turn off, remap, or focus-scope single-character shortcuts that are implemented in web content.
• Risky shortcuts do not bypass review, confirmation, permissions, rate limits, or audit requirements.

Implementation Checklist

• Inventory commands and classify each shortcut by command name, scope, platform chord, risk level, visible fallback, disabled condition, and owner.
• Build shortcuts from a central command registry so menus, toolbars, command palette rows, help pages, and keyboard handlers share one source of truth.
• Check conflicts against browser shortcuts, operating-system shortcuts, screen reader commands, text-editing commands, composition events, and existing product shortcuts.
• Suppress global shortcuts inside inputs, textareas, contenteditable regions, combo boxes, and editing modes unless the shortcut is explicitly owned by that component.
• Expose shortcuts through visible hints, shortcut help, command rows, aria-keyshortcuts where appropriate, and onboarding only for frequent expert accelerators.
• Provide remapping, disable, or focus-only options for single-character shortcuts and preserve user settings across sessions.
• Route destructive, expensive, permission-changing, or external-side-effect shortcuts through confirmation, preview, undo, or approval workflows.
• Test Windows, macOS, Linux, browser variants, screen readers, speech input, international layouts, hardware keyboards on tablets, mobile fallback, high zoom, and focus return.

Common Generated-UI Mistakes

• Making a shortcut the only path to a primary command.
• Binding single-letter global shortcuts that fire during typing, dictation, or screen reader use.
• Showing shortcut hints that do not match the current platform or remapped key.
• Letting disabled commands still run from the keyboard handler.
• Overriding browser find, save, print, back, refresh, or operating-system shortcuts without a strong app-like reason.
• Using one shortcut for different commands in different panels without showing scope.
• Executing destructive, paid, public, or permission-changing commands from a key press without review or recovery.
• Documenting shortcuts in a help page but not exposing them near commands, menus, toolbars, or command search.

Critique Questions

• What visible command does this shortcut invoke, and does the shortcut call the same command handler?
• Where is the shortcut active, and where is it deliberately suppressed?
• Which browser, operating-system, assistive-technology, text-editing, and product shortcuts could conflict?
• How do users discover, search, remap, disable, and restore the shortcut?
• What happens when the command is disabled, pending, failed, risky, or no longer valid?
• Does this shortcut still work with international keyboard layouts, speech input, screen readers, and hardware keyboards on tablets?
• Is a visible button, menu item, toolbar control, command palette row, or focus traversal pattern the real primary pattern?