A practical keyboard check for your business website
Published
Put the mouse aside for a few minutes. Can you find your way around your website, open the menu and reach the information you came for using the keyboard?
That check will not tell you whether the whole website is accessible. It can, however, expose barriers that are easy to miss when you always use a mouse. Start with the pages customers actually use, and record what happens rather than guessing at a fix.
Start with a real task
Choose a simple journey: open a service page, find the areas served, or reach the contact page. Begin at the top of the page and use Tab to move forward through interactive items. Shift+Tab generally moves backward. Browser and operating-system settings can affect which controls receive focus, so note the setup you use.
You do not need to send a real enquiry or place an order to check whether you can reach a control. If a journey requires a submission, use an agreed test environment and process.
Watch where focus goes
As you press Tab, look for a visible indicator around the active link, button or field. Can you tell where you are at each step? Does the sequence make sense for the task, or does it jump unexpectedly around the page? Check whether sticky headers, banners or popups hide the focused item.
Try the skip-to-content link if the site offers one. It should make it easier to move past repeated navigation. W3C's focus guidance explains why a visible indicator matters for people using a keyboard.
Open and leave the controls
Use the keyboard to open the menu, follow a link and return. If the page has expandable questions, a carousel or a dialog, check whether you can operate its controls without switching to the mouse. Try the keys indicated by the interface; Enter, Space, arrows and Escape may have different roles depending on the control.
A dialog may intentionally keep focus inside while it is open. The important question is whether there is a usable keyboard way to close it and continue. If focus becomes stuck, note the steps and tell the person responsible for the site. W3C's explanation of keyboard traps describes the distinction.
Write down what you find
For each issue, record the page address, browser and device, the steps you took, and what you expected to happen. A short screen recording or screenshot can help show a missing focus indicator; avoid capturing private customer information. Test the same journey after a fix to see whether the specific problem has changed.
Do not remove focus outlines simply because they look different from the rest of the design. Ask the developer to investigate the underlying behavior and provide an indicator people can see.
Know what the check does not cover
A successful keyboard pass is a starting point, not certification or proof of legal compliance. It does not replace checking screen-reader use, color contrast, text resizing, captions, forms, different devices and the other requirements relevant to the site. It also cannot substitute for involving people with disabilities in evaluation.
For a broader starting point, use W3C's Easy Checks and plan a more thorough accessibility review. One clear, reproducible finding is useful: it gives the person maintaining the site a concrete place to begin.
