Design Keyboard Shortcuts That Do Not Collide
Navigation & IA · keyboard, accessibility, consistency
Updated 2026-07-28
- Never override what the browser and operating system already own. Taking find, save, print, or tab switching away from a user is a betrayal of muscle memory built over years.
- Reserve single-key shortcuts for pages with no text entry, and always disable them while a field has focus. Nothing is worse than typing a note and triggering delete.
- Follow the conventions people already know rather than inventing your own for the same actions.
- Make shortcuts discoverable:
- Show them in menus next to the action they trigger.
- Show them in tooltips.
- Provide one overlay listing everything, opened by a conventional key.
- Display the correct symbols for the platform, since the wrong modifier name is enough to make a shortcut unusable.
- Watch for conflicts with assistive technology, which claims many key combinations for its own navigation.
- Let users see, and where practical change, the bindings. Power users have preferences, and international keyboards make some combinations physically awkward or impossible.
- Confirm that a shortcut fired. An action that happens silently off screen leaves the user unsure whether anything happened at all.
Shortcuts are for the people who use a product all day, and they only pay off when they are consistent, discoverable, and never in the way.
Related guides
UX Handbook