Operable 2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond a keyboard.
Examples
- A slider that can be operated by dragging the thumb can also be operated with a keyboard via buttons or inputs.
- A list that can be reordered by dragging and dropping also has button controls.
Success Criteria
Criterion | Level | Description |
---|---|---|
2.5.1 | A | Content can be controlled with a range of input types. |
2.5.2 | A | Prevent accidental pointer input by either not executing functions on down-events, by only completing functions on up-events, or by making sure the action of up-events will reverse the action of the corresponding down-events. |
2.5.3 | A | Visible text labels and programmatic names of the same control should match. |
2.5.4 | A | Any function that can be operated by device motion also has a corresponding component control. |
2.5.5 | AAA | All targets for pointer inputs should be at least 44px by 44px. |
2.5.6 | AAA | The content on the website does not restrict the type of input modalities that can be used (such as touch screen only interactions). |