Keyboard access exposes pointer-only architecture

A pointer-only interface hides architectural defects until someone tries completing the same task without a mouse.

WCAG keyboard guidance requires all functionality through a keyboard interface, except input inherently dependent upon movement paths.

Meeting that baseline requires logical focus order, visible focus, reachable controls, predictable activation, and deliberate modal containment.

A clickable div usually fails because appearance and pointer events never provide the complete control contract.

When semantics establish control meaning, manual tasks verify actual operation beyond static markup.

Keyboard testing also benefits switch devices, speech input, power users, and anyone with an unavailable pointing device.

Begin every critical flow using only Tab, Shift Tab, Enter, Space, Escape, and arrow keys where expected.

If completion becomes impossible or focus disappears, the interface architecture is incomplete rather than merely inconvenient.