WCAG 2.1.4 Character Key Shortcuts

Success criterion 2.1.4 protects people who use speech recognition and people who press keys by accident (for example because of tremors) from triggering commands they did not mean. It is level A and part of EN 301 549 (clause 9.2.1.4).

What the criterion requires

If the content implements a keyboard shortcut using only letter (upper- or lower-case), punctuation, number or symbol characters, at least one of these must be true:

• Turn off: a mechanism is available to turn the shortcut off;
• Remap: a mechanism is available to remap it to include one or more non-printable keys (such as Ctrl or Alt);
• Active only on focus: the shortcut for a component is only active when that component has focus.

It does not matter how many physical keys produce the character: "?" typed with Shift+/ still counts as a character key. Sequences such as pressing G and then A also count.

Not affected: listboxes and dropdowns where typing a letter jumps to an option while they have focus, menus opened with a modifier such as Alt, and browser access keys that use modifier keys.

Typical failures on an online shop

• a "/" or "s" key that jumps to the search field from anywhere on the page;
• "?" opening a help overlay, or "c" opening the cart, with no way to disable it;
• product galleries or lookbooks that react to single letters globally, not only when focused;
• an admin-style theme feature or third-party widget (chat, accessibility toolbar) that adds letter shortcuts to the storefront.

Most shops have no character shortcuts at all — then the criterion simply does not apply.

How to check it

Automated: there is no axe-core rule for this criterion. Shortcuts live in JavaScript key handlers, which a scan does not exercise, so it needs a manual check.

By hand: click on an empty area of the page (so no field has focus) and press single letters, digits and common symbols such as "/", "?" and ".". Watch whether anything happens. Read the theme and plugin documentation for listed shortcuts. If you find one, check for a setting to turn it off or remap it, or confirm it only works when its widget is focused.

How to fix it

• Prefer shortcuts with a modifier key (Ctrl, Alt, Cmd) for site-wide actions.
• Scope single-key shortcuts to the component that has focus, for example arrow and letter keys inside a focused gallery.
• If you keep global character shortcuts, add a clear setting to turn them off or change them.
• Never fire a shortcut while the user is typing in a text field.

Related criteria

• 2.1.1 Keyboard — all functions must work from the keyboard.
• 2.5.3 Label in Name — another criterion that helps speech input users.
• Our rule library lists the criteria that automated rules do cover.

Frequently asked questions

Which keyboard shortcuts does 2.1.4 cover?

Shortcuts made only of printable characters: letters, numbers, punctuation or symbols, including sequences such as G then A. Shortcuts that need a modifier key such as Ctrl or Alt are not affected.

How can a site meet 2.1.4?

At least one of three options: a way to turn the shortcut off, a way to remap it so it includes a non-printable key such as Ctrl or Alt, or the shortcut works only while its own component has focus.

Why are single-letter shortcuts a problem?

Speech input users dictate words, and each letter can fire a shortcut. People who brush keys by accident can also trigger actions they never wanted.