WCAG 2.1.4: Character Key Shortcuts

Who this helps

Single-key shortcuts are convenient for the people who know them and a minefield for the people who do not. Controlling them protects several groups at once:

What the requirement covers

The trigger for this criterion is specific: a keyboard shortcut bound to a single printable character — a letter such as a or B, a number like 3, or punctuation and symbols like ? and / — with no modifier key held. When that pattern exists, you must provide at least one of these three mechanisms:

• →Turn off. Give users a mechanism to disable character-key shortcuts entirely — a settings toggle, a preference, or a per-shortcut switch. Once off, no bare keystroke fires a command.
• →Remap to a non-printable key. Let users reassign the shortcut to a combination that includes at least one non-printable key such as Ctrl or Alt. A modifier-based shortcut is effectively impossible to trigger by dictation or a stray keystroke.
• →Active only on focus. Scope the shortcut so it fires only when its specific component has focus. A media player that responds to 'k' only while the player is focused cannot interfere with typing elsewhere on the page.

What is out of scope

Shortcuts that require a modifier or a non-printable key are inherently fine and need no extra mechanism: Ctrl+S, Alt+K, and function keys are all outside 2.1.4 because voice input and accidental presses will not reproduce them. This is the difference between 2.1.4 and 2.1.1 Keyboard: 2.1.1 is about making features operable by keyboard at all, while 2.1.4 is about preventing a shortcut from being triggered unintentionally.

Pass and fail examples

Code examples

The failure: an always-on global shortcut

A bare key handler on document with no off switch, no remap, and no focus check is the classic 2.1.4 violation.

// ✗ Fires on every bare keystroke, everywhere, always
document.addEventListener('keydown', (e) => {
  switch (e.key) {
    case 's': starMessage();   break; // dictating "s" stars a message
    case '/': focusSearch();   break; // typing "/" jumps to search
    case 'c': composeNew();    break;
  }
})

Remedy 1 & 2: an off switch and a modifier requirement

Guard the handler with a user preference (turn off) and skip anything that carries a modifier so a remapped Ctrl+S can pass through untouched. Also ignore keystrokes aimed at text fields.

// ✓ Respects a "shortcuts off" preference and modifier remaps
let shortcutsEnabled = loadUserPref('charKeyShortcuts', true)

document.addEventListener('keydown', (e) => {
  if (!shortcutsEnabled) return                 // (1) turn off
  if (e.ctrlKey || e.altKey || e.metaKey) return // (2) modifier = out of scope

  // Never hijack keys while the user is typing
  const t = e.target
  if (t.matches('input, textarea, [contenteditable]')) return

  if (e.key === 's') { e.preventDefault(); starMessage() }
})

Remedy 3: active only on focus

Bind the shortcut to the component itself rather than the document, so it can only fire while that component holds focus.

<!-- ✓ "k" toggles play only while the player is focused -->
<div class="video-player" tabindex="0">
  <!-- controls … -->
</div>

<script>
  const player = document.querySelector('.video-player')
  // Listener is on the player, not on document
  player.addEventListener('keydown', (e) => {
    if (e.key === 'k') { e.preventDefault(); togglePlay() }
  })
</script>

Interactive demo

Press s to fire a “star” shortcut and watch the log. Then toggle the shortcut off, switch it to focus-only mode, and try typing in the text field to see how each remedy stops the shortcut from firing by accident.

Common failures

• ✗App-wide single-key shortcuts (Gmail-style j/k to move, s to star, c to compose) that are always active globally with no off switch.
• ✗A single '/' or 'f' bound document-wide to focus search, firing while the user dictates or types outside a field.
• ✗Single-letter commands with no remap option, so a user cannot move them to a modifier combination.
• ✗Shortcuts that stay active while focus is in a text input, so dictation and typing trigger unintended actions.
• ✗Undocumented hidden shortcuts users cannot discover, disable, or predict.
• ✗Assuming an on-screen button alternative is enough — it does not remove the accidental-activation hazard the criterion targets.
• ✗Treating documentation of the shortcuts as compliance; listing them does not turn them off, remap them, or scope them to focus.

How to test for 2.1.4

1. 1

   Enumerate every single-character shortcut

   Review the interface and its documentation, then press single keys — letters, numbers, punctuation, symbols — with no modifier held, in different parts of the page. List every bare-character key that triggers an action.

2. 2

   Confirm one of the three remedies for each

   For every shortcut you found, verify at least one is true: there is a mechanism to turn it off, a mechanism to remap it to a modifier combination, or it only fires while its component has focus. Any single one passes.

3. 3

   Check the modifier boundary

   Shortcuts that already require Ctrl, Alt, Cmd, or a function key are out of scope. Confirm the in-scope set is only the bare single-character shortcuts, so you test the right things.

4. 4

   Run the speech-input scenario

   Dictate a sentence into a text field (or type a long string). No global shortcut should fire from the characters. If it does, the shortcut is not focus-scoped or disabled and the page fails.

5. 5

   Exercise the off switch and remap UI

   If the page relies on turn-off or remap, actually use those controls: disable shortcuts and confirm the bare keys go silent; remap one to a modifier and confirm the single key no longer triggers it.

6. 6

   Verify focus scoping is real

   For focus-only shortcuts, move focus away from the component and confirm the key no longer does anything. A shortcut that still fires from elsewhere is effectively global.

For a structured audit, work through the full WCAG 2.2 checklist.

Frequently asked questions