Technical writing UI Design
back to Technical Writing Level 2
Choosing the right colors to use is a very important aspect of user interface design. Choosing a color palette that makes it easier for the user to distinguish content is essential.
Avoid using disturbing colors and try to keep the general appearance pleasing to the eye. Certain colors are extremely difficult for color blind users to read, e.g. shades of green and red.
Designers of user interfaces should try to limit the number of colors to three or four. Contrasting colors should be chosen carefully and there should be a distinct difference between the color of the text and the color of the associated background.
Affordances are visual clues in the design that allow users to guess the function of an object. For example, a teapot is traditionally designed with a handle on one side and a spout on the opposite side. This should indicate to an observer which part of the teapot is safe to hold.
In User Interface (UI) design, such clues could take the form of embedded navigation buttons.
Usability refers to the ease with which users can interact.
As with any form of design the key is KIS - Keep It Simple.
Continuing from the teapot analogy in the 'affordances’ section, it should be clear to users how they can interact with products, services, and texts, in much the same way that a teapot is designed with a lid that users know intuitively to use to open the pot in order to insert the tea bag and water.
The World Wide Web Consortium (W3C) is dedicated to ensuring that the technology of the Web supports accessibility. It sees access to the Web as a basic human right (W3C 2009). When developing a website, there are many ways in which the Web can be made accessible. An instructional designer needs to be aware of people with disabilities and the various assisted technologies that there are.
The Web Content Accessibility Guidelines (WCAG 2.0) provide a framework which an instructional designer can implement to ensure that the courses they create are accessible to as many users as possible. These guidelines are of particular importance to those with disabilities, but also serve to make content more usable and accessible to all.
These are available at 
Technical writers should be aware of GUI elements such as dialog box, chevrons, window, screen, check-box, radio button, drop-down list, field, text box and so on. This will help them to document instructions correctly and easily. Technical writers with basic knowledge of GUI elements can contribute by assisting developers and web developers in labelling their application's field names correctly.
I just don't know where to start folks, so please add some content to give me a kick start.
TWFred 14:25, 14 February 2008 (UTC)
- someone spare timer here and write about tabbing and skipping on UI like forms (The preceding unsigned comment was added by 22.214.171.124 (talk • contribs) 17:16, 19 May 2008)
- Question - should this be about the role of Technical Writers in UI design, or about the UI of user documentation? (The preceding unsigned comment was added by Spiderling (talk • contribs) 10:56, 7 July 2008)
- Question: Is this topic about documenting UI or role of technical writers in UI design? User: Bhavna, 12:14, 11 July 2008
back to Technical Writing Level 2
Question - Maybe something about Mindmapping-Software, Audio- and Video-Pod-Production for mobile players, the moodle-learning-platform,...???