2.1.2 No Keyboard Trap

Level: A
Guideline: 2.1 Keyboard Accessible
Principle: 2 Operable

What it is

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.

How to test

Check: 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.
Use the sufficient techniques below as acceptable methods when applicable.
Confirm none of the common failures apply.

Sufficient techniques (W3C)

G21: Ensuring that users are not trapped in content

Common failures (W3C)

F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type

Notes

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Resources

WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#no-keyboard-trap
Understanding: https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap.html
Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#no-keyboard-trap

Back to 2 Operable index

1.8 KiB Raw Blame History