Who needs keyboard navigation?

People who cannot use a mouse reliably, many screen reader users, and anyone with temporary hand or motor limitations. It is a core WCAG requirement, not a niche edge case.

What is a visible focus indicator?

A clear visual outline or highlight on the element that currently has keyboard focus. Without it, keyboard users lose track of where they are on the page.

Does a widget fix keyboard problems?

No. Broken tab order, missing focus styles, and traps in menus or modals must be fixed in the site code or theme.

Keyboard navigation on websites, why it matters and how to check it

If your site only works with a mouse, a large group of visitors cannot complete basic tasks. Keyboard navigation is one of the first checks an accessibility review runs, and one of the most common failures on small business sites.

Why keyboard access is mandatory

WCAG 2.0 level AA, and therefore Israeli Standard 5568, requires that functionality is operable through a keyboard interface. That covers menus, forms, buttons, carousels, dialogs, and checkout steps.

A five-minute smoke test

Click in the address bar, then press Tab repeatedly.
Confirm you can reach the main menu, search, forms, and primary buttons.
Confirm a clear focus ring moves with you.
Open a menu or modal and check that Escape closes it and focus returns sensibly.
Make sure focus is never trapped with no way out.

Common breaks

Custom buttons built as <div> without keyboard handlers
Dropdowns that open only on hover
Carousels with no keyboard controls
CSS that removes outline globally
Cookie banners and chat widgets that steal focus forever

What to do next

Start with the pages that convert: homepage, contact, booking, and checkout. Fix focus styles and real buttons or links first. Then re-run the keyboard path after theme or plugin updates.