Success Criteria 2.1 requires that all functionality be
available from a keyboard.
Even if your designing content for a device with no
keyboard, you must also include functionality for keyboards.
You should still optimize your content for the other input
methods your target device supports, while maintaining the capability for
keyboard control.
Requiring keyboard accessibility does not prohibit mouse
input nor discourage providing mouse and other input methods in addition to
keyboard accessibility.
There are several supporting Success Criteria for 2.1:
2.1.1 Keyboard
All functionality of the
content is available through a keyboard interface without requiring specific
timings for individual keystrokes except where the underlying function requires
input that depends on the user’s movement and not just the endpoints.
2.1.2 No Keyboard Trap
If keyboard focus can be
moved to a component of the page using a keyboard interface, then focus can be
moved away from that component using only a keyboard interface, and, if it
requires more than unmodified arrow or tab keys or other standard exit methods,
the user is advised of the method for moving focus away.
2.1.3 Keyboard (No Exception)
All functionality of the
content is operable through a keyboard interface without requiring specific
timings for individual keystrokes.
2.1.4 Character Key Shortcuts
If a keyboard shortcut is
implemented, it must allow for modification, and be active only on focus.
2.4.7 Focus Visible
Any keyboard operable user
interface has a mode of operation where the keyboard focus indicator is
visible.
