2.1.1 Keyboard Level A

Browse by Category

Conformance Levels


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.

This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

[View on W3C.org]

Questions & Answers

Do tooltips need to be keyboard operable?

I have an interactive button with a tooltip that opens on mouse hover to give more information. All the tooltip information is in the button’s ARIA label, so why does the tooltip need to be openable on keyboard?

  • keyboard
  • tooltip

Are there multiple ways to build an accessible widget?

I'm trying to build a widget that follows an example in the W3C ARIA Authoring Practices Guide, but I can't quite match it because of the way my site is built. Can my widget still be accessible?

  • aria
  • custom widgets

What does “accessibility node not exposed” mean?

I was checking to make sure an element on my page has an accessible name in Chrome's Developer Tools and under the Computed Properties section of the Accessibility panel, it says "Accessibility node note exposed. Element not interesting for accessibility." What does that mean?

  • accessibility node
  • hidden content