Loading Developer Playground

Loading ...

Skip to main content
Developer Playground
Share:
Back to WCAG Explorer

Success Criterion · WCAG 2.1.4

Character Key Shortcuts

If a keyboard shortcut is implemented in content using only letter, punctuation, number, or symbol characters, then at least one of the following is true: the shortcut can be turned off, remapped, or is only active when the relevant user interface component is in focus.

Level AWCAG 2.1Operable2.1 · Keyboard Accessible
Copy button ready

Success criterion

What WCAG 2.1.4 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

All non-text content that is presented to users must expose an equivalent text-based alternative unless a documented exception applies.

View Understanding 2.1.4Open QuickRef techniques

Fast facts

Conformance level
Level A
WCAG version introduced
WCAG 2.1
Principle
Operable
Guideline
2.1 · Keyboard Accessible

Implementation checklist

Capture progress and blockers

  • Document how this criterion impacts your product and note any exceptions.
  • Describe the user experience goal in plain language for designers and engineers.
  • List the components, templates, or workflows that must meet this requirement.
  • Capture manual and automated testing steps for future audits.

Testing ideas

Prove conformance with evidence

  • Pair automated linting with human review to verify visual, auditory, or temporal aspects.
  • Use assistive technology walkthroughs (screen reader, keyboard, switch, voice) to validate behavior.
  • Capture screenshots or recordings that demonstrate pass/fail conditions.

Related success criteria

More from Keyboard Accessible (2.1)

View all criteria
WCAG 2.1.1KeyboardLevel AWCAG 2.1.2No Keyboard TrapLevel AWCAG 2.1.3Keyboard (No Exception)Level AAA
Back to WCAG Explorer