Not everyone uses a mouse. People with motor impairments such as tremors, limited fine motor control, or paralysis may rely on a keyboard, a switch device, or voice control that emulates keystrokes. Screen reader users also navigate almost entirely by keyboard. For all of these users, an interface that can only be operated by pointing and clicking is simply unusable, which is why WCAG 2.1 requires that all functionality be available from a keyboard.
This topic covers four related ideas. Keyboard operability means every control — buttons, menus, form fields, modals, custom widgets — can be reached and activated with keys like Tab, Shift+Tab, Enter, Space, and the arrow keys, and that focus is never trapped. Logical tab order and focus management mean the sequence of focus follows the visual and logical reading order, that focus is visibly indicated at all times, and that it is moved deliberately when dialogs open and close. Skip navigation links let keyboard users jump past long repeated menus straight to the main content. Finally, custom components built from generic elements must reproduce the keyboard behavior that native controls provide for free.
The three videos below are practical, demonstration-based walkthroughs rather than lectures. As you watch, pay attention to the specific keys being pressed, to whether the focus indicator is always visible, and to the moments where the presenter points out a breakdown — focus disappearing, order jumping unexpectedly, or a control that cannot be activated. Try the same steps on a site you use often; you will likely find barriers within a minute or two.
A short, focused walkthrough from Nielsen Norman Group on testing your own site using only a keyboard. Based on its title and description, it covers checking for clear, visible focus states and confirming that interactive elements can be reached and operated without a mouse. Expect a quick, structured testing routine you can repeat on any page.
NN/g is a long-established and reliable usability research organization, and the brevity makes this a good first introduction to keyboard operability and focus visibility before moving to longer demonstrations.
Pope Tech, an accessibility tooling company, explains which keys to use when navigating a site with the keyboard alone and what problems to watch for during testing. The description indicates it names the specific keystrokes — Tab, Shift+Tab, Enter, Space, arrows — and the common failures associated with each. It is framed as a repeatable manual testing procedure.
It directly supports the tab order and operability subtopics by giving you a concrete key-by-key checklist, which is exactly what you need when evaluating custom components that may not respond to the expected keys.
A longer session from ExpandTheRoom combining screen reader use with keyboard navigation, with links to the WCAG 2.1 guidelines referenced in the description. The extra runtime allows for a fuller demonstration of moving through a real page and interpreting what is announced as focus moves. Expect coverage of how keyboard order and screen reader output are connected.
This video ties keyboard behavior back to WCAG and to assistive technology output, showing why logical focus order and features like skip links matter beyond sighted keyboard users.
Together these videos move from standards to practice. The WCAG references in the ExpandTheRoom walkthrough connect keyboard operability to the formal guidelines named in MO1, while all three model a hands-on inspection method that you can apply when auditing an interface for motor-related barriers, supporting MO2. The specific failure patterns they highlight — missing focus indicators, illogical tab order, unreachable custom controls — give you a concrete punch list for revising your own prototypes under MO3. Finally, seeing a real user journey conducted entirely by keyboard and screen reader makes the cost of exclusion tangible rather than abstract, which is the reflective work asked of you in MO4.
These videos were chosen from YouTube on October 10, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.