2.1.4 Character Key Shortcuts (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.1.4 Character Key Shortcuts (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.1.4 Character Key Shortcuts
2.1.4 Character Key Shortcuts (Level A)
What it requires: If a single-character keyboard shortcut exists (like pressing “s” to open search), the user must be able to turn it off, remap it, or have it only active while a specific control has focus — because single-key shortcuts collide with screen-reader and speech-input commands that use the same keys.
Common failure: A site adds a global “/” or “s” shortcut to focus the search box, which fires even while a screen-reader user is reading page content in browse mode, unexpectedly hijacking their letter-key navigation.
Fix it: Scope single-character shortcuts to only fire when a specific element has focus, or provide a setting to disable/remap them if they’re global.
In 2.1 Keyboard Accessible: ← 2.1.3 Keyboard (No Exception)
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.