Practical guide
Check Whether a Page Works With Your Keyboard
Try a short keyboard journey to see whether a site's controls remain understandable and reachable.
Choose one ordinary journey
You do not need to audit an entire website to notice whether a simple keyboard journey feels workable. Pick a familiar task such as reaching the navigation, opening a category, or moving to an article link. W3C guidance identifies keyboard reachability and visible focus as important considerations for interactive elements. Begin with the controls you actually need. For example, a directory may offer useful content, but if you cannot tell which navigation link is currently selected, reaching that content becomes much harder without a pointing device.
Watch where focus goes
As you move through the page using your usual keyboard navigation, look for a visible indication of the current control. Notice whether the order makes sense for the task. A route that jumps unpredictably between unrelated parts of the page can be difficult to follow even when individual links are reachable. Keep your observation specific: 'The current link is hard to distinguish' or 'The search control appears after a long sequence of unrelated items.' This is more useful than the broad statement that the entire site is inaccessible.
Test the return path too
Opening an item is only half the journey. Check whether you can return to the list or continue to a neighboring entry without losing track of your position. If a panel or gallery opens, use the available controls to close it and observe where the journey resumes. Do not make assumptions about every browser or device from this one test. You are checking the experience in your current setup, with your own input method, and noting the specific steps that helped or obstructed the task.
Keep a practical result, not a certification
Record the outcome as a narrow finding: 'Category links and article navigation worked in this keyboard check; gallery controls were not checked.' If an essential action remains difficult, choose an alternative route or another resource for the current task. A quick test cannot establish compliance with every accessibility requirement. The takeaway is to inspect a complete small journey, including visible focus and the return path, and describe the result precisely. That gives you useful evidence about everyday browsing without overstating what one short session can prove.
Sources checked
Linked reference pages checked on 2026-09-09. Product details can change. No paid-membership test or sponsorship is implied.
W3C WAI: Designing for Web Accessibility ↗