Registry · Operable

2.1.2 — No Keyboard Trap

Level A Operable

Operational summary

IF focus enters a component by keyboard, provide a keyboard route out. Explain nonstandard exit methods. An operable modal with a discoverable close mechanism may contain focus temporarily without constituting an inescapable trap.

This is an original implementation summary, not replacement normative text. The sources below supply the precise requirement, its definitions and its qualifications.

Primary sources

• Normative text — W3C WCAG 2.2 Recommendation
• Understanding 2.1.2 — explanatory guidance

Registry record

Applicability and assessment start unset by design — no product has been evaluated. Instantiate the entry for an actual product, assign an owner and retain evidence.

{
  "criterion_id": "2.1.2",
  "level": "A",
  "name": "No Keyboard Trap",
  "rule_definition": "../03-WCAG22-AA-REGISTRY.md#sc-2-1-2",
  "normative_source": "https://www.w3.org/TR/WCAG22/#no-keyboard-trap",
  "understanding_source": "https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap.html",
  "applicability_status": "NOT_EVALUATED",
  "assessment_status": "NOT_TESTED",
  "owner": null,
  "test_instance_ids": [],
  "exception_evidence_ids": []
}

Example rules referencing this criterion

• LAKA-WCAG-MODAL-PATTERN

This criterion as JSON →