If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
Turn off
A mechanism is available to turn the shortcut off;
Remap
A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
Active only on focus
The keyboard shortcut for a user interface component is only active when that component has focus.
About Success Criterion 2.1.4: Character Key Shortcuts
The purpose of these requirements is to minimize accidental activation of keyboard shortcuts, which can pose significant issues for users who depend on them. Speech Recognition users have to spell out content, say when writing an email, or entering text into a Search feature. If they say one of the letters that is used as a Character Key Shortcut, then they can inadvertantly trigger the shortcut when spelling out their content. As a results, users often cannot perform certain actions because shortcuts are unintentionally triggered. Ensuring that character-only shortcuts can be disabled or modified helps prevent unintended activations, particularly in contexts such as speech input.
An example of a previous issue (that has been addressed) involves the Android Twitter app. It featured a single-character shortcut—pressing the letter “N”—which could not be disabled. When activated via key press or speech recognition, it opens the “compose” screen, as demonstrated in the accompanying screenshots:
| Twitter: | On speaking the letter “N” |
|---|---|
 |  |
More Resources
- W3C: Understanding SC 2.1.4: Character Key Shortcuts
- W3C – Single character key shortcuts affecting speech input – example 1
- W3C – Single character key shortcuts affecting speech input – example 2