Keyboard Shortcuts
Give frequent users fast keyboard paths that are discoverable, consistent and never get in the way of typing.
6 states4 edge casesDesktop + Mobile
01The problem
Power users who live in a product all day want to move without the mouse. Shortcuts deliver that, but only if people discover them, they don't conflict with the browser or assistive technology, and they never fire while the user is typing in a field.
02When to use
Use when
- Products used for hours a day: inboxes, issue trackers, editors, CRMs
- Repetitive actions on lists: next, previous, archive, assign
Avoid when
- Occasional-use products — users won't learn them.
- As the only way to perform an action.
03Recommended UX
Statecraft recommendation
Teach shortcuts where users already look — in tooltips, menus and the command palette — provide a “?” help sheet listing them all, use single keys only for list navigation outside inputs, and never override browser or screen-reader shortcuts.
04Desktop behaviour
On desktop, shortcut hints appear in tooltips and menus, and a help sheet lists every shortcut grouped by context.
Desktop rules
- Show shortcuts in tooltips (“Archive · E”) and menu items.
- “?” opens a grouped help sheet: Navigation, Lists, Editing.
- Use platform modifiers: ⌘ on Mac, Ctrl elsewhere — and display them correctly.
- Sequences (G then I) for navigation to avoid conflicts.
05Mobile behaviour
On phones, shortcuts don't apply — but tablets with keyboards do. Hide hints on touch-only devices.
Mobile rules
3 mobile rules are included in Pro.
Statecraft Pro
Unlock the full pattern
Get the complete interaction flow, states, edge cases, mobile rules and implementation prompt.
- Interaction flow · 5 steps
- 3 mobile rules
- 6 states
- 4 edge cases with recommendations
- 4 microcopy comparisons
- Accessibility notes
- Developer notes
- Claude Code / Codex implementation prompt
Edge cases covered in this pattern
- Typing in a field
- Screen reader conflicts
- Non-QWERTY layouts
- Destructive shortcuts