Keyboard & focus

The keyboard is the floor that every other input method stands on. If a feature works with a keyboard alone, it almost always works for switch devices, voice control, and screen readers too — because those technologies drive the page through the same focus and activation model. So the rule is simple and absolute: everything that works with a mouse must also work without one. And it isn’t enough to be merely operable — the user has to be able to see where they are. Focus must be visible, it must move in an order that matches the visual layout, it must never get trapped, and it must never be hidden behind a sticky header or cookie bar.

Who this affects

• Keyboard-only users — people who can’t or don’t use a pointer navigate entirely with Tab, Shift+Tab, arrow keys, Enter, Space, and Esc. A control that only responds to a mouse click is invisible to them.
• Screen reader users move through interactive elements with the keyboard and their AT’s own commands. Unfocusable custom widgets and illogical focus order leave them unable to reach or understand controls.
• Switch-device and voice-control users rely on the focus order and on named, focusable controls; their hardware and software step through the same tab sequence the keyboard exposes.
• People with tremor, RSI, or limited dexterity often find precise mouse targeting painful or impossible and prefer the keyboard, which demands a visible focus indicator to track their position without fine pointing.
• Power users — sighted, able-bodied people who simply work faster from the keyboard — benefit too, which is why good keyboard support pays off for everyone.

Standards covered

The lessons in this category map keyboard operability and focus behaviour to the success criteria and laws that require them. The same fixes satisfy all of them at once.

Lessons

• Keyboard access & visible focus

  Make custom controls operable, keep the focus ring visible and unobscured, escape keyboard traps, and give people a way to skip repeated blocks — the four defects behind most keyboard failures.

  2.1.1 2.1.2 2.4.3 2.4.7 2.4.11 2.4.1

• Managing focus in dynamic UIs

  Move focus deliberately when content changes, views switch, or overlays close.

• Visible focus & focus appearance

  Keep a clear, high-contrast focus indicator that is never removed or hidden.