Character Key Shortcuts
Tier 1 · The normative floor
Baseline compliance
What the normative text of WCAG 2.2 requires, and nothing more. Only a failure of this tier is a WCAG failure.
The bare minimum
If a keyboard shortcut uses only a letter, punctuation, number or symbol key, at least one of these is true: it can be turned off; it can be remapped to include a non-printable key such as Ctrl or Alt; or it only works while the relevant component has focus.
Normative text
Verbatim from WCAG 2.2, W3C Recommendation 12 December 2024. Underlined terms are defined below.
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.
Not required by the normative text
Common claims that this criterion does not support. Don't log these as WCAG failures.
- Anything for shortcuts that already use a modifier key such as Ctrl or Alt.
Definitions used (3)
Glossary definitions are normative. Their notes are informative.
- keyboard shortcut
-
alternative means of triggering an action by the pressing of one or more keys
- mechanism
-
process or technique for achieving a result
Informative notes (2)
The mechanism may be explicitly provided in the content, or may be relied upon to be provided by either the platform or by user agents, including assistive technologies.
The mechanism needs to meet all success criteria for the conformance level claimed.
- user interface component
-
a part of the content that is perceived by users as a single control for a distinct function
Informative notes (3)
Multiple user interface components may be implemented as a single programmatic element. "Components" here is not tied to programming techniques, but rather to what the user perceives as separate controls.
User interface components include form elements and links as well as components generated by scripts.
What is meant by "component" or "user interface component" here is also sometimes called "user interface element".
Tier 2 · The gap
Usability & user impact
Where content can meet this criterion and still make things harder for people with disabilities. These are not failures of SC 2.1.4, so raise them as usability defects. Known failures, including failures of related criteria, are listed in Tier 1.
A setting to turn shortcuts off that is hard to find leaves speech-input users accidentally triggering actions until they discover it.
Tier 3 · The golden path
Recommended best practice
The pattern that meets the floor, closes the gap, and avoids audit disputes. A recommendation, not a requirement.
Avoid single-key shortcuts, or make them opt-in, and list all shortcuts in an easy-to-find help panel.
W3C's Understanding document and techniques for SC 2.1.4 ↗ are informative: sufficient techniques show ways to pass, and documented failures show common ways to fail, but neither changes what the criterion requires.
How SC 2.1.4 maps to the WCAG 3 draft
From this site's reviewed map to the WCAG 3 editor's draft. It's an interpretation: W3C has not published a mapping.
Successor provisions
From WCAG 2.2, section 5.1: “The main content of WCAG 2.2 is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.”