Goal
- Allow keyboard navigation for users with a preference for that practice.
- Allow content to be accessed and services to be used, regardless of the input device, so as to make them accessible by users of technical aids (screen readers, for example) who only utilize the keyboard or a more specific device based on the same mechanisms as a keyboard (like a push button).
- Improve the accessibility of content for people with disabilities.
Implementation
Use universal event handlers in case of JavaScript-based interaction (for example, onclick for an a link or for a form field or control) or, failing this, complement non-universal event handlers (onmouseover for example) by a second handler allowing keyboard access (onfocus for example) or even provide an alternative means of access.
Control
This check applies to all interactive elements: hyperlinks, buttons, form fields, JavaScript widgets, etc. The default interaction mode is the Tab key to go to links, fields, and controls, and then the Enter key to activate them. In some widgets, a specific mode of interaction may be present: space bar to validate, arrow keys to move, escape key to close or exit. As far as possible in this case, these specific keys should be indicated to the user.
Within each page checked:
- Check that all interactions, links, buttons, form fields, present in the pages are usable from the keyboard, with the exception of those for which this would not make sense, such as a mouse plotting functionality.
Discover Opquast training and certification
The objective of these rules and the Opquast community mission is ‘making the web better’ for your customers and for everyone! Opquast rules cover the key major areas of risk that can negatively affect website users such as privacy, ecodesign, accessibility and security.
Opquast training has already allowed over 19,000 web professionals to have their skills certified. Train your teams, contact us
We offer a 1 hour free discovery module.