Keyboard Shortcuts for Power Users: What Actually Works
Shortcuts that let frequent users work faster without reaching for the mouse.
Priya Raghunathan
Where most projects go wrong
The usual mistakes:
- Single-key shortcuts with no way to disable them
- Overriding browser shortcuts
- Undocumented shortcuts
- Different shortcuts across similar screens
What good looks like instead
- Publish a shortcut reference in the product
- Allow shortcuts to be turned off or remapped
- Follow platform conventions
- Require modifier keys where possible
- Show shortcuts in menus and tooltips
Why it matters
Shortcuts speed up expert work, but poorly chosen ones conflict with assistive technology and browser defaults.
The specs that matter
| Measure | Figure |
|---|---|
| Discoverability | shortcuts need to be findable and documented |
| Conflicts | single-character shortcuts can interfere with speech input |
| Remapping | WCAG expects single-key shortcuts to be adjustable |
| Consistency | shortcuts should follow platform conventions |
Knowing when to hand it over
Tip: Bring in help when building tools used all day.
Where this comes from
- W3C Web Accessibility Initiative — Understanding SC 2.1.4 Character Key Shortcuts
- Apple Human Interface Guidelines — Keyboards
The figures and practices above come from the sources listed.
Working on something like this?
We take on UI & UX Design work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
