Warning:
This wiki has been archived and is now read-only.
2.1.1 Keyboard
From Automated WCAG Monitoring Community Group
Success criterion 2.1.1 Keyboard: 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. (Level A)
Background
Which elements / situations are tested?
All elements that respond to pointer presence, activation or that sollicit interection. The actual visibility of keyboard focus is treated elsewhere.
- All links, focus SC2-1-1-links-tabbable
- All links, activation SC2-1-1-links-activation
- All clickable regions and elements, focus SC2-1-1-nonlinks-tabbable
- All clickable regions and elements, activation SC2-1-1-nonlinks-activation
- All form elements, focus SC2-1-1-inputs-tabbable
- All form elements, interaction SC2-1-1-inputs-activation
- All interactive regions accepting input, focus SC2-1-1-noninputs-activation
- All interactive regions accepting input, interaction SC2-1-1-noninputs-activation
- All regions featuring pointer related dynamics, focus SC2-1-1-mouse-activation
- All regions featuring pointer related dynamics, effect SC2-1-1-mouse-effect
Expert input
Are there other elements in the page which respond to user/pointer actions?
Open questions
- "All interactive regions accepting input, focus SC2-1-1-noninputs-activation" and "All interactive regions accepting input, interaction SC2-1-1-noninputs-activation" refer to those sites that develop their own select boxes, or checkboxes. This is actually an accessibility problem in and of itself, all user input should be by type input, therefore, do we need to test for this