How to test Keyboard accessible

Which standards this maps to

Korean standard (KWCAG 2.2)

6.1.1 Keyboard accessible

Operable

International standard (WCAG 2.2)

2.1.1 Keyboard (A) ↗2.1.2 No Keyboard Trap (A) ↗

How to test it

Operate every feature using only the keyboard; ensure no keyboard traps.

What automation covers

5 automated rules judge this checkpoint. Each comes with remediation guidance.

• Server-side image maps are not accessible server-side-image-map

  Replace server-side image maps with client-side maps or plain links.

• Scrollable regions must be keyboard accessible scrollable-region-focusable

  Give scrollable containers tabindex 0 and an accessible name.

• Frames with focusable content must not have tabindex=-1 frame-focusable-content

  Remove tabindex=-1 from frames containing focusable content.

• Interactive controls must not be nested nested-interactive

  Do not nest interactive elements; merge or separate them.

• Clickable element is not keyboard operable a11ychk:keyboard-clickable

  Elements with onclick but no keyboard focus/handler can't be operated by keyboard. Prefer <button>, or add tabindex, role, and key handlers.