A website can look polished and still be frustrating to use without a mouse. Someone may navigate with a keyboard because of a motor disability, an injury, assistive technology, or simply personal preference. If links, menus, and forms cannot be reached in a sensible order, that person may be unable to contact the business or complete a basic task.
You do not need expensive testing software to uncover many of these problems. A simple keyboard-only walkthrough can reveal missing focus indicators, trapped menus, skipped controls, and confusing interaction patterns. Here is a repeatable test a small business owner can carry out before a site launch or after a major redesign.
What keyboard navigation should accomplish
Visitors should be able to move to interactive controls, identify which control currently has focus, activate it, and move away again. On most desktop browsers, Tab moves forward between focusable controls and Shift + Tab moves backward. Enter commonly activates links and buttons; Space activates many button controls. The exact keys for selecting options depend on the control and operating system.
The goal is not to make every visual item focusable. Headings and ordinary paragraphs generally do not belong in the tab sequence. The focus path should follow the content’s meaningful reading and interaction order.
Begin with a ten-minute keyboard-only walkthrough
Open the homepage in a desktop browser, disconnect your mouse from the process, and reload the page. Use Tab from the beginning and watch where focus goes. Keep a small record of each problem and the page where you found it. Test a typical service page and the contact page, too: the homepage alone cannot reveal every issue.
- Press Tab once. Can you see which link or button has focus?
- Continue through the header and navigation. Is the order predictable?
- Open any menu using the keyboard. Can you reach and choose its items?
- Use Shift + Tab to backtrack. Can you reverse direction without becoming stuck?
- Reach the main call to action, then the contact form. Can you complete the primary task?
- Repeat the test at a narrow browser width, where the navigation may change into a menu button.
If focus disappears, jumps around unpredictably, or enters a component and cannot leave, make a note of the exact control and the keys you used. Reproducible steps make later repairs much faster.
Check that keyboard focus stays visible
Test forms as complete tasks, not isolated fields
What a keyboard test does not prove

A focus indicator is the outline, underline, highlight, or comparable visual treatment that tells a keyboard user where they are. It must be distinguishable from the unfocused state and visible against the surrounding colors. If you press Tab but cannot see anything change, a stylesheet may have removed the browser’s default outline without providing a usable replacement.
Pay particular attention to text links in the main content, buttons on photographic backgrounds, light-colored header links, and form inputs. Test both normal and high-contrast-looking backgrounds. A hover effect alone does not help someone who never moves a pointer over the element.
A good fix preserves a strong focus treatment, often through the CSS :focus-visible selector. Do not solve the problem by making everything bright or adding focus rings to noninteractive decoration. Apply the visual cue to controls people can actually use.
Make sure dropdowns, dialogs, and mobile menus are operable
Navigation menus and popups are common places for keyboard access to fail. A menu that opens only when a mouse hovers over it can hide important service links. A popup can also send focus behind its overlay, while an animated mobile menu may trap focus in hidden items.
For each component, check whether it opens using a keyboard, whether the current location of focus remains clear, whether items can be reached in a meaningful order, and whether the user can close or leave it. Escape behavior is especially useful for dialogs and many expandable interfaces, although behavior depends on the widget pattern.
If the page jumps to the top, the entire screen begins scrolling sideways, or focus lands on links that cannot be seen, do not assume these are cosmetic flaws. They may prevent someone from reaching the information they came for. For broader mobile layout checks, see the existing guide to troubleshooting mobile website layout problems.

A contact form is not accessible merely because the cursor can enter the Name field. Start at the first field and move all the way through submission without touching the mouse. You should be able to understand each field’s purpose, select any checkboxes, activate the submit button, and read the resulting confirmation or validation messages.
Try submitting the form with a required field empty. Does the error explain what needs correcting? Does focus remain somewhere useful, or does it move to an unrelated part of the page? Then complete the fields with test information and confirm the page presents a clear outcome. A form can also appear to submit while its email delivery is broken, so delivery testing is a separate operational check.
If you discover a problem, the related article on why website contact forms stop working covers practical diagnosis beyond keyboard access.
Look for a sensible focus order
Focus normally follows the document structure. Visually moving an element with CSS does not necessarily move it in the keyboard sequence. That can create an especially confusing page when columns stack differently on mobile or when a promotional button appears visually near the top but is reached only after dozens of unrelated links.
Work through each page in the order an unfamiliar visitor would use it: navigation, main content, useful links, forms, then supporting footer controls. The exact order varies by design, but jumps that appear to have no reason are worth investigating. Avoid forcing a custom order with positive tabindex values; fixing the underlying HTML order is usually more maintainable.

Passing a manual keyboard test is valuable, but it does not certify full accessibility. Screen readers may announce controls incorrectly even when they can be reached with Tab. Some users operate switch devices, speech input, touch exploration, or browser zoom. Color contrast, text alternatives, page structure, and error communication also deserve review.
For a broader review, the existing website accessibility launch checklist is a useful companion if that destination is confirmed live. For formal criteria, consult the W3C WCAG 2.2 quick reference rather than treating one visual test as a certificate.
Prioritize repairs by whether they block a task
Fixing every issue matters, but an organized queue helps a small business decide where to start. First address keyboard traps, inaccessible navigation, and unusable contact or checkout controls. Next address missing focus indicators, confusing order, and poorly communicated errors. Then review less frequently used interactive widgets and content-specific edge cases.
Retest after each repair rather than assuming that changing the code fixed the experience. A correction to one menu may affect another version of the menu at a different screen width. If a template supplies the same navigation to dozens of pages, test representative page types before and after deploying a template-wide change.
A practical routine to repeat
Keep a short keyboard audit checklist with the website’s regular maintenance notes. Run it after changing navigation, installing a new interactive plugin, modifying forms, or redesigning major sections. A quick check before publishing an important landing page can prevent visitors from encountering a problem that is inexpensive to catch early.
When recurring keyboard problems are tied to the theme, page builder, or interaction scripts, targeted WordPress troubleshooting support may be more appropriate than repeatedly adjusting colors or spacing. The most useful outcome is not a perfect-looking checklist; it is a site where people can find information and complete important tasks without being blocked by the interface.
