2.7 KiB
2.7 KiB
2.1.1 Keyboard
- Level: A
- Guideline: 2.1 Keyboard Accessible
- Principle: 2 Operable
What it is
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.
How to test
- Check: 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.
- Use the sufficient techniques below as acceptable methods when applicable.
- Confirm none of the common failures apply.
Sufficient techniques (W3C)
- G202: Ensuring keyboard control for all functionality
- H91: Using HTML form controls and links
- PDF3: Ensuring correct tab and reading order in PDF documents
- PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents
- PDF23: Providing interactive form controls in PDF documents
- G90: Providing keyboard-triggered event handlers
- SCR20: Using both keyboard and other device-specific functions
- SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons
- SCR2: Using redundant keyboard and mouse event handlers
Advisory techniques (W3C)
- Using WAI-ARIA role, state, and value attributes if repurposing static elements as interactive user interface components (future link)
- SCR29: Adding keyboard-accessible actions to static HTML elements
Common failures (W3C)
- F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function
- F55: Failure of Success Criteria 2.1.1, 2.4.7, 2.4.13, and 3.2.1 due to using script to remove focus when focus is received
- F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links
Notes
- Note 1: 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.
- Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
Resources
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#keyboard
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#keyboard