![ufocus guidance for the puzzled ufocus guidance for the puzzled](https://1.bp.blogspot.com/-AttrebWfX2s/YSfIe_U67PI/AAAAAAAARno/9Qnka15rGygrMFVnEVpnMTwdoX4div2eQCLcBGAsYHQ/s320/image-crop.jpg)
Use an error message style that first gives the cause of the problem and the name of the specific object involved, and then tells briefly how to fix the problem. Use only the present tense for UI text, unless an occasional odd situation demands another tense. Use only one space between sentences, not two. Start the instructional text with a present tense, active verb, for example, "Enter your locale, region, and language". Use instructional text on forms if necessary. Use singular objects unless the task can apply to multiple instances of an entity at the same time. Use the verb-object construction for things that are tasks, for example the Enter customer payments form or the Service > Create service orders menu option in the Projects form. Use correct punctuation (period or question mark) for messages. Do not use punctuation after labels or after short Help text that is displayed in the status bar.
![ufocus guidance for the puzzled ufocus guidance for the puzzled](https://i.ytimg.com/vi/O_zh2_AvWsE/maxresdefault.jpg)
For example, use "ID," and not "Id." Use sentence case for everything else. Approved abbreviations, acronyms, and intialisms should use all uppercase letters. When you create UI text, the top things you should do are as follows: Although appropriate for some audiences, an end-user should never have to decipher technical jargon. A user should never be given multiple wording for the same UI element.Īvoid technical jargon. A user should never have to read more than absolutely necessary. A user should never be puzzled by any UI text. When you create UI text, the following should be your guiding principles: This topic includes the following sections:
![ufocus guidance for the puzzled ufocus guidance for the puzzled](https://johnrausch.com/PuzzleWorld/art/art02/fig11_2.jpg)
Therefore, this topic documents only general UI text guidelines that are not covered in those topics. The specific UI text guidelines for Microsoft Dynamics AX 2012 list pages, forms, reports, and so on, are included in the "Labels and text" sections of the topics under the Client, Enterprise Portal, and Reporting User Experience Guidelines. UI text also includes tooltip text that appears when the user moves the pointer over a button or a menu, short Help text that is displayed in the status bar, and the messages that the user may receive, such as Infologs. UI text includes titles of list pages, forms, and reports, and the labels of controls that they may contain, such as fields and buttons. User interface (UI) text is text that appears on the user interface. Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012