In the incorrect example, the red icon unintentionally suggests an error, creating confusion. Use swaths of pure red, yellow, and green only to communicate status information. Prefer icons with unique outlines over square or rectangular shaped icons. Present status information in the following order: current window status progress and contextual information.Ĭhoose easily recognizable status icon designs.Remove non-modal status that doesn't apply.Modal status includes keyboard and document states. Disable modal status that doesn't apply.Don't use the status bar to explain menu bar items.Hide the status bar by default if most users won't need it. Consider providing a View Status Bar command if only some users will need the status bar information.In this example, Microsoft Paint shows the selection size in pixels. In this example, the status bar includes a progress bar to show the Web page loading into a Internet Explorer window.Ĭontextual information Show contextual information about what the user is currently doing. Progress Show the progress of background tasks, either with a determinate progress bar or an animation. In this example, the status bar displays the path to the document. Status bars have several usage patterns: UsageĬurrent window status Show the source of what is being displayed along with any view modes Make sure that the status bar information is useful and relevant but not crucial. If users must see it, don't put it in a status bar. Users should never have to know what is in the status bar. Not using status bars for crucial information.If not, don't provide a status bar at all. Making sure that the status information is useful and relevant.The solution to this problem isn't to demand the user's attention by using garish icons, animation, or flashing, but to design for this limitation. So easy, in fact, that many users don't notice status bars at all. However, status bars are easy to overlook. Status bars are a great way to provide status information without interrupting users or breaking their flow. Is the program intended primarily for novice users? Inexperienced users are generally unaware of status bars, so reconsider the use of status bars in this case. Is the status critical? Is immediate action required? If so, display the information in a form that demands attention and cannot be easily ignored, such as a dialog box or within the primary window itself.Ī red address bar in Windows Internet Explorer. Is the status useful and relevant? That is, are users likely to change their behavior as a result of this information? If not, either don't display the status, or put it in a log file. Status bars must not be used as a secondary menu bar or toolbar.ĭoes the information explain how to use the selected control? If so, display the information next to the associated control using a supplemental explanation or instruction label instead. Is the information primarily status? If not, don't use a status bar. Dialog boxes, wizards, control panels, and property sheets shouldn't have status bars. Is the window a primary window? If not, don't use a status bar. Is the status relevant when users are actively using other programs? If so, use a notification area icons.ĭoes the status item need to display notifications? If so, you must use a notification area icon. Guidelines related to the notification area are presented in a separate article.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |