A practical keyboard-only first pass for small-business website owners.
A good-looking homepage is only the beginning. Try completing its most important task without touching your mouse. Can you reach the enquiry link, open the menu and understand where you are? This small exercise turns “the website feels awkward” into a problem your designer can reproduce.
This is a first review, not an accessibility certification. W3C warns that a page can pass simple checks while still having significant barriers. Use this exercise to find work to do, not to award your site a badge.
Choose one journey before you start
Write a plain-language goal, such as “Find the service area and reach the enquiry form.” Keep this first run short. Testing five unrelated journeys at once makes it difficult to remember which control caused the problem.
Open the public page, rather than an editing screen. Write down the page address, browser and date. Put the mouse aside. If you are working with a developer, agree on a safe test environment before trying actions that send messages, place orders or change account information.
Follow the keyboard focus
Use Tab to move between interactive controls and Shift+Tab to move back. Watch for a visible indicator showing which control has focus. Try activating links with Enter. Check that you can reach controls in a sensible order and move away again without getting trapped. Keyboard settings can differ between browsers and operating systems, so record your setup when reporting a problem. See W3C’s keyboard access guidance for the fuller check.
Do not expect Tab to stop at every paragraph. Your immediate question is whether the interactive route works. If a menu needs a mouse hover before its links appear, note the exact menu and what happened rather than guessing at the code underneath.
Write a useful bug report
Compare these two reports:
“The navigation is bad.”
“On the services page in my desktop browser, I pressed Tab from the address bar. The focus reached the logo and then skipped the Services menu. I could reach Contact, but I could not open the service choices without using the mouse.”
The second is an illustrative report, not a finding about a real business. It identifies a page, a sequence and an observable result. A short screen recording can help, provided it contains no customer details, passwords or private account information.
Check the words around the controls
When you reach a form, look for clear labels explaining each field. W3C recommends associating labels with their controls so assistive technology can identify the right label. A developer can inspect that relationship in the markup; seeing nearby words alone does not verify it. Read W3C’s form-label tutorial.
For your notes, separate an observation from an assumption: “The email field has no visible label” is an observation. “No disabled person can use this site” is not something this quick test establishes.
Give each finding a next step
Make four columns: page, action attempted, result, person responsible. Add a fifth column for the retest. Prioritize a blocked essential journey before a cosmetic preference. After a fix, repeat the same steps and record whether the result changed.
Our local-service design concept illustrates why this matters: a visual mockup can suggest a clear customer journey, but it cannot prove keyboard behavior, message delivery or accessibility. Those need testing in the implemented page. The concept below is fictional, not a client success story.
Keep the improvement honest
Use this first pass to start a more complete review involving appropriate accessibility expertise and users. Do not describe the whole site as accessible because one route worked. Continue with our small-business website checklist, then choose the next important journey to examine.
Technical references checked November 16, 2026. The testing worksheet and report examples are our suggested working method.


