Skip to content

WAS Notes: WCAG 2.1 Keyboard Accessible

I'm studying for the WAS certification. These are some of the notes I've taken recently.

Published:

2.1.1 Keyboard - Level A

All functionality is operable through keyboard interface without requiring timed keystrokes, except for when the function requires path-dependent input, such as handwriting for an electronic signature.

How to Succeed

How to Fail

2.1.2 No Keyboard Trap - Level A

Keyboard focus can’t get stuck without providing a standard way for users to escape out of a component or region. If there’s a non-standard way to exit, users are informed on how to do so.

How to Succeed

Ensure users aren’t trapped in content by letting them tab or escape out of it.

How to Fail

Trap focus without providing a keyboard accessible way out.

2.1.3 Keyboard (No Exception) - Level AAA

All functionality is operable through keyboard interface without requiring timed keystrokes. This removes the exception for path-dependent interactions from 2.1.1.

2.1.4 Character Key Shortcuts - Level A

Keyboard shortcuts are not implemented using single characters (letters, punctuation, numbers, or symbols), unless they can be turned off, remapped, or only apply when a component is focused.

How to Succeed

How to Fail

Implement single character shortcuts that can’t be turned off or changed by the user.