A menu bar incorporates a strip of drop-down menus. It is typically located at the top of a primary window, below a window title bar.
Menu bars increase the vertical footprint of an application’s user interface, introduce a large number of disclosure points, and function as a fixed set of inflexible options. For these reasons,and are generally recommended over menu bars, along with other design patterns for exposing controls on demand, such as , , and .
At the same time, it can be appropriate for complex applications that already include a menu bar to retain it. Additionally, some platforms also incorporate space for a menu bar in their user environment, and a menu model can be desirable for cross-platform integration purposes.
The menubar is normally visible at all times and is always accessible from the keyboard, so make all the commands available in your application available on the menubar. (This guideline is unique to menu bars — other menus should not seek to reproduce functionality that is made available by other controls).
Treatas part of the menu bar — it is not necessary to reproduce items from the application menu in other menus.
Do not disable menu titles. Allow the user to explore the menu, even though there might be no available items on it at that time.
Menu titles on a menubar are single words with their first letter capitalized. Do not use spaces in menu titles, as this makes them easily-mistaken for two separate menu titles. Do not use compound words (such as WindowOptions) or hyphens (such as Window-Options) to circumvent this guideline.
Do not provide a mechanism for hiding the menubar, as this may be activated accidentally. Some users will not be able to figure out how to get the menu bar back in this case.
This work is licensed under a.
Got a comment? Spotted an error? Found the instructions unclear? Send feedback about this page.