The five-minute tab test
Put your mouse aside. Load your home page and press the Tab key repeatedly. Focus should move through links, buttons and form fields in a logical order, usually left to right and top to bottom. You should always be able to see where focus is. Shift plus Tab moves backward, Enter activates links and buttons, and Space toggles checkboxes.
Try to open your menu, use a dropdown, submit the contact form and close any pop-up using only the keyboard.
Visible focus outlines
The outline that appears around the focused item is essential. Some designs remove it for looks with a CSS rule, leaving keyboard users lost. If you see no marker, ask your designer to restore a clear focus style that has good contrast against the background. A thick, visible ring is better than a faint glow.
Skip links and logical structure
A skip link is a hidden first link that appears on focus and jumps past the menu to the main content. It saves keyboard users from tabbing through the same navigation on every page. Use proper headings in order, with one main heading per page, so assistive tools can offer a quick outline. Use real buttons and links, not clickable boxes made from generic elements.
Form labels and errors
Every field needs a visible label tied to it in the code, so a screen reader announces its purpose. Placeholder text inside the box is not a replacement, as it disappears while typing and often has low contrast. Mark required fields clearly and explain formats, such as phone numbers, before the person fills them in.
Error messages should say which field has a problem and how to fix it, and appear in text, not only as a red border. After a failed submit, move focus to the error summary.
Pop-ups, sliders and menus
Modal windows should trap focus inside while open, close with the Escape key, and return focus to the trigger when closed. Auto-rotating sliders need pause controls. Dropdown menus should open with the keyboard, not only on hover.
If your site uses a builder or plugin that fails these tests, report it to the vendor and consider simpler alternatives. Retest after every redesign, and keep a short log of what you fixed.
Who should do the fixing
Some problems can be solved in settings, such as turning on visible focus styles in a theme or switching to a form plugin with proper labels. Others need a developer to adjust code, for example fixing a menu that opens only on hover. Describe what you saw, such as the focus disappears after the third menu item, so the fix can be targeted.
Include accessibility in your requirements when you hire, and ask for a keyboard test before sign-off.
Also give the form a clear submit button with a descriptive name, and confirm the success message is announced or at least visible near where the person was working. A silent page reload leaves many users unsure whether anything happened.
Common questions
Do I need special software to test?
No. A keyboard is enough for a first check. Free screen reader programs allow deeper tests.
Is this only for people with disabilities?
Many people use keyboards for speed, and the same fixes help everyone.
Are placeholders ever enough as labels?
No. Use a real label and treat placeholder text as an optional hint.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.