Keyboard (No Exception) ensures that all functionality on a page can be operated using a keyboard, without relying on pointer-based input or specific timing for keystrokes, such as requiring users to drag, draw, or press keys within a narrow time window.
If users can act with a mouse, touch, or other pointer input, they must also be able to perform that action using only a keyboard. This criterion exists because some users rely entirely on keyboard input and cannot use pointer-based interactions at all. At Level AAA, partial keyboard access is not sufficient.
WCAG Success Criterion
2.1.3 Keyboard (No Exception) (Level AAA)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Why This Matters
For some users, the keyboard is not an alternative input method; it is the only way they can interact with content. If even a single required action depends on pointer input, those users may be unable to complete tasks, access information, or use essential features of a page.
At Level AAA, keyboard accessibility must be complete. If functionality cannot be operated with a keyboard, the content cannot conform to this criterion.
Intent of the Criterion
This success criterion intends to ensure that all content is operable from the keyboard, with no exceptions. This criterion builds on SC 2.1.1 Keyboard, but removes the allowance for certain pointer-dependent interactions. At Level AAA, functionality that relies on path-dependent input, input defined by movement paths rather than discrete actions, cannot conform.
This does not mean authors are required to make every possible interaction keyboard accessible. Instead, it establishes a strict boundary: If content depends on input that cannot be expressed through a keyboard interface, it cannot meet Guideline 2.1 at Level AAA.
Important Distinction from SC 2.1.1
SC 2.1.1 allows an exception for path-dependent input, such as:
- Drawing with a pointer
- Gestures that depend on movement paths rather than endpoints
SC 2.1.3 removes this exception entirely.
If functionality depends on path-based pointer movement, it cannot meet Level AAA for Guideline 2.1. This is a conformance limitation, not an implementation defect. The content may still be usable or conformant at lower levels, but it cannot satisfy this criterion.
What This Criterion Does Not Require
This success criterion does not require that:
- Every pointer-activated control must be focusable or operated in the same way as for pointer users
- Keyboard users must interact with controls using identical interaction models
- All interactions must follow platform or user-agent conventions
The requirement is that keyboard users can perform the same or comparable actions, even if the interaction model differs.
For example, providing a keyboard-specific mode of interaction does not fail this criterion.
Platform and Convention Considerations
User agents and platforms typically define conventions for keyboard interaction. Following these conventions is strongly recommended because it reduces cognitive effort and learning burden.
However, deviating from conventions does not fail SC 2.1.3, as long as keyboard operability is preserved.
For example:
- A custom button that responds only to Enter (and not Space) still conforms
- A control that uses a custom key combination still conforms
Conformance is about operability, not familiarity.
WCAG Criteria Affected
This criterion directly builds on:
- SC 2.1.1 Keyboard (Level A)
If content cannot meet SC 2.1.1 due to path-dependent input, it cannot meet SC 2.1.3.
This criterion does not introduce new techniques; it removes previously allowed exceptions.
Because of these constraints, SC 2.1.3 is rarely achieved in complex interactive applications.
Who This Helps
This criterion primarily supports:
- People who are blind and use screen readers
- People with motor or mobility impairments
- Users who rely on alternative input devices that emulate keyboard input
- Users who cannot perform precise pointer movements or gestures
How Keyboard Operability Is Expected to Work
Keyboard users must be able to perform all required actions using standard keyboard interaction without relying on timing-sensitive input.
Functionality must not depend on:
- Pointer movement paths
- Dragging gestures without keyboard alternatives
- Time-based key sequences
If an action cannot be completed without pointer-based movement, the content cannot conform at Level AAA.
Rule Description
All functionality must be operable through a keyboard interface, without relying on pointer-only interaction or path-dependent input.
If any required functionality cannot be performed using a keyboard, the content does not meet this criterion.
The Algorithm
- Identify all user-facing functionality
- For each function, attempt to perform it using only the keyboard
- Verify that:
- No pointer input is required
- No specific timing of keystrokes is required
- If any required action cannot be completed with the keyboard, the criterion fails
Test Rules
- Interactive content inside iframes can be reached using sequential focus navigation
- Scrollable content can be accessed and operated using the keyboard
- No required interaction depends solely on pointer movement paths
Wrapping Up
SC 2.1.3 represents the strictest form of keyboard accessibility in WCAG. It does not ask authors to make every interaction possible; it defines a boundary: If functionality cannot be operated through a keyboard, it cannot conform to Level AAA.
This criterion is not about convenience or best practice. It is about ensuring that keyboard users are not excluded from any essential interaction, without exception.
