Why this wireframe works | Dropdown hamburger menu
It opens as part of the header, so it is clear where it came from
A menu that appears somewhere else can leave people unsure which button opened it. It opens right below the header, at the same width as the header, so it reads as a continuation of the header.
The same button opens and closes it
With separate open and close buttons, people have to look for the way to close. While the menu is open, the menu button changes to an × and the word “Close”, and pressing the same spot closes it.
It does not dim or block the whole page behind it, so opening and closing feel light
A menu that covers the whole page changes the screen every time it opens. The page behind is only slightly dimmed and stays in view, and tapping outside the menu or pressing the Esc key also closes it.
On desktop, items sit in two columns so the menu stays short
The menu opens across the full width, so a single column leaves the right side empty. On desktop, the main pages sit in two columns, with the contact button and phone number on the right.
Common mistakes when building it
The menu overlaps the header and hides the button
If the menu is laid over the header, the button needed to close it disappears. Open the menu below the header and keep the menu button in view.
The button looks the same while the menu is open
If the button stays as three lines, nothing says that pressing it again closes the menu. While open, change it to an × and “Close”, and show the state with aria-expanded too.
The menu runs past the screen and the last items are out of reach
On mobile, a menu with many items runs off the bottom of the screen. Fit the menu’s height to the rest of the screen and let only the menu scroll.
People tap links on the page behind while the menu is open
Because the page behind stays visible, people trying to close the menu sometimes tap a link on it. A tap outside the menu should only close the menu, without following the link.
If you dim the page behind, that layer exists to close the menu on an outside tap, so links behind it can no longer be pressed. If you treat the menu as non-modal with a usable page behind, do not add a dimming layer, and test on a real device that closing on an outside tap does not clash with links behind it. In both cases, do not trap focus.
Frequently asked questions
Does a dropdown hamburger menu need to trap focus?
If it does not dim or block the whole page behind it and the page behind can still be used, it can be handled as a disclosure, a list that opens and closes, rather than a dialog. In that case, do not trap focus: put the menu right after the menu button in the code so Tab moves into it naturally.
Should a tap outside the menu close it?
Closing it is the norm. But following the link at the tapped spot easily becomes an unintended action, so it works well to have the first tap only close the menu.
Can I use this form on desktop too?
You can, but the main pages are hidden behind the button. To keep them always visible, consider listing them in the header on desktop and using the dropdown hamburger menu only on mobile.













