Keyboard Operability
What Is Keyboard Operability in Accessibility?
Keyboard operability refers to the ability to use all features and navigate digital content (websites, software, applications) entirely via the keyboard, without requiring a mouse or touch interface. This is a crucial requirement for:
- People with motor disabilities who cannot use a mouse
- People who are blind or have severe visual impairments, relying on Screen readers
- Users who prefer or need assistive technologies such as alternative input devices (e.g., sip-and-puff systems, mouth sticks)
A fully keyboard-operable website allows the user to:
- Move through menus, forms, buttons, modals, and sliders using the Tab, Arrow, Enter, and Space keys
- Access all content and interactions (including dropdowns, pop-ups, etc.) without getting stuck
- See clear visual focus indicators that show where they are on the page
Keyboard operability is a fundamental requirement under standards like WCAG 2.1 (Success Criterion 2.1.1) and the BITV 2.0 in Germany. It ensures equal digital participation and is part of legal accessibility compliance.
Testing for keyboard operability involves navigating a site using only the keyboard, identifying any elements that cannot be accessed or operated.
Many people cannot use a mouse: people with motor impairments, screen reader users and anyone who simply works faster with the keyboard. A page is keyboard-operable when all functions can be reached and triggered with Tab, Shift-Tab, arrow, Enter and Space keys.
What matters is a logical order, a clearly visible focus outline and avoiding keyboard traps from which you cannot get out. Skip links at the top of the page help to jump straight to the main content without going through the entire menu every time. Menus, dialogs and sliders need their own keyboard logic.
You can test this quickly: put the mouse aside and work through your most important flows using only the keyboard. Anything that cannot be reached or is not visible belongs on the defect list and should be fixed before publication.
Keyboard operation most often fails with custom-built components such as carousels, dropdowns and overlays. Where possible, use native HTML elements such as button and link, as they already bring keyboard behaviour and role with them.
In short: Keyboard Accessibility: Ensuring Inclusive Web Use.