2.1.1 Keyboard

Summary

All functionality must be operable through a keyboard. Users with motor disabilities, screen reader users, and speech-input users all reach the page through the keyboard interface. Native elements satisfy this for free; failures almost always come from buttons built out of divs.

Common failures

• A `<div onclick>` button that Tab never reaches and that ignores Enter and Space.
• Binding functionality only to drag-and-drop or hover, with no keyboard alternative.

Corresponding KWCAG 2.2 items

• 6.1.1 Keyboard Accessibility Guaranteed

Related study units

• Keyboard Navigation and Focus Management
• Semantic HTML and Accessibility