WCAG 2.2
Principle 2 Operable: Guideline 2.1 Keyboard Accessible – WCAG 2.2

WCAG 2.2 2.1.2: No Keyboard Trap (Level A)

If keyboard focus can move into a component, it can move out again using the keyboard alone, and where anything beyond unmodified arrow, Tab or standard exit keys is needed the user is told how. Applies to all content on the page (non-interference).

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 3 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • 10.2.1 10.2.1 Keyboard accessible
  • 11.2.1 11.2.1 Keyboard accessible
  • 9.2.1 9.2.1 Keyboard accessible

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Principle 2 Operable: Guideline 2.1 Keyboard Accessible – WCAG 2.2

Query this from an agent

The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.