• Success Criterion 2.1.2
  • Conformance level A

2.1.2 · No Keyboard Trap

Lesson overview · No Keyboard Trap

In plain language

Keyboard focus must never get stuck anywhere on the page.

Who it affects

All keyboard and screen-reader users who can become stuck inside a component.

How to check

Tab through the whole page including embeds and popups: confirm you can always Tab or Esc back out of every component. Worked example — A grocery delivery app's shopping cart: tab into a rich-text editor and press Tab: if it's captured for indentation with no documented alternate exit key (and none is advised on screen), it fails.

Common misconception

A modal that intentionally holds focus is fine, and expected. The failure is a modal that holds focus with *no* documented way out, no Esc, no visible close button. Real example: on an email client's compose window, keyboard focus can get stuck inside an embedded plugin/format (video player, widget) and the user cannot Tab back out to the rest of the page.

Learn more

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

Scenarios in this lesson