Understanding Success Criterion 2.1.3: Keyboard (No Exception)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Intent of Success Criterion 2.1.3: Keyboard (No Exception)

The intent of this Success Criterion is to ensure that all content is operable from the keyboard. This is the same as Success Criterion 2.1.1, except that no exceptions are allowed. This does not mean that content where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (excluded from the requirements of 2.1.1) must be made keyboard accessible. Rather, it means that content that uses path-dependent input cannot conform to this Success Criterion and therefore cannot meet Guideline 2.1 at Level AAA.

Examples of Success Criterion 2.1.3: Keyboard (No Exception)

Resources Success Criterion 2.1.3: Keyboard (No Exception)

Techniques for Success Criterion 2.1.3: Keyboard (No Exception)

Sufficient Techniques

No additional techniques exist for this Success Criterion. Follow techniques for Success Criterion 2.1.1. If that is not possible because there is a requirement for path-dependent input, then it is not possible to meet this Level AAA Success Criterion.