Microsoft Error Message Guidelines
Contents |
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET error messages examples - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics error messages best practices Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore
A Error Message
Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize
Error Message Examples Text
Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI list of error messages design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Design Guidelines Messages Messages Error Messages Error Messages Error Messages Error Messages Warning Messages Confirmations Notifications TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Error Messages An error message alerts users of a problem that has already occurred. By contrast, a warning message alerts users of a condition that might cause a problem in the future. Error messages can be presented using modal dialog boxes, in-place messages, notifications, or balloons. A typical modal error message. Effective error messages inform users that a problem occurred, explain why it happened, and provide a solution so users can fix the problem. Users should either perform an action or change their behavior as the result of an error message. Well-written, helpful error messages are crucial to a quality user experience. Poorly written error messages result in low product satisfaction, and are a leading cause of avoidable technical support costs. Unnecessary error messages break users' flow. Note: Guidelines related to dialog boxes, warning mess
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community
Error Message Text Prank
Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev friendly error messages examples centers Samples Retired content We’re sorry. The content you requested has been removed. You’ll be auto error message design redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office development https://msdn.microsoft.com/en-us/library/windows/desktop/dn742471(v=vs.85).aspx Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Error and Informational Message Guidelines https://msdn.microsoft.com/en-us/library/bb158646.aspx Windows Mobile 6.5 4/19/2010 Follow these guidelines when you write error messages and informational text: Identify the problem, indicate the cause if helpful, and provide a solution if possible. Write phrases instead of complete sentences to conserve space. For example, write "Save using a different name" instead of "Save this document using a different file name." Use title caps in the title bar of the message box and sentence caps in the message body text. Title caps rules specify that all words are capitalized with the exception of articles, coordinating conjunctions (and, but, for, not, or, so, and yet), and prepositions containing four or fewer letters. Sentence caps rules specify that only the first word and any proper nouns are capitalized. Bold command names instead of using quotation marks. When there may be a consequence of a user's action, preface the error message with the word "Warning." For example, write "Warning: If you synchronize now, duplicate it
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, https://msdn.microsoft.com/en-us/library/windows/desktop/bb226825(v=vs.85).aspx C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities http://stackoverflow.com/questions/3354867/does-anyone-use-a-style-guide-for-error-messages Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started error message UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started error messages examples Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Welcome to the MMC 3.0 Guidelines Common UI Controls and Text Guidelines Messages Messages Messages: UI Text Guidelines Messages: UI Text Guidelines Messages: UI Text Guidelines Messages: Design Guidelines Messages: UI Text Guidelines TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Messages: UI Text Guidelines Content and Presentation Terminology Capitalization and Punctuation Standard Message Phrasing Content and Presentation Use messages to report those conditions that require special consideration or affect the user’s ability to complete the action. Avoid combining more than two or three issues in a single message. For example, if a file cannot be opened for several reasons, provide a separate message for each reason. Put the program name in the title bar of the message box to identify the source of the message. Do not use the words warning, caution, or error in a message-box title bar. State the problem, its probable cause (if known), and what the user can do about it, no matter how obvious the solution. Try to include enough information so that an adva
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Does anyone use a style guide for error messages? up vote 5 down vote favorite 5 I've noticed that error messages tend to be written in a handful of common styles. Either in full-form, casual-friendly sentences, or in shortened passive ones that don't always form a full sentence. The latter of the two seems to be the more common - though maybe not as common as the haphazard mixing of styles that I see in a lot of applications. Does anyone include error messages in their style guide? I'm more curious about opinions on the consistent grammatical construction of these things than about the content of them, which has already been discussed. user-interface modal-dialog exception share|improve this question edited Jul 28 '10 at 16:10 skaffman 278k63619656 asked Jul 28 '10 at 16:04 Wayne Renaud 6927 If they don't they should. –Lucas B Jul 28 '10 at 16:05 add a comment| 1 Answer 1 active oldest votes up vote 8 down vote accepted Both the iPhone Human Interface Guidelines and the Apple Human Interface Guidelines contain sections on alerts. Also, the Windows User Experience Interaction Guidelines have information for a few different types of dialogs, including error messages. (iPhone) As you compose the required alert title: Keep the title short enough to display on a single line, if possible. A long alert title is difficult for people to read quickly, and it might get truncated or force the alert message to scroll. Avoid single-word titles that don’t provide any useful information, such as “