Description
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.
Questions & Answers
Do I need aria attributes or roles on native elements?
Do I need to add aria attributes on native elements (eg. <button role="button>)?
- aria
- aria attributes
- native elements
How do I change the order the elements on my page are given focus?
When I tab through the elements on my site with the keyboard everything is almost perfect except for a couple case where it looks like the order is messed up. How can I change the order the elements on my page are given focus when...
- best practices
- html
- keyboard
- page structure
How do I navigate a website with my keyboard?
I've been reading about how I need to make sure my site can be navigated with a keyboard. Honestly, I'm not even sure where to start because I don't know what button I would hit on my keyboard. How do I navigate a website with...
- keyboard