Why hover-triggered navigation breaks down
Hover submenus are an old CSS trick: a rule like li:hover > ul reveals a nested list, and :focus-within later made it possible for keyboard and mouse to share the same reveal behavior.
<ul class="my-menu">
<li>
<a href="page-a.html">Page A</a>
<ul>
<li><a href="page-b.html">Page B</a></li>
<li><a href="page-c.html">Page C</a></li>
<li><a href="page-d.html">Page D</a></li>
</ul>
</li>
<!-- etc... -->
</ul>
/* Position submenus relative to parent list item */
.my-menu li {
position: relative;
}
.my-menu ul {
/* Hide my submenus by default */
display: none;
/* Position submenus, when open */
position: absolute;
left: 0;
top: 100%;
}
/* Look, Ma! No onclick handler! */
.my-menu li:hover > ul {
display: block;
}
/* No IE11 support */
.my-menu li:focus-within > ul {
display: block;
}
Hover interaction is nonetheless weaker than a click on usability, accessibility and content strategy grounds. The problem is ambiguity: if a menu with chevrons on every item except "Home" opens on hover, visitors have no reliable way to predict how the parent item behaves. Hover menus commonly take one of four forms:
- The parent links to its own page, and every submenu item links to a separate page.
- The parent has
href="#"(or nohrefat all), so only the submenu links are functional. - The parent and the first submenu item point to the same page — and when their link text differs, that fails a WCAG 2.1 Level AA criterion.
- The parent leads to a page with no real purpose, holding only filler or a copy of the submenu links.


The uncertainty produces three reasonable questions from visitors: can the parent items be clicked, will the parent duplicate the first submenu link, and is a unique parent page worth the visit? Because there is no standard hover implementation, Jakob's law — users expect your site to behave like the sites they already know — cannot be satisfied.
The split-button variant doesn't help
A rarer pattern separates the two roles: the parent stays a link, and a distinct dropdown icon toggles the submenu. The Twenty Fifteen default WordPress theme does this. It is uncommon enough that visitors often miss the top-level link entirely, and research indicates people do not perceive a label and an adjacent icon as separately clickable.


Click-triggered submenus as the default
Make the parent a button that shows and hides its submenu. Links then live only inside submenus, apart from top-level items that have none, such as "Home". Interaction is unambiguous, and it matches expectations set elsewhere:
- On touch devices, hovering does not exist.
- Application menus (File, Edit and so on) do not open on hover.
- For keyboard and switch-control users, pressing
ENTERresembles a click, whereas:focusis not an equivalent of:hover.
Existing systems back this up. The U.S. Web Design System advises against hover expansion:
Avoid using hover to expand dropdown lists. Hover is difficult for some users and won't work on touch screens. Dropdowns should expand on click or with keyboard navigation.
Bootstrap's reasoning is built on user intent:
What it really boils down to is user intent. The purpose of a hover state is to indicate something is clickable (underlined text)… The purpose of a click is to actually do something, to take an explicit action. Opening a dropdown is an explicit action and should only happen on click.
The caret in a dropdown link is the equivalent of underlining a link: it provides some affordance for what will happen when you click this element. Don't mistake that for providing enough information to pop the dropdown on hover though.
Worth remembering from the UK.gov design system: you may not need submenus at all. Its menus are plain lists of links, supplemented by on-page link grids and accordions. CSS-Tricks likewise has no submenus.
Visitors raised on hover menus adapt quickly to click menus, even if some say they prefer hover when asked.
Side effects worth having
- Content decides the page structure. A menu is no longer forced to mirror a chain of parent and child links. Where an overview genuinely helps, add an item such as "Services Overview" or "All Services" at the top of the submenu.
- Open is open until closed. Hover menus vanish on a stray cursor movement or when someone moves toward a submenu link, especially in fly-out layouts. Persistence makes the interface feel solid.
- Megamenus need that persistence most, since their contents take time to read.
- One behavior for mobile and desktop. Whether the menu sits behind a hamburger or is visible, the interaction is identical; only CSS needs to change for responsiveness.
Implementing an accessible click menu
There is no single standard for this pattern. Useful references:
- "Link + Disclosure Widget Navigation" by Adrian Roselli
- "Header demo" by US Web Design Service
- "Menu Design: Checklist of 15 UX Guidelines to Help Users" by Nielsen Norman Group
- "Example Disclosure Navigation Menu" in ARIA Authoring Practices
Key implementation points:
- The toggle is a
<button>, since it navigates nowhere. aria-expandedgoes on that<button>to expose the open and closed state.- Hidden submenus use
display: noneorvisibility: hidden, keeping them out of the tab order. - Add
aria-controlsanyway, despite its poor support. - Skip
role="menu", the ARIA menu pattern andaria-haspopup; they resemble what you want but are not meant for navigation. - Close an open submenu when another one opens, when the user clicks outside it, or when
ESCis pressed with focus inside it — the last is a nicety rather than an expectation.
JavaScript is required, so build for graceful degradation. Start with the CSS-only pattern using li:hover > ul and li:focus-within > ul, then use JavaScript to create the <button> elements, apply the aria attributes and attach the handlers. The menu still largely works without JavaScript and fits link-only menus produced by WordPress.
A reference implementation lives in the clicky-menus script, though other options are likely stronger. Whatever you ship, test it with real users.



