Using a keyboard without a mouse is one of the simplest ways to reveal serious website accessibility barriers. It shows whether important links, menus, forms and controls can be reached and operated.
This preliminary test does not replace a complete accessibility audit and does not reveal every problem faced by screen reader or other assistive technology users. It does, however, expose barriers that often block critical tasks.
Which keys should you use?
- Tab – move to the next interactive element.
- Shift + Tab – move to the previous interactive element.
- Enter – activate a link or certain controls.
- Space – activate a button, checkbox or supported control.
- Arrow keys – move within menus, radio groups, tabs and select controls.
- Escape – close a dialog, menu or temporary layer.
Keyboard focus example
Press Tab to move through the following links and button. The visible yellow outline shows the element that currently has focus.
1. Start at the top of the page
Load the page, place focus in the browser address bar and press Tab until focus enters the page. Continue pressing Tab and observe the order.
- Is focus always clearly visible?
- Are important links and buttons included?
- Does focus avoid invisible content?
- Does the order follow the visual and task logic?
- Does focus unexpectedly return to the beginning?
2. Test the main menu
Confirm that every navigation link is reachable. Open dropdowns using Enter or Space and check whether their items can be reached and closed without a mouse.
3. Test dialogs and temporary layers
Open cookie settings, login dialogs or other overlays. Focus should move into the dialog, stay within it while open, and return to the trigger after closing.
- The close control is reachable and has a clear name.
- Escape closes the dialog where expected.
- Focus does not move behind the overlay.
- Focus returns to the control that opened it.
4. Complete and submit a form
Reach every field and control, submit incomplete or invalid data, and confirm that errors are understandable and easy to locate.
- Every field has a visible and programmatic label.
- Checkboxes and radio buttons can be operated.
- Error messages explain what needs to change.
- Focus or an error summary leads the user to the problem.
5. Test a complete user journey
Do not stop after testing individual controls. Complete the task that matters to the business.
- Find a product and select a variation.
- Add it to the basket and change the quantity.
- Complete registration, booking or checkout.
- Resolve an error and confirm the final result.
6. Repeat the test in a narrow viewport
Mobile navigation and responsive components often behave differently. Resize the browser or test at 200–400% zoom and repeat the keyboard journey.
What counts as a serious problem?
- A critical control cannot be reached.
- Focus is invisible or trapped.
- A menu, dialog or checkout step cannot be operated.
- The order is confusing or moves through hidden content.
- Errors cannot be found or corrected.
What should you do with the findings?
Record the URL, component, exact steps, expected behaviour and observed result. Group repeated failures by shared component and verify the complete journey after remediation.
Trusted sources
Found a keyboard barrier?
Send the website URL and the task that cannot be completed. Webmedic can assess the complete journey and provide a practical remediation path.