2.1.1: Keyboard

What it means

All functionality must be operable through a keyboard alone, without requiring specific timings for individual keystrokes. Mouse-only actions need keyboard equivalents.

Keyboard access is how many assistive technology users navigate the web.

How to fix it

  • Ensure every button, link, and control is focusable and activatable with Enter or Space.
  • Provide keyboard paths for custom widgets (menus, sliders, dialogs).
  • Do not rely on hover-only actions for tasks users must complete.
  • Test the full checkout or sign-up flow using only Tab, Enter, Space, and arrow keys.

Quick examples

  • Good: A custom dropdown opens with Enter and options move with arrow keys.
  • Bad: A drag-only image cropper has no way to adjust the crop with a keyboard.
  • Good: Modal dialogs trap focus and close with Esc.
  • Bad: Important filters apply only on mouse click with no keyboard event handler.

W3C Understanding 2.1.1: Keyboard — full official details