Fake Menu Button
A button which opens a single column of links in flyout
Last updated
A button which opens a single column of links in flyout
Last updated
A button that expands a flyout containing a single column of links. Clicking any link will perform a URL navigation.
The fake menu can also contain buttons. This pattern is useful if your "dropdown" contains a mix of navigation items and items that execute JavaScript.
If you desire a dropdown menu that triggers a partial page reload instead of full page reload, please use the Menu Button pattern instead.
The distinction between menuitems and links is important! A menuitem is a command that executes JavaScript, whereas a link is a command that navigates to a url.
You can take a look at the fake menu pattern in action on our examples site.
You can get an idea of the required markup structure by viewing our bones site.
fake menu button: the pattern as a whole, comprised of the following sub-parts
host: a link, button or stealth button that *hosts* the overlay
overlay: the non-modal overlay that contains the fake menu items
fake menu: the list of fake menu items
fake menu item: a link or button
expanded/collapsed: the state of the overlay (i.e. visible or hidden)
hover-activated: the overlay expands on hover of host (implies host is a link)
click-activated: the overlay expands on click of host (implies host is a button)
For mouse users, a fake menu button can be expanded on hover of a link, but we do not recommend doing so. For keyboard users, a fake menu button must always be triggered via a button click. If using a link as the host, a stealth button must be inserted for keyboard users. A stealth button is a button that only appears on keyboard focus.
Avoid using a fake menu for important and/or frequently navigated links. Links in a hidden overlay will not show up in screen reader's list of links until the overlay is visible.
This section provides interaction guidelines for keyboard, screen reader, and pointing devices.
If host is a link, pressing TAB key while focus is on host must move keyboard focus to stealth button host.
ENTER or SPACEBAR on button or stealth button host must expand overlay. Keyboard focus can be moved to first fake menu item.
With focus on fake menu item, TAB key must move focus to next fake menu item.
With focus on fake menu item, ESC must collapse the overlay and must return focus to host.
With focus on last fake menu item, TAB key must move to next interactive element on page and should collapse overlay.
ENTER key must activate any fake menu item with focus (i.e. links).
Expanded state will be announced when focus is on button host or stealth button host.
Fake menu items must be identified as links or buttons (e.g. not menuitems).
Hovering over a link host must expand overlay.
Hovering out of a link host must collapse overlay.
Clicking button host must toggle state of overlay.
Unlike a menu button, which is always opened via a button for all devices, there are two ways in which a fake menu can be opened. The first, and simplest method, is also via a button. The second, and more complicated method, is via link element for pointing devices, combined with a hidden stealth button for keyboard.
We will begin with the simplest use case of a button as the host.
Notice placement of the host (the button) directly before the overlay element. This allows natural keyboard flow and reading order from the host into the overlay.
You may also notice that this structure is almost identical to the flyout. This is because the fake menu pattern is an extension of the flyout pattern. In essence it is just a button that opens an overlay of content; the content in this case being a list of links (buttons are permissible too).
The section is not yet available.
The section is not yet available.
This section gives an overview of our use of ARIA, within the specific context of this pattern.
This boolean attribute signifies the expanded state of the host button or stealth button (but is not used on a host link).
