2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
SC 2.1.2 supports the principle of Operable because all users must be able to navigate to use websites, documents, and applications. The intent of this SC is to ensure that content does not “trap” keyboard focus within subsections of content, leaving keyboard-only users no way to return to other content. In essence, a “keyboard trap” occurs when a person who uses a keyboard cannot move focus away from an interactive element or control using only the keyboard. A keyboard navigation trap can occur in a number of ways, e.g., on a specific element of a page, a section of the page, or a popup message that cannot be dismissed using the keyboard.
Impact of Nonconformance with SC 2.1.2 No Keyboard Trap
| Type of Disability | Description of Impact |
|---|---|
| 302.1 Without Vision | Users who are blind cannot use a mouse to interact with electronic content and typically use an assistive technology, such as a screen reader, to get audible or other alternative output for the information represented visually. To be able to navigate the content, understand its structure and relationships, and understand the meaning of content represented in graphics and images, the content must provide textual and programmatic cues in addition to the content presented purely visually. |
| 302.2 With Limited Vision | Users with limited vision may have widely different visual perception. Individuals with limited vision may or may not use assistive technologies. Therefore, in addition to textual and programmatic cues necessary for assistive technologies, ICT must also present content consistently and predictably. Users who view content with magnifiers may not pick up alerts, warnings, or other content if such content is presented outside of a consistent and predictable navigation pattern or if the content is not itself viewable at large magnification. Content that becomes distorted when magnified can also prevent some users with limited vision from being able to understand or interact with the content. |
| 302.7 With Limited Manipulation | Some users may not be able to perform actions that require fine motor control (clicking and dragging), path dependent gestures (pattern-based passcodes), or simultaneous actions (Ctrl + Alt + Del). Providing alternative means to perform the same actions, such as entering the size specifications in an input field to resize an object or allowing sequential key entries, can enable users with limited manipulation to interact with the same content. |
| 302.8 With Limited Reach and Strength | Some users may lack sufficient strength to perform actions such as squeezing, grasping, or depressing a hardware control. Some users, including those in wheelchairs or of shorter stature, may not be able to reach controls that are placed too high or too far away from where a user would access the device controls or interface. ICT designers and developers must consider a broad range of statures, strength and dexterity limitations, and the needs of wheelchair users in order to provide interfaces that are operable with limited reach and/or strength. |
Applicability of Success Criteria 2.1.2 No Keyboard Trap
| Technology | Applicability of SC 2.1.2 No Keyboard Trap |
|---|---|
| Web | Keyboard traps typically arise from content that is embedded within a web page and isolates the keyboard navigation or tab order from the other content. Developers can typically overcome such keyboard traps by providing links, controls, or other functions within such content that allow the user to close or exit the content and/or navigate to a location outside of the content. |
| Software | Keyboard traps typically arise from embedded content or content that is designed to isolate the keyboard navigation or tab order from the other content. Developers can typically overcome such keyboard traps by providing links, controls, or other functions within such content that allow the user to close or exit the content and/or navigate to a location outside of the content. |
| Office documents | Keyboard traps are not typically a problem in Office documents unless a document author or developer adds custom controls or code to a document. When an author or developer adds custom controls or code, they must identify whether such content isolates keyboard navigation or tab order from other document content. As described above, a content author or developer can typically overcome such keyboard traps by providing links, controls, or other functions within such content that allow the user to close or exit the content and/or navigate to a location outside of the content. |
| PDF documents | Keyboard traps typically arise from embedded content or custom-coded content that may isolate the keyboard navigation or tab order from the other content. Developers can typically overcome such keyboard traps by providing links, controls, or other functions within such content that allow the user to close or exit the content and/or navigate to a location outside of the content. |
| Mobile Native | Keyboard traps typically arise from embedded content or content that is designed to isolate the navigation or tab order from the other content. Developers can typically overcome such tab order navigation traps by providing links, controls, or other functions within such content that allow the user to close or exit the content and/or navigate to a location outside of the content. |