Rhonda Bracey's presentation from the WritersUA 2008 Conference (Portland, OR) **************** "Can you just look over these new screens for us? Oh, and can you check the error messages too? It won't take long!" If you've been asked to review a web or standalone application's user interface but don't know what to look for other than checking the text, then this session is for you. As technical communicators, we are often in a position to identify usability problems related to the logical flow, layout, and structure of the interface; inconsistencies in the design; non-compliance with standards and guidelines; ambiguous wording on labels, error messages, dialogs, and onscreen user assistance; performance issues; functional errors; and the like. Rhonda shares practical checklists of things to look for when reviewing an interface, as well as various tools that can assist you. — YOU WILL LEARN — * What to look for when checking an application's user interface, including overall design, textual and visual elements, user actions and interactions, navigational links, and the '-ilities': accessibility, readability, usability. * About some tools that can help automate parts of the review process. ************** Other supporting material available from here: http://www.cybertext.com.au/10353.htm

1. Techniques for Reviewing a User Interface Rhonda Bracey [email_address] http://www.cybertext.com.au

2. Communication What is communication in this context? What's the cost of NOT reviewing an interface?

5. Dollar cost The further along the development process, the greater the cost of making even a simple change. Recommendation: Get involved EARLY in the development cycle. $ Spec $$ Design $$$ Code $$$$ Test $$$$$ Beta/internal release $$$$$$ After release

6. Reputation cost From Australian Personal Computer , Nov 2007

7. Design Elements Does it 'look good'? (Aesthetics) Does it work? (Function) Is there anything that makes you hesitate?

8. Quotable quote… Design is NOT about decoration. It's about communication and problem solving. --Garrett Dimon, "Improving Interface Design" (Web Visions 2007) http://garrettdimon.com/pages/ improving_interface_design

9. Quotable quote… Sometimes there is a huge disconnect between the people who make a product and the people who use it. --Barbara Whitaker, NY Times, 8 July 2007 http://www.nytimes.com/2007/07/08/ business/yourmoney/08starts.html

11. Text Elements What to check? Check for what?

15. Weak error messages

16. Better error message

30. Examples Familiar icons and placement? And if you change the CSS…

41. Example: Callouts

42. Example: Document (1)

43. Example: Document (2)

44. Example: Checklist

48. Handy Tools and Resources

57. Just for fun… From "Error Pages": http://www.smashingmagazine.com