← Back to all categories
Error keyboard-1 · WCAG 2.1.2

Keyboard trap

Focus enters this text area and cannot leave via keyboard alone. The Tab key is captured by JavaScript and focus is forced back into the element. (Press Escape to override and release focus in this demo.)

Error keyboard-2 · WCAG 2.1.1

Click handler on div with no keyboard support

This div has an onClick handler but no tabIndex, no role, and no onKeyDown handler. Keyboard users cannot activate this interactive element.

Click to Activate
Error keyboard-3 · WCAG 2.4.7

Focus indicator removed with no replacement

These interactive elements have outline:none and no replacement focus style. Keyboard users cannot see which element currently has focus.

Link without focus ring
Error keyboard-4 · WCAG 2.4.3

Positive tabindex disrupting focus order

These fields use positive tabindex values (5, 3, 1) which override the natural DOM order. The focus order becomes unpredictable and confusing.