The menu is where most sites lock people out

Hover is not enough

A dropdown that only appears when a pointer rests on it does not exist for anybody using a keyboard. The parent gets focus and nothing happens.

Everything under that parent is then unreachable, which on most sites is half the site.

Menus have to respond to focus as well as hover, and they need to close again with the escape key.

The reach of this fault is what makes it serious. A hover-only dropdown hides every page beneath it, which on most sites is the majority of the site.

The hamburger button

A small icon with three lines is understood visually and says nothing aloud unless somebody labeled it.

It needs a text label, and it needs to announce whether the menu is currently open or closed. Both are small additions and both are commonly missing.

It also needs to be a real button, so that space and enter operate it without extra code.

Depth is the enemy

Three levels of nested dropdown is difficult with a mouse, awkward on a phone and genuinely painful by keyboard.

Most sites with deep menus are using navigation to compensate for a structure problem. The fix is usually fewer top level sections with landing pages beneath.

If a menu needs a diagram to explain, visitors are not holding it in their heads either.

A useful test is whether you can name every top level section from memory. If you cannot, neither can a visitor who arrived a minute ago.

A useful test: name every top level section from memory. If you cannot, a visitor who arrived a minute ago certainly cannot.

Where you are

Mark the current page in the menu, visually and in the markup, so a reader arriving mid site knows where they stand.

Colour alone is not enough, since some readers cannot separate the shades. Add weight, an underline or a marker.

This is one of the cheapest orientation improvements available and it is skipped on most small sites.

Consistency across pages

The same menu, in the same order, in the same place on every page. Reordering by section forces everyone to relearn it.

Consistency is a named expectation in the accessibility guidelines and it is simply good design.

The same applies to the footer, which is where many readers look for contact details and legal pages.

Consistent navigation is a named expectation in the accessibility guidelines and it is simply good design, which is the overlap described in where accessibility and SEO agree.

Touch and small screens

Targets need to be large enough to hit reliably and far enough apart that a shaking hand does not choose the wrong one.

A menu that opens over the content needs an obvious way to close it, reachable without precision.

Test with one thumb, standing up, which is how most people actually use a phone.

Also check what happens when the menu is open and the page behind it scrolls. Locking the background is usually the right behavior.

• Targets large enough to hit with a thumb
• Enough space between them that a near miss does not choose the wrong item
• An obvious way to close an open menu
• The page behind locked while the menu is open
• The current page marked, not only colored
• Nothing that depends on hovering, which does not exist on touch

What the builder ships

Navigation here is built from real links and real buttons, with the current page marked and a skip link ahead of it.

Every page passes a check that runs before anything publishes, validated against Google Search Essentials and modern web standards.

A machine can confirm the controls are reachable. Whether your menu makes sense is a structure question, and the in-app assistant will tell you when a section has grown too large to sit under one heading.

Nothing here is legal advice. A menu is simply the one component where a single fault reaches every page you have.

Test yours one-handed, standing up, on a phone. That is how most people actually use a menu, and it finds spacing problems a desktop review never will.