WCAG 2.1.2: No keyboard trap
In European law this criterion is EN 301 549 clause 9.2.1.2 — chapter 9, the part of the harmonised standard that applies to websites under the European Accessibility Act.
What automation checks
axe-core has no rule for this criterion, so our own browser check a11y-keyboard-trap walks the page with the Tab key in a real browser and flags focus that cannot move past an element.
What automation cannot prove
An automated test finds some failures of WCAG 2.1.2; it cannot confirm the criterion is met. Whether the result actually works for people — in context, with real content — is a judgement call that needs a human auditor. Nothing on this page is a statement of conformance or legal advice. The full map of what our scanner covers and where it stops is on what our scanner checks.
Related guides
- Audyt WCAG i deklaracja dostępności: przewodnik
- EN 301 549: the European accessibility standard explained
- Accessibility Overlays vs. Real WCAG Audits: What Actually Delivers Compliance
- ARIA Labels Explained: aria-label vs aria-labelledby vs aria-describedby
- How to Write Alt Text: A Practical Guide (WCAG 1.1.1)
- WCAG accessibility audit: process, deliverables and how to choose a vendor
- WCAG conformance levels: A, AA and AAA — which one actually applies to you
Does your site pass this check?
Free instant scan. No signup required. WCAG 2.1.2 is one of the criteria it tests.
Scan website