Not everyone who navigates by keyboard is a screen-reader user. Motor disabilities, RSI and switch devices all ride the same Tab key — which is why keyboard support is the first thing we test.
Big targets, forgiving spacing
WCAG 2.2 asks for 24×24 pixel targets at minimum; we aim larger. Fingers tremble, pointers drift, and a generous button forgives both.
Nothing that requires holding or dragging
Drag-and-drop, long-press and hover-only menus exclude switch users entirely. Every interaction here has a simple click-or-keypress alternative.
The Tab order is the interface
When focus moves the way the page reads, a keyboard user can predict every next stop. That predictability is worth more than any animation.
Leave a Reply