Link to documentation: https://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable **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) *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 * Annotate expected keyboarding behavior with these [Accessibility Bluelines](https://www.figma.com/community/file/779827094223635810) (Figma) * Use the [ChromeLens](https://chrome.google.com/webstore/search/chromelens?hl=en-US) Google Chrome extension to trace tab path * Use the [NerdeFocus](https://chrome.google.com/webstore/search/nerdefocus?hl=en-US) Google Chrome extension to always show where the the focus is, option to record too