Category: Keyboard

Tests that require manual keyboard testing to verify (also covers Screen Readers)

**Related Guidelines**
42	1.4.13 Content on Hover or Focus (AA)	Content generated by hover or focus can be dismissed without moving hover or focus.
43	1.4.13 Content on Hover or Focus (AA)	Content generated by hover or focus of an element can be hovered over without the content disappearing.
44	1.4.13 Content on Hover or Focus (AA)	Content generated by hover or focus of an element does not disappear until dismissed, is no longer valid, or hover or focus is removed.
45	2.1.1 Keyboard (A)	All interactive elements must be able to be navigated to and interacted with using a Keyboard only.
46	2.1.1 Keyboard (A)	Timing of keystrokes must not be required for interacting with any functionality.
47	2.1.1 Keyboard (A)	Functionality available when hovering with a cursor must be available to keyboard input.
48	2.1.2 No Keyboard Trap (A)	Focus that enters any element must be able to leave that element. If the method requires more than ESC, Arrow Keys, or Tab, the user must be informed of the method.
49	2.1.4 Character Key Shortcuts (A)	If any keyboard shortcut only requires letter, number, punctuation, or symbol characters, an option exists to turn it off, remap to include CTRL or ALT modifiers, OR be active on focus only.
54	2.4.1 Bypass Blocks (A)	Content which repeats on multiple webpages has a mechanism of skipping over it.
56	2.4.3 Focus Order (A)	Focus order must follow a logical sequence. Tabindex values must not interfere with the proper tab sequence of the page.
57	2.4.3 Focus Order (A)	Dialog content must gain focus immediately or as the next press of TAB once activated. Dismissing dialog content returns focus to the trigger or to the next element in DOM after the trigger.
62	2.4.7 Focus Visible (A)	Every focusable element has a focus indicator present.
63	2.4.11 Focus Not Obscured (Minimum) (AA)	Elements that currently have focus may never be hidden by other elements (such as a sticky header).
73	3.2.1 On Focus (A)	When a user interface component gains focus, it may not trigger a change of context. (Submission of a form, new window launch, immediate change of focus, changing content on the page where such that the purpose is different)