2.1.1 Keyboard [A]

Level A

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.>

Explanation

It must be possible to do everything without a mouse that a mouse user can do. This makes sure that people who use keyboards or speech recognition tools can navigate content and complete tasks successfully.

Responsibilities

  • Design
  • Development
  • QA

Requirements

  • All interaction and functionality is usable with a keyboard;
  • All interaction and functionality is usable on a touch-screen device;
  • All interaction and functionality is usable with speech recognition tools.

Common mistakes

  • A custom widget has been created, but the necessary keyboard support has not been provided;
  • An <a> element has been used as the basis for a button, but the additional keyboard interaction (activation with the space key) has not been provided;
  • A dialogue opens but cannot be dismissed by touch, because it does not have a close button;
  • The tabindex attribute has been used with a value of “-1” to mistakenly remove it from the tab order.

Official resources

Other resources