Character Key Shortcuts
Single-character shortcuts must be switchable off, remappable, or active only on focus.
Definition
WCAG 2.1.4 requires that shortcuts using only letter, punctuation, number or symbol characters can be turned off, remapped to include a modifier, or made active only when the relevant component has focus.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
On this plate
Reach for this when
- Adding keyboard shortcuts.
- Building professional tools with heavy keyboard use.
Common mistakes
- Global single-character bindings.
- No way to disable shortcuts.
- Shortcuts that collide with browser or assistive technology bindings.
Safe approaches
- Prefer modifier combinations for global shortcuts.
- Scope single-key shortcuts to a focused component rather than the document.
- Provide a settings page to disable or remap shortcuts.
- Publish a shortcut reference, and make it reachable by keyboard.
Shortcut schemes, and whether they conform
| Scheme | Position | Notes |
|---|---|---|
| A bare letter, bound globally | Fails 2.1.4 unless it can be turned off or remapped | Dictation produces stray characters, and screen reader users press letters to navigate. |
| A bare letter, active only while a component has focus | Conforms | Scoping to the focused component is the exception the criterion allows. |
| A modifier combination | Conforms | The safest default for anything global. |
| A sequence, such as g then i | Conforms in practice | Nothing fires on the first key alone, so stray characters are harmless. Give the sequence a visible timeout. |
| Remappable or switchable off | Conforms, and is the strongest answer | It also serves people using alternative keyboards and layouts other than the one you designed for. |
Shipping shortcuts safely
Do
- Scope single-key shortcuts to the component that has focus.
- Let people turn shortcuts off, and remap them where the product is used all day.
- Show the shortcut next to the action in menus and palettes, which is how people learn them.
- Ignore shortcut keys while focus is in a text field, which is the most common source of accidental activation.
Do not
- Do not bind bare letters at the document level.
- Do not make a shortcut the only route to an action.
- Do not use a shortcut that collides with a screen reader command or a browser one.
- Do not assume the reader's keyboard layout. A key that is convenient on one layout may be unreachable on another.
Local chart
A11Y·019 · Region V · Grid B3
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
- [1]
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Related concept
Connected closely enough to change how you apply this.
- Keyboard NavigationA11Y·002 · Accessibility
- Flexibility and Efficiency of UseHEUR·007 · Heuristic
Nearby in the Atlas
Adjacent territory, found through shared tags rather than a stated link.