Goal
Ensure keyboard operation does not depend on timed keystrokes.
Success Criterion · WCAG 2.1.3
Keyboard (No Exception)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Level AAAWCAG 2.0Operable2.1 · Keyboard Accessible
Copy button ready
What to do
Support keyboard operation without requiring specific timings for individual keystrokes (e.g., key sequences that must be entered quickly).
Why it matters
Some users type slowly or use alternative input devices; timed keystroke requirements can make functionality impossible.
Success criterion
What WCAG 2.1.3 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.
Intent
Why WCAG created this requirement
- Timed key sequences can exclude users with motor impairments or users using assistive tech.
- Keyboard operation should be robust regardless of typing speed.
- The only exception is path-based input (same as 2.1.1).
Benefits
Who gains when you pass
- Users with motor impairments can operate features at their own pace.
- Users relying on switch control or alternative keyboards are not excluded by timing constraints.
- Users with tremors or fatigue can interact without rushing.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may fail to trigger actions because they cannot press keys “fast enough.”
Assistive technologies that generate key events at different pacing may break functionality.
Exception guidelines
Use the WCAG 2.1.3 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Path-based input
Functions that inherently depend on the path of movement may be exempt.
Requirement
If path-based, provide alternatives where feasible.
Overview
This AAA criterion strengthens keyboard accessibility by ensuring users don’t need to press keys within a narrow time window to operate features. Avoid “type quickly to activate” interactions and provide alternatives for timed sequences.
- Avoid interactions that require rapid repeated key presses or fast key chords to succeed.
- If shortcuts exist, ensure they don’t depend on timing (or provide non-timed alternatives).
- Use standard keyboard patterns and allow sufficient time for sequences.
Reference: All summaries and highlights originate from Understanding WCAG 2.1.3 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.1 · Keyboard Accessible
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Shortcut timing
Pass
Shortcut can be entered at normal pace; there is also a menu item for the same action.
Fail
Feature activates only if user types a sequence within 1 second.
Key repeat
Pass
Holding Arrow key scrolls, but single presses also work without timing constraints.
Fail
User must rapidly press Arrow key to move focus; slow presses don’t register.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document all keyboard shortcuts and confirm none rely on timing.
- Record alternatives for any complex keyboard interactions.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Audit keyboard interactions for timed sequences (rapid key combos, quick multi-key patterns).
- Replace timed sequences with explicit controls or menus.
- Ensure keyboard shortcuts are tolerant of slower input pacing.
- Provide UI controls that duplicate shortcut-only features.
- Test with alternative input devices and slower key repeat rates.
Testing ideas
Prove conformance with evidence
- Operate all keyboard-accessible features slowly and verify they still work.
- Adjust OS key repeat/delay settings to slowest and retest.
- Test with screen reader and switch control where possible.
- Verify no action requires rapid repeated key presses to succeed.
Related success criteria