Success Criterion 2.1.2
Conformance level A

Non-Standard Focus Exit Key That’s Never Explained to Users

2.1.2 — No Keyboard Trap

Scenario

Setting

A professional networking site's profile editor

What’s wrong

Non-standard exit exists (e.g., Ctrl+M) but user is never advised of it — normative fail of the advisory clause.

Example

// modal traps Tab inside with no Escape handler

Why it matters

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

How to test

Look for any documentation or on-screen text advising a non-standard exit key (e.g., Ctrl+M): if such a key exists but the user is never told about it, it fails the advisory requirement.

How to fix

Focus must always be able to leave the component using Tab/Shift+Tab or Esc (or a standard method the user is told about). document.addEventListener('keydown', e => { if (e.key === 'Escape') closeModal(); }); Any component that captures focus needs a standard way out — Escape, or focus cycling back to a close control.

Outcome

On a professional networking site's profile editor, this barrier is gone for all keyboard and screen-reader users who can become stuck inside a component — they can finish what they came here to do.

Who is affected