Keyboard navigation means every interactive element of a learning platform — video player controls, course menus, quiz inputs, modal dialogs, and navigation links — can be reached and activated using only the keyboard, without a mouse or touch input. WCAG 2.1 AA Success Criterion 2.1.1 (Keyboard) requires that all functionality be operable via keyboard interface unless the underlying function requires path-dependent input. For a video player, the standard expectations are: Tab moves focus through controls, Enter or Space activates the focused control, arrow keys adjust volume or seek position, and Escape closes overlays. Keyboard navigation is important for users with motor impairments who cannot use a pointing device, as well as for power users and screen-reader users who navigate primarily by keyboard. A common failure mode is custom-built player controls using div or span elements that are never focusable by default and receive no keyboard event handlers; the fix is to use native button and input elements or add tabindex and keydown handlers explicitly. A related WCAG criterion, 2.4.7 (Focus Visible), requires that the element that currently holds keyboard focus always have a visible focus ring, which is frequently suppressed by CSS resets in learning platform themes. Testing keyboard navigation should include a full walkthrough of the learner journey — from login to completing a video lesson — using only Tab, arrow keys, Enter, and Escape.
