http://tc.eserver.org/dir/Articles/User-Interface/Help A listing of the most recently indexed works about Articles and User Interface and Help in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Articles/User-Interface/Help http://tc.eserver.org/34097.html http://tc.eserver.org/34097.html Motivation is an important factor in any kind of online interaction or transaction. People need a little encouragement when they’re not really convinced they should take any action or are uncertain about what action to take next. As users perform tasks online, they need to understand what’s happening and expect you to help them move forward. This article discusses the responsibility of a user interface to provide recommendations along a user’s path of interaction. http://tc.eserver.org/33468.html http://tc.eserver.org/33468.html Frequently, error messages are totally uninformative -- or, worse, just plain wrong. Here, we look at how meaningful error messages can make it easier for users to correct problems without having to rely on technical support, and how poorly chosen messages can turn users into ex-users. http://tc.eserver.org/28661.html http://tc.eserver.org/28661.html In a utopian world, a product would be so perfect it would not need any user assistance at all. But in reality, products aren't perfect, and users need assistance through different stages of their use. User assistance (UA)--in the form of manuals or online Help--guides users in their tasks, suggests better ways of getting their work done, and provides directions for troubleshooting their problems. http://tc.eserver.org/28658.html http://tc.eserver.org/28658.html User assistance occurs within an action context--the user doing something with an application--and should appear in close proximity to the focus of that action--that is, the application it supports. The optimal placement of user assistance, space permitting, is in the user interface itself. We typically call that kind of user assistance instructional text. But when placing user assistance within an application as instructional text, we must modify conventional principles of good information design to accommodate certain forces within an interactive user interface. This column, User Assistance, talks about how the rules for effective instruction change when creating instructional text for display within the context of a user interface. http://tc.eserver.org/20285.html http://tc.eserver.org/20285.html As documentation is more and more built directly into the interface, and as technical communicators move into interface design and usability, it is important to have a theoretical framework within which to make decisions about what kind of information will be conveyed at any moment. We can build on basic principles of cognitive psychology to help us make these decisions. We start from a question: Why should users be aware of the difference between interface and documentation when all they want is to get something done? http://tc.eserver.org/19504.html http://tc.eserver.org/19504.html Context-sensitive Help is assistance that is appropriate to where the user is in the software application, and what they are trying to do. Carol Johnston's article describes what programmers and technical authors need to know about Context-sensitive Help.