Accessible and operable by keyboard and any pointing device
This term is defined by more than one standard, and the wording differs. Each definition below is the one that applies to that standard’s criteria.
Definition in RAWeb 1.1
- A user interface component (link, button, etc.) can be accessed from the keyboard and by any pointing device when the user can focus it either by using the pointer or the tab key;
- A user interface component (link, button, etc.) can be activated from the keyboard and by any pointing device when the user can trigger the action intended by the interface component by pressing either the pointer or the default key(s) in the user agents (e.g. Enter, Space);
- Note: for some user interface components such as sliders (sliding or rotating knobs, etc.), it is not possible to control the component using the enter key alone. In these situations, other keys (such as arrow keys) can be used. In particular, for elements with a WAI-ARIA role corresponding to a design pattern, it is recommended to consider the document WAI-ARIA 1.1 Authoring Practices when implementing them.
In the framework, the expression "operable by keyboard and any pointing device" also refers to this definition.
Important note: the use of certain technologies may make focus management too complex or too unstable to rely solely on tab, arrow and enter keys. In this case, providing keyboard shortcuts may be the only way to make the component usable.
The criterion can only be considered compliant if the keyboard shortcuts used are properly documented, functional and comply with critère 12.10.
Criteria in RAWeb 1.1
- 4.11 — Is the viewing of each time-based media, if required, accessible and operable by keyboard and any pointing device?
- 4.12 — Is the viewing of each non-time-based media accessible and operable by keyboard and any pointing device?
- 7.3 — Is each script accessible and operable by keyboard and any pointing device (excluding special cases)?
Definition in RAAM 1.1
Pointing devices in a mobile environment can be, but are not limited to:
A user interface component (link, button, form field, etc.) can be accessed by any pointing device when the user
- can set the focus on the component, regardless of the device;
- can initiate the action provided for by the user interface component by means of a manipulation specific to the device (a certain key on the keyboard, a gesture on the screen, for example);
Warning: for certain user interface components such as potentiometers (slider, rotary knob), several interactions are possible and therefore several manipulations specific to the device may be required to interact with the component. On the keyboard, for example for potentiometers, the direction arrows (right, left, up and down) are used to interact with and modify the component.
In this framework, the expression "accessible and operable by keyboard and any pointing device" also refers to this definition.
Important note: the use of certain technologies may make focus management too complex or too unstable to rely solely on tab, arrow and enter keys. In this case, providing keyboard shortcuts may be the only way to make the component usable. The criterion can only be considered compliant if the keyboard shortcuts used are properly documented, functional and comply with criterion 10.4.