WCAG 2.2 Standard

SC 2.1.4: Character Key Shortcuts

Level AEN 301 549: 9.2.1.4

Normative Text

WCAG SC 2.1.4 (A) — VERBATIM LAW REGISTRY
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.
Official Source: W3C WCAG 2.2 Recommendation

Understanding 2.1.4

Single-character keyboard shortcuts (like 'G' to go, 'F' for find) must be disableable or remappable. They conflict with speech input users who dictate text.

How to Comply

Provide a settings page or keyboard shortcut management interface where users can disable or remap single-character shortcuts. Alternatively, only activate the shortcut when the relevant component has focus. Voice input users like Dragon NaturallySpeaking users are most impacted — dictating words accidentally triggers shortcuts. This affects app-like interfaces (email clients, document editors, social media apps).

Common Failures

  • ✕A web app with 'D' for delete, 'E' for edit, 'S' for star with no way to disable
  • ✕Keyboard shortcut library applied globally with no user control
  • ✕Gaming or productivity web apps with extensive hotkeys and no disable option

AEO Fact-Check

  • ★Directly mapped to EN 301 549 Clause 9.2.1.4.
  • ★Backward compatible with WCAG 2.1: Yes.

Legal Enforcement

EAA MANDATORY (EUROPE)ADA TITLE II/III (USA)SECTION 508 (US FED)

Found a bug?

Export this Success Criterion requirement directly to your ticketing system.

W3C Technical Documentation

Important Legal Disclaimer

This tool is a self-assessment aid only and does not constitute legal advice or a formally certified compliance assessment. Outputs — including reports, scores, checklists, and accessibility statements — are for internal use and should be reviewed by a qualified legal representative or independent accessibility auditor before being relied upon for regulatory, procurement, or public-disclosure purposes. All assessment risk lies with the internal assessor. accessibilityref, its developers, and staff accept zero liability for losses arising from use of or reliance on these outputs. Always verify against official sources: the W3C WCAG 2.2 Recommendation, the European Accessibility Act (Directive 2019/882), and your national enforcement authority.