The Windows desktop

The Windows desktop has the following program access points:

• Work area. The onscreen area where users can perform their work, as well as store programs, documents, and their shortcuts. While technically the desktop includes the taskbar, in most contexts it refers just to the work area.
• Start button. The access point for all programs and special Windows places (Documents, Pictures, Music, Games, Computer, Control Panel), with “most recently used” lists for quick access to recently used programs and documents.
• Quick Launch. A direct access point for programs selected by the user. Quick Launch was removed from Windows 7.
• Taskbar. The access point for running programs that have desktop presence. While technically the taskbar spans the entire bar from the Start button to the notification area, in most contexts taskbar refers to the area in between, containing the taskbar buttons. This area is sometimes referred to as the taskband.
• Deskbands. Minimized functional, long-running programs, such as the Language Bar. Programs that minimize to deskbands don’t display taskbar buttons when minimized. Deskbands are not recommended for Windows 7.
• Notification area. A short-term source for notifications and status, as well as an access point for system- and program-related features that have no presence on the desktop.

Context menus

• Display the context menu near its associated icon, but away from the taskbar.
• The context menu may include the following items, as appropriate, in the listed order (exact text is in quotes):
  

  Primary commands
  Open (default, list first, in bold)
  Run
  Secondary commands
  <separator>
  Suspend/resume enable/disable command (check mark)
  “Minimized to notification area” (check mark)
  Opt in to notifications (check mark)
  “Display icon in notification area” (check mark)
  <separator>
  “Options”
   “Exit”

• Remove rather than disable any context menu items that don’t apply.
• For Open, Run, and Suspend/Resume commands, be specific about what is being opened, run, suspended, and resumed.

  In this example, Windows Defender has specific Open and Run commands.

• Use Suspend/Resume running background tasks, Enable/Disable for everything else.
• Use check marks to indicate state. List and enable all states and place the check mark next to the current state. Don’t disable options or change option labels to indicate the current state.Correct:
  

  Incorrect:
  

  In the incorrect example, Windows Defender should use a check mark to indicate the current state.

• All background tasks must have a Suspend/Resume command. Choosing the command should temporarily suspend the task. Users may want to temporarily suspend background tasks to increase system performance or reduce power consumption. Suspended background tasks are restarted when resumed by the user or when Windows is restarted.
• Allow users to opt into or out of different notification types if your program has notifications that some users might not want to see. The FYI notification pattern requires users to opt in, so these notifications must be disabled by default.

  In this example, Outlook allows users to choose the notifications they receive from the icon.

• Clearing the “Display icon in notification area” option removes the icon from the notification area, but doesn’t affect the underlying program, feature, or process. Users can redisplay the icon from the program’s Options dialog box. Don’t automatically re-display the icon when Windows is restarted.
• The Exit command quits the program for the current Windows session and removes the icon. Don’t have an Exit command if program can’t be shut down. The program is restarted when Windows is restarted. Users can permanently quit the program from the Options dialog box.
• Don’t have an About command. Such information should be communicated by the icon, its infotip, and the context menu. If users want more information, they can view the primary UI.
  • Exception: You may provide an About command if the icon is for a program that doesn’t have desktop presence.

For general context menu guidelines and examples, see Menus.

Rich tooltips

• Use rich tooltips only to make the information easier to understand. Don’t use rich tooltips just to decorate the feature. If you can’t use richness to make the information easier to understand, use a plain tooltip instead.Incorrect:
  

  Correct:
  

  In the incorrect example, the calendar icon doesn’t make the date easier to understand.

• Use a concise presentation. Use concise text and a concise layout with a 32×32 pixel icon. Spacious tooltips risk being distracting, especially when displayed unintentionally.
• Don’t put controls or elements that appear interactive in a rich tooltip. Tooltips aren’t interactive and therefore shouldn’t appear interactive. Don’t use blue or underlined text.Correct:
  

  Incorrect:
  

  In the incorrect example, the current power plan appears to be a link, but it is impossible to click.

Notification area flyouts

• When appropriate, present notification area flyouts with three sections:
  • Summary. Display the same information that is displayed in the icon’s tooltip or infotip, possibly with more detail. For consistency, use the same text and icons, and generally the same layout (if using a rich tooltip). Unlike the infotips, this information is accessible when using touch.
  • Common tasks. Present the most commonly performed tasks directly in the flyout.
  • Related links. Provide at most one of each type of the following optional links:
    • A link to the most frequently performed task in Control Panel. Provide if there is a frequently performed task that can’t be presented in the common tasks section.
    • A link to the related Control Panel item. This Control Panel item should allow users to perform any tasks that can’t be performed in the common tasks section.
    • A link to a specific, relevant Help topic. Follow the standard Help link guidelines.

  

  This example shows a notification area flyout using the recommended presentation.