Pimp My IDE / garage dispatchBack to the garage
October 9, 2026 / interface craft / keyboard input

A shortcut is a local contract.

The same printed key can name a different action, produce a different character, or lose to the operating system on another machine.

Bind the intent after you map the platform, locale, and focus context.
INPUT FIXTURE / US LAYOUTUNTESTED
CTRLALTSHIFTKENTERSPACE
No browser or locale result attached

The legend is not the event.

Marcin Wichary's platform comparison starts with names that already disagree. Windows calls one key Backspace. Apple calls that key Delete. Windows shortcut labels usually join keys with a plus sign. macOS menus usually place modifier symbols beside the final key.[1]

The disagreement reaches past labels. macOS Option combinations can produce characters. Windows layouts can use AltGr for letters and punctuation. Some Windows layouts also expose AltGr through Ctrl plus Alt. A shortcut that looks free on a US keyboard can take a character away from another layout.

Store the action once. Render and test its keys per platform and input context.

The browser reports meaning after layout.

MDN documents KeyboardEvent.key as the value after modifier state, locale, and keyboard layout are considered. A printable key returns the resulting character. A dead key reports Dead. The same physical press can therefore produce a different value on a different layout.[2]

Use key when the action follows the character the user typed. Use the physical position only when the product truly needs that position, such as a game control. Do not turn every keydown into a command. Text fields, composition, repeated keys, and assistive technology still own parts of the route.

Focus is part of the shortcut.

The W3C ARIA Authoring Practices Guide says every interactive element must work from a keyboard. It also asks authors to keep focus visible and predictable. Its conflict guidance warns about operating-system, assistive-technology, and browser commands.[3]

That makes context a first-class input. A global command, editor command, and text-field command do not share one safe keyspace. The visible menu route matters too. If the shortcut collides or cannot be discovered, the user still needs a button, menu item, or command palette entry.

Test the contract, not the label.

Write the action name before the key chord. Record the target platforms and keyboard layouts. Exercise the chord with focus on the page, in the editor, and inside a text field. Check the operating system, browser, and assistive-technology conflicts that apply to the product.

Then inspect the fallback with the keyboard. The focus ring must stay visible. The action must announce a result. A rejected shortcut must leave typed text and composition intact.

Interactive makeover / static shortcut table replaced

Run keyboard customs.

The traditional table lists one chord and calls the job finished. This bench separates platform presentation from test requirements. It drafts a test card. It does not prove that a shortcut works on any browser, layout, or assistive setup.

Name actionChoose platformCheck conflictsRecord result

Input manifest

The platform detent changes the displayed chord. Each square breaker adds one requirement to the test card.

Platform detent
Conflict breakers
Platform display / evidence required

Shortcut test card

Windows0 / 4 breakers
CTRL+K
Test card emptyNo locale, focus, conflict, or fallback requirement is selected. No runtime result is attached.
Sources read / October 9, 2026

Source log

Open the evidence boundary
  1. Marcin Wichary, "Keyboard differences between Windows and Macs", published October 8 and read October 9, 2026. The reference covers key names, modifier conventions, shortcut rendering, character entry, reserved keys, text fields, and focus movement across Windows and macOS.
  2. MDN, "KeyboardEvent: key property", read October 9, 2026. The page defines layout-aware key values, dead keys, unidentified keys, repeat behavior, and the keyboard event sequence.
  3. W3C ARIA Authoring Practices Guide, "Developing a Keyboard Interface", read October 9, 2026. The guide covers keyboard operability, native element preference, visible and predictable focus, composite widgets, and shortcut conflicts.
  4. Hacker News discussion, "Keyboard differences between Windows and Macs", item 50015515, read October 9, 2026. We resolved the exact item URL through the Hacker News API. The discussion led to the reference. It does not verify platform behavior.

Scope: this page does not register or intercept a keyboard shortcut. The customs bench changes a displayed test-card template only. Platform behavior still needs testing on each supported operating system, browser, layout, input method, and assistive setup.