1. Home
  2. :
  3. WCAG Guidelines
  4. :
  5. 2.1.2 No Keyboard Trap –...

2.1.2 No Keyboard Trap – Level A

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.

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.

Understanding Success Criterion 2.1.2: No Keyboard Trap

Checklist – Components

Accordions

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Cards

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Dialogs

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Drag-and-drop components

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Forms

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Global Header

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Local Navigation

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Menus

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Tables

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Tabsets

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Trees

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone

Testing – Special Testing Scenarios

Keyboard Navigation

TestPriorityAutomated test?
Is the component free of keyboard traps?HighNone