Chords usually require the modifier to be down before the primary key; reversing the order may not fire

What it is

Most systems implement chords so that the modifier must already be held when the primary key goes down and the shortcut table is consulted. Tapping the primary key and then adding Ctrl or Command typically emits the character first; the late modifier does not rewrite it into a command. Order is a directed sequence, not “several keys touching at once.” Users think simultaneity is enough; the device decides command versus typing in a gap of tens of milliseconds.

Why it happens

The keyboard reports a sequence: modifier down, primary down, primary up, modifier up. Shortcut matching usually hangs off the primary-down (sometimes primary-up) frame and reads the modifier bitmap at that instant. If the primary arrives first, the bitmap is still empty and the app inserts a character; the modifier arriving later has no unconsumed primary to pair with. Games and some native tools re-interpret subsequent keys as soon as a modifier goes down, but they still do not retract a character already inserted. Touch chords are stricter: one finger must hold the modifier before the other taps the primary, or the two contacts become unrelated taps. This is the entry rule of the same state machine as “releasing the modifier exits the quasi-mode,” but the question here is the order of the command stroke, not how long the mode lasts.

Studying it

Log scan-code timing while people fire a fixed set of shortcuts, and plot modifier-versus-primary onset lag. Independent variables include whether instructions say “hold, then tap,” whether a key visualization is shown, and one hand versus two. Dependent measures are fire rate, character-then-undo counts, and the onset-lag distribution. Novice failures cluster where the primary leads by about 20–80 ms. A questionnaire on “do you know this shortcut” does not measure timing.

Where it stops holding

Sticky Keys latches modifiers so they can be pressed one after another, relaxing this order for those who enable it. Some apps still listen for a modifier while a letter is already down, allowing “hold the letter, then Ctrl,” but that is not the system default and should not drive general teaching. During IME composition the primary key may be consumed before the app sees it, so even correct modifier order will not fire an application shortcut. Remote desktop can reorder the queue so two locally simultaneous strokes arrive with the primary leading.

Applying it

• Write teaching and empty-state copy as “hold the modifier, then press the key,” not “press them together.”
• Shortcut visualizations should highlight available primaries as soon as a modifier is down, giving immediate feedback for “hold first.”
• If a command is critical, provide a menu or button equivalent rather than relying on a correctly ordered chord.
• Verify by recording novices doing copy, save, and undo, and scoring how often the primary leads the modifier. If almost every miss is a leading primary, change the copy and feedback, not the letter.

Related

• Same group: C6.20.2 Sticky Keys lets modifiers be pressed one after another, serving people who cannot hold chords · C6.20.3 Chord vocabulary grows with features until it exceeds ordinary finger-reachable combinations · C6.20.4 Three-key and larger chords are a steep barrier for one-handed or motor-impaired users
• Adjacent: C6.04 Modifier keys · C6.03 Shortcut systems
• Search: modifier-first · key chord timing · keyboard shortcut order