|
|||||||
|
|||||||
| Guidelines | |||||||
| Web design for helping novices builds upon general principles of good web design. The following guidelines are producted by selecting and combining guidelines from web sites and references. KNOWLEDGE 1. Use consistent presentation. Consistency helps users determine the relationships between items in the content. This ability to understand the structure helps users navigate, orient themselves, and thus understand. 2. Provide site map and users position (path). o Novice may get lost in the mass of available information. An interactive concept map is a good solution to this problem. 3. Define key terms, abbreviations, acronyms, and specialized language. o Defining key terms and specialized language will help people who are not familiar with the topic you are presenting. Providing the expansion of abbreviations and acronyms not only helps people who are not familiar with the abbreviation or acronym but can clarify which meaning of an abbreviation or acronym is appropriate to use. For example, the acronym "ADA" stands for both the American with Disabilities Act as well as the American Dental Association. 4. Be predictable - users should understand the consequences of their actions and be aware of what they must do next. TASK 5. The number of actions should be small, so that novice and first-time users can carry out simple tasks successfully and thus reduce anxiety, build confidence, and gain positive reinforcement.[1] 6. Information feedback about the accomplishment of each task is helpful.[1] o For example, in Chevy Chase Online Banking, after logging out users will see the following message: You have successfully logged out. Thank you for using Chevy Chase Online Banking. 7. Constructive, specific error messages with positive tone should be provided when users make mistakes.[1] o For example, users who enter an invalid password in AOL, will see the following message: You have entered an invalid password. Please try again. If you are an AOL member and you also use AOL Instant Messenger with the same screen name, you must use your AOL password at Screen Name Service instead of your AIM password. If you are not an AOL member and you've forgotten your password, click here. 8. Avoid placing frequently used functions deep in a menu structure.[13] 9. Enable easy searches. o If search functions are provided, provide a variety of search options for different skill levels and preferences. o Example: For a search field, provide a tree of indexed links 10. When a timed response is required, alert the users, and give sufficient time to indicate more time is needed. CLARITY - extent to which you succeed in conveying your intentions to the user. 11. Make sure the users know what will happen when they press a button or select an option based on the information at hand. 12. Use font styles/sizes consistently o Using font styles/sizes inconsistently, and using cute icons that have little or no relation to the operations can reduce clarity. 13. Provide descriptive names for all interface components and any object using graphics instead of text (e.g., palette item or icon). [13] 14. Link text should be meaningful but brief. [14] 15. Use conceptual models and metaphors that make sense o Common metaphors - toolbox, desktop, trashcan o Classic misuse - on Macintoshs (MACs) to eject a diskette you drag it into a trashcan. 16. Good ALT text for all graphics. [14] o Every image should have ALT text. o Convey the important information in the image. o Use simple text for simple images (e.g. "*" for a bullet, numbers for a numbered image, and a single space character or an empty string for invisible images that are typically used for spacing). o For complex images, provide a link to a separate page with a more detailed description. 17. Avoid using image maps or use image maps properly o Provide text links in addition to any image map, either in-line or at the bottom of the page. [14] o Use useful ALT text (such as "Map of campus; use text links below"). [14] ELEGANCE = novelty, simplicity, economy, and effectiveness 18. Don't use unnecessary ornamentation or embellishments 19. Select words that convey meaning accurately and economically (use the fewest words possible that have an unambiguous meaning) 20. Restricting vocabulary to a small number of familiar, consistently used concept terms is essential to begin developing the user's knowledge. [1] 21. Use common words, not "techno-jargon" FUNCTION 22. Know when to use complex dialog boxes versus wizard style ones o Complex - used for intermediate and expert applications. o Wizard for novice or first time - one time applications (e.g. installation wizards). 23. Beware of "overloading" controls o Overloading means that one control has many meanings based on the current context of actions of the user. For example, in Microsoft Word (and PowerPoint) the left mouse button is used to select, drag, resize, etc, based on the location and contents of the window. Other commonly overloaded controls are the ESC, CTL, and Enter keys. BASIC 24. Involving novice users into design process and evaluation of the web site might be a key to success. 25. Extensive testing and iterative refinements are necessary parts of web design and as well as every development project. HELP FACILITY 26. Online Help, Online Tutorial o Users at different levels of proficiency need different levels of help. Novice users will require a lot of help with deep explanations and definitions of the terms used. As they progress they will still need help to explain how to use complex functions. o The tutorial approach requires more detailed explanation: not only how to do something, but also why it is done, how other things are affected and example. [3] 27. Interface assistants: Wizard, Selective prompting [2] o Prompting is instructional information. It takes the form of messages or other advice, such as the values to be keyed into a field. Prompting is also the system's way of requesting additional or corrected information, or of guiding users step by step through tasks. Inexperienced users find prompting a valuable aid in learning a system. Experienced users, however, often find prompting undesirable. It shows them down, then adds "noise" to the screen, and reduces the amount of working information that can be displayed at one time. Ideally, prompting should be available only as needed. People should be able to selectively or completely turn prompting on or off as needed. As an alternative, two separate sets of screens could be made available, one with prompts, the other without. 28. Webmaster E-mail help o Setup Webmaster contact information 29. Others o Frequently Asked Question list o News group
|
|||||||
| Tzu-Ting Chen Department of Computer Science University of Maryland College Park, MD 20742 USA jacktar@cs.umd.edu April 2001 |
Previous | Top | Next | ||||||