Difference between revisions of "Projects/Usability/HIG/Wording"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Guidelines: Updated to integrate wording guidelines from VDG typography guideline (moved here).)
Line 6: Line 6:
 
== Guidelines ==
 
== Guidelines ==
 
* Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.  
 
* Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.  
 +
* Put the most important thing first.
 +
* Short words, active verbs and common nouns.
 
* Avoid [[Projects/Usability/HIG/Contractions|contractions]] such as ''Don't'' and ''Won't'' etc.
 
* Avoid [[Projects/Usability/HIG/Contractions|contractions]] such as ''Don't'' and ''Won't'' etc.
 
* Avoid abbreviations, acronyms, and tech-babble.
 
* Avoid abbreviations, acronyms, and tech-babble.
* Use a tone that’s informal and friendly, but not too informal.
+
* Use a tone that’s informal and friendly, but not too informal; avoid popular, but transient, words and phrases.
* Keep information short and consistent; avoid redundancy or unnecessary words.  
+
* Keep information short and consistent; avoid redundancy or unnecessary words. e.g. Do not repeat the dialog title in the dialog text.
 
* Don't abuse [[Projects/Usability/HIG/Capitalization|capitalization]] because it draws people’s attention.
 
* Don't abuse [[Projects/Usability/HIG/Capitalization|capitalization]] because it draws people’s attention.
* In respect to chronological information consider that your app is potentially used for decades; don't use fix dates like ''this year''.
+
* For date and time information, consider that your app may potentially be used for several years; do not use immutable date references like ''this year'' unless it is algorithmically determined.
* Follow system-wide conventions for basic functions to keep wording consistent.
+
* Follow system-wide wording conventions for basic functions to keep wording consistent.
  
[[Category:Usability]][[Category: Presentation]][[Category:Text]]
+
[[Category:Usability]][[Category: Presentation]]

Revision as of 20:29, 28 March 2014


Purpose

Every word displayed in an application is part of a conversation with users. This conversation is an opportunity to provide clarity and to help people feel comfortable in the system.

Guidelines

  • Use a terminology that is familiar and easy to understand for the target audience (i.e. Persona) of your application.
  • Put the most important thing first.
  • Short words, active verbs and common nouns.
  • Avoid contractions such as Don't and Won't etc.
  • Avoid abbreviations, acronyms, and tech-babble.
  • Use a tone that’s informal and friendly, but not too informal; avoid popular, but transient, words and phrases.
  • Keep information short and consistent; avoid redundancy or unnecessary words. e.g. Do not repeat the dialog title in the dialog text.
  • Don't abuse capitalization because it draws people’s attention.
  • For date and time information, consider that your app may potentially be used for several years; do not use immutable date references like this year unless it is algorithmically determined.
  • Follow system-wide wording conventions for basic functions to keep wording consistent.

Content is available under Creative Commons License SA 4.0 unless otherwise noted.