Operable / 2.1 Keyboard Accessible
2.1.1Keyboard
Level AEnsure all functionality is operable via keyboard alone, without requiring specific timing for individual keystrokes. Even custom, mouse-oriented widgets must be reachable with Tab and operable with Enter, Space, or arrow keys. The only exception is when the underlying function itself inherently requires path-based input, such as a freehand signature -- simply choosing handwriting as an input method doesn't qualify.
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(9)
Show all (9)
- G90: Providing keyboard-triggered event handlers(opens in a new tab)waic.jp(opens in a new tab)
- G202: Ensuring keyboard control for all functionality(opens in a new tab)waic.jp(opens in a new tab)
- H91: Using HTML form controls and links(opens in a new tab)waic.jp(opens in a new tab)
- PDF3: Ensuring correct tab and reading order in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
- PDF11: Providing links and link text using the Link annotation and the /Link structure element in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
- PDF23: Providing interactive form controls in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
- SCR2: Using redundant keyboard and mouse event handlers(opens in a new tab)waic.jp(opens in a new tab)
- SCR20: Using both keyboard and other device-specific functions(opens in a new tab)waic.jp(opens in a new tab)
- SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons(opens in a new tab)waic.jp(opens in a new tab)
Advisory Techniques(1)
Failures(3)
- F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links(opens in a new tab)waic.jp(opens in a new tab)
- F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
Normative References
- Success Criterion 2.1.1 Keyboard — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Keyboard — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.