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
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
I was told that my buttons need to be operable by the spacebar. Is that true? Are there any other keys that need to be supported?
- keyboard support
Do I need to add aria attributes on native elements (eg. <button role="button>)?
- aria attributes
- native elements
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
- page structure
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...
I see a lot of WordPress websites (and websites in generally really) using sliders for images and information. I can see how it would be really easy to make an accessible slider. Are there any 'out of the box' accessible WordPress sliders?
- third party