A store that does not work without a mouse is inaccessible. Learn how to test keyboard navigation and fix common problems.
Scan Your Store NowNot everyone uses a mouse. People who use screen readers, voice control software, or who have motor disabilities rely entirely on the keyboard. If your store is not fully navigable by keyboard, you are excluding these customers.
Keyboard navigation is also required by WCAG 2.1 AA, the accessibility standard referenced in the ADA and many compliance frameworks.
Literally put the mouse away. You will use only the keyboard for this test.
Starting from the top of your homepage, press Tab repeatedly. Ask:
When focus reaches a button or link:
Problem: When you Tab through the page, you cannot see where focus is. The focus outline is removed or invisible.
Fix: Use CSS to show focus. Do NOT remove the default outline.
:focus { outline: 2px solid #10B981; outline-offset: 2px; }
Problem: You Tab into a dialog or modal and cannot Tab out. Focus is stuck.
Fix: Ensure Escape closes the modal and returns focus to the trigger. Ensure Tab cycles through the modal's interactive elements only.
Problem: A clickable area is a <div>, not a <button> or <a>. It works with a mouse but is not reachable by keyboard.
Fix: Use semantic HTML. Replace <div onclick> with <button> or <a>. If you must use a div, add role="button" tabindex="0" onkeydown="if(event.key==='Enter') ..."
Problem: Dropdowns appear only on mouse hover. Keyboard users cannot access them.
Fix: Make menus keyboard-accessible. Open on focus, close on blur or Escape. Show a focus indicator.
Scan Record automatically detects keyboard navigation issues and generates a dated audit record listing:
Full accessibility checklist →
Alt text guide →
Form label compliance →