Building Blocks
Menu
SystemFoundationComponentsPatternsThemesIncluded
CatalogsLive catalogsHow catalogs work
GuidesDocs
Pattern

Keyboard shortcuts chrome

Power path

RequiredSource pattern
ContractKeyboard shortcuts chrome
Job
Power path
Requirement
must specify
States / rules
Live vs mock
Specified means
Not separately stated in this row.
Hardest context
⌘K dead, ⌘J live
Example

—

Counter-example

Both look live

Flow

Trigger: A recurring command benefits from a faster keyboard path without removing the ordinary visible path.

  1. Keep a visible ordinary command path.Keep a visible ordinary command path.
  2. Expose the shortcut where the command is learned, not only in a separate cheat sheet.Expose the shortcut where the command is learned, not only in a separate cheat sheet.
  3. Do not fire shortcuts while the user is typing into an incompatible text context.Do not fire shortcuts while the user is typing into an incompatible text context.
  4. Move focus or execute the command predictably.Move focus or execute the command predictably.
  5. Provide immediate feedback when the command changes state.Provide immediate feedback when the command changes state.
  6. Let Escape or the relevant cancel path return the user to a known location.Let Escape or the relevant cancel path return the user to a known location.

Typical Building Blocks composition

Composition below is baseline guidance for the pattern; it does not rename or add source checklist rows.

Command surfaceTooltip or menu hintFocus ringStatus / toast where feedback is needed

Flow rules

  • Shortcuts augment; they do not replace visible navigation or controls.
  • Avoid collisions with browser/platform conventions.
  • Keyboard focus remains visible after the shortcut changes context.

Responsive behavior

Shortcut hints may reduce on touch-first layouts, but the command itself cannot disappear solely because a hardware keyboard is less likely.

Accessibility is tested across the sequence.

Keyboard order, focus movement, state announcements, touch targets, cancellation, and recovery must be verified for the whole flow—not only for each participating component in isolation.

Recovery is part of the pattern.

A complete pattern defines what the user sees when the happy path breaks, what is preserved, where focus goes, and how the user safely resumes or exits.

Catalog connection

A product Catalog can show this pattern only when the product actually implements the flow. If it is absent, keep the section honestly Not yet rather than mounting a fictional working pattern.