Testing for Keyboard Access

When testing for keyboard access, the visual and non-visual parts of accessibility testing begin to overlap. The primary question you need to test for is whether or not all parts of the website or application can be operated entirely with the keyboard. This is very important for people with visual impairments that can’t use the mouse, people with a motor impairment, or some kind of technological limitation. This includes:

Logical tab order

Assistive technologies, such as screen readers and switch control, rely on the tab order to logically navigate a page or application. The focus must not move randomly around the page when they press the tab key. When that happens, the user could get lost, get overwhelmed by the sudden shift in context, or take unreasonably longer than their peers to complete an essential task. Be sure to include all interactive elements such as links, form controls and accordion buttons in the tab order.

You can learn more about this by reading guideline 2.1 of WCAG 2.2 and the Accessible Rich Internet Applications (ARIA) authoring practices.