Understanding Success Criterion 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.

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.

Intent of Success Criterion 2.1.2: No Keyboard Trap

The intent of this Success Criterion is to ensure that that content does not "trap" keyboard focus within subsections of content on a Web page. This is a common problem when multiple formats are combined within a page and rendered using plug-ins or embedded applications.

There may be times when the functionality of the Web page restricts the focus to a subsection of the content, as long as the user knows how to leave that state and "untrap" the focus.

Benefits of Success Criterion 2.1.2: No Keyboard Trap

Examples of Success Criterion 2.1.2: No Keyboard Trap

Resources Success Criterion 2.1.2: No Keyboard Trap

Techniques for Success Criterion 2.1.2: No Keyboard Trap

Sufficient Techniques

  1. Ensuring that users are not trapped in content
  2. Preventing a keyboard trap in Flash content

Advisory Techniques

Failures