Try this on your own website. Put your mouse aside, click once in the browser’s address bar and then press the Tab key repeatedly. Watch what happens. Can you see where you are on the page at every step? Can you reach the main menu, open its dropdowns and get to every link? Can you fill in and submit the contact form? Can you close the cookie banner? Keyboard navigation problems like these are common and very fixable.
On many WordPress sites I test, the answer to at least one of these is no. Focus disappears behind invisible elements. Dropdown menus only open on hover. A popup traps focus with no way out. A “Book now” button turns out to be a div that the keyboard can’t reach.
Keyboard accessibility matters for a wide range of people: those with motor disabilities who can’t use a mouse precisely, blind users with screen readers, which rely on keyboard navigation, people with temporary injuries, and power users who simply prefer the keyboard. It’s also a requirement of WCAG, the accessibility standard referenced by laws in many countries.
The good news is that keyboard issues are usually straightforward to find and fix.
How keyboard navigation works
Keyboard users mainly use:
- Tab to move forward through interactive elements
- Shift + Tab to move backwards
- Enter to activate links and buttons
- Space to activate buttons and toggle checkboxes
- Arrow keys to move within menus, radio groups, sliders and similar widgets
- Escape to close dialogs, menus and popups
The element currently selected is said to have focus. Browsers show focus with a visible outline, the focus indicator, unless a website’s CSS removes it.
Problem 1: invisible focus
The most common keyboard issue is a missing focus indicator. Many themes include CSS like this:
Designers sometimes remove the outline because it looks untidy when clicking with a mouse. The result is that keyboard users have no idea where they are on the page. It’s like using a mouse with an invisible cursor.
The modern solution is :focus-visible, which shows focus styles when the browser determines they’re needed, typically for keyboard navigation, but not for mouse clicks:
Make the indicator clearly visible against all backgrounds. WCAG 2.2 includes a criterion for focus appearance at the enhanced level, and in practice a thick outline with good contrast and a small offset works well. On dark sections, you may need a light outline instead.
In block themes, you can set focus styles globally in theme.json or in the theme’s stylesheet. Check buttons, links, form fields and navigation items.
Problem 2: no skip link
Every page usually starts with a header, logo and navigation menu. Keyboard users have to tab through every menu link on every page before reaching the content. On a site with a large menu, that’s dozens of key presses each time.
A skip link solves this. It’s the first focusable element on the page, usually hidden until focused, that jumps straight to the main content:
Most well-built themes include one, and block themes get one automatically when templates use a main element. Test it: press Tab once on a fresh page load. A “Skip to content” link should appear. Pressing Enter should move focus to the main content.
If it doesn’t appear, or appears but doesn’t work, check that the target ID exists on the main content area.
Problem 3: menus that only work on hover
Dropdown menus that open on mouse hover are a classic barrier. Keyboard users tab to the parent item, but the submenu never opens, so its links are unreachable. Sometimes the submenu links are focusable but invisible, so focus disappears into hidden items.
Accessible dropdowns:
- Open when the parent item or a toggle button receives a click or Enter key press
- Use a button element for toggles, with aria-expanded indicating open or closed state
- Close with Escape and return focus to the toggle
- Keep hidden submenu items out of the tab order until opened
The core Navigation block in WordPress handles this reasonably well, opening submenus on click when configured and supporting keyboard interaction. Many page builder and theme menus also have an “open on click” option. If your menu doesn’t work with a keyboard, check its settings or consider replacing it.
Problem 4: modals, popups and off-canvas menus
Dialogs like newsletter popups, cookie banners, video lightboxes and mobile off-canvas menus need careful focus management:
- When a modal opens, focus should move into it.
- While it’s open, Tab should cycle within the modal, not escape to the page behind it.
- Escape should close it.
- When it closes, focus should return to the element that opened it.
The native HTML dialog element, opened with showModal(), handles much of this automatically, including focus trapping and Escape to close. If you’re building custom modals, it’s a great place to start.
Third-party popup plugins vary widely. Test them with a keyboard. A popup that opens with no way for keyboard users to close it effectively blocks them from the site.
Problem 5: fake buttons and links
Developers sometimes create clickable elements with div or span and a JavaScript click handler:
It looks like a button, but the keyboard can’t reach it, and screen readers don’t announce it as a button. The fix is simple: use real elements. Links for navigation, buttons for actions.
Page builders occasionally produce fake buttons too, especially for custom widgets. Test them.
Problem 6: illogical tab order
Focus should move through the page in an order that matches the visual layout: top to bottom, left to right in left-to-right languages. Problems arise when:
- CSS reorders content visually, with flexbox order or grid placement, while the HTML order stays different
- Positive tabindex values, like tabindex=”3″, force a custom order
- Hidden elements remain focusable
Avoid positive tabindex values entirely. Keep source order matching visual order wherever possible. Make sure hidden content is genuinely hidden with display: none, the hidden attribute or inert, so it’s not focusable.
Problem 7: sliders, carousels and tabs
Interactive widgets need keyboard controls too:
- Carousels should have previous and next buttons and pause controls that are keyboard accessible. Auto-advancing carousels must be pausable.
- Tabs should be reachable and switchable, ideally following the ARIA tabs pattern with arrow key navigation.
- Accordions should use buttons for headings, with aria-expanded.
The native details and summary elements create accessible accordions with no JavaScript at all.
Problem 8: forms
Forms must be fully usable with a keyboard:
- Every field should be reachable with Tab
- Custom dropdowns, date pickers and checkboxes need keyboard support
- Error messages should be announced and focus should move to the first error after submission
- Submit buttons should be real buttons
Form plugins vary in accessibility. Test your actual forms, including validation errors.
A quick testing routine
You can test the basics on any page in five minutes:
- Load the page and press Tab. Does a skip link appear?
- Keep pressing Tab. Is focus always visible?
- Does the order make sense?
- Can you open and use every menu, including dropdowns, with the keyboard?
- Can you close any popups or banners with Escape or a focusable close button?
- Can you complete and submit every form?
- Can you operate sliders, tabs and accordions?
- Can you get back to the top using Shift + Tab without getting stuck?
Do this for the homepage, a typical content page, the contact page and, for stores, the full purchase journey from product page to checkout.
Building keyboard access into your process
Fixing keyboard issues after launch is always more work than preventing them. Add a short keyboard check to your development and review process: whenever a new component is built, tab through it before it’s marked as done. Include focus styles in the design system from the start, so designers specify them rather than developers inventing them later. When evaluating plugins that add front-end features, such as sliders, popups and forms, test them with the keyboard before committing. These small habits mean most keyboard issues never reach the live site.
Frequently asked questions
Is keyboard accessibility a legal requirement?
It’s part of WCAG, which accessibility laws in many places reference, including the European Accessibility Act and requirements in the US and India for certain organisations. Beyond legal duties, it’s simply good practice.
Will visible focus outlines spoil my design?
Not if they’re designed thoughtfully. Using :focus-visible means mouse users rarely see them, and a well-styled outline can match your brand.
Do accessibility overlay plugins fix keyboard issues?
Generally no. Overlays can’t reliably fix underlying problems like fake buttons, hover-only menus or broken focus management. Fix the site itself.
How do I test with a screen reader too?
Keyboard testing is the first step. Screen reader testing, with NVDA on Windows or VoiceOver on Mac, adds checks for labels, headings and announcements.




