Feature Library

Two clicks or Ctrl K

0.10 CPU ms
A still of the Two clicks or Ctrl K demo
Still
The live demo starts when it’s in view.Pick a ▲ function, then a fix · arrow keys walk the map · Fix all, or change the limit

A test that fails when any function in an app is more than two clicks away and has no Ctrl K command.

What it costs a frame

0.10 ms
GPU
not used
CPU, median
0.10 ms
CPU, 95th pct
0.20 ms
Draw calls
0
Weight
Light

Measured 13 November 2026 on RTX 4060 Laptop, 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept (rounds ranged CPU 0.10–0.21 ms). What ran: Measured with the demo fixing every function and starting over in turn, about twice a second: each time the reach test runs over 27 functions, the map is laid out again and every moved control and its line glide to their new places. Idle, nothing runs. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
RTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed0.100.20
apple · Apple A19 Proin a browser tab · 16 November 2026not timed0.180.40
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed0.200.37

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Keeping a growing app’s functions findable
  2. A unit test over the menus as they are defined
  3. Reviewing an app’s map before a redesign
  4. Deciding what goes in the command palette
  5. Catching a feature added with no way in
  6. Holding a hand-kept feature map to the source

Pitfalls, in brief

  1. The model checks the map you give it, not the screen.
  2. Clicks count from the app as it opens, with what the function acts on already selected.
  3. A submenu that opens on hover costs 0 clicks for a mouse but not for touch or a keyboard: give it cost 0 only if you also check those another way.
  4. A key counts as a way in by default, as in the app this came from; keys are invisible until learnt.
  5. Allow a function deep only with a reason (a delete that can’t be undone).
2 more in brief
  1. Moving a control up gives it its function’s name as its label (“Export as Markdown”, not “Markdown”), since it no longer sits under the menu that named it.
  2. fixAll applies one fix at a time and re-checks, so two fixes never fight; still review what it did before you change real menus.
7 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From SpaciousPro. Fully custom code.

WAI-ARIA Authoring Practices Guide (W3C): the Tree View pattern for the demo’s map (one Tab stop, arrow keys, aria-level, aria-setsize and aria-posinset on a flat list), and a polite live region for each fix

reachabilityinformation architecturemenuscommand paletteCtrl Kkeyboard shortcutsdiscoverabilityUX testvitestfeature mapaccessibilityno dependencies

Near it in the frame