OIT > WCG > UI/UX > Help, Feedback, and Errors

Help, Feedback, and Errors

From Userfocus' 247 web usability guidelines page:

1. The FAQ or on-line help provides step-by-step instructions to help users carry out the most important tasks.
2. It is easy to get help in the right form and at the right time.
3. Prompts are brief and unambiguous.
4. The user does not need to consult user manuals or other external information to use the site.
5. The site uses a customised 404 page, which includes tips on how to find the missing page and links to "Home" and Search.
6. The site provides good feedback (e.g. progress indicators or messages) when needed (e.g. during checkout).
7. Users are given help in choosing products.
8. User confirmation is required before carrying out potentially "dangerous" actions (e.g. deleting something).
9. Confirmation pages are clear.
10. Error messages contain clear instructions on what to do next.
11. Immediately prior to committing to the purchase, the site shows the user a clear summary page and this will not be confused with a purchase confirmation page.
12. When the user needs to choose between different options (such as in a dialog box), the options are obvious.
13. The site keeps users informed about unavoidable delays in the site's response time (e.g. when authorising a credit card transaction).
14. Error messages are written in a non-derisory tone and do not blame the user for the error.
15. Pages load quickly (5 seconds or less).
16. The site provides immediate feedback on user input or actions.
17. The user is warned about large, slow-loading pages (e.g. "Please wait…"), and the most important information appears first.
18. Where tool tips are used, they provide useful additional help and do not simply duplicate text in the icon, link or field label.
19. When giving instructions, pages tell users what to do rather than what to avoid doing.
20. The site shows users how to do common tasks where appropriate (e.g. with demonstrations of the site's functionality).
21. The site provides feedback (e.g. "Did you know?") that helps the user learn how to use the site.
22. The site provides context sensitive help.
23. Help is clear and direct and simply expressed in plain English, free from jargon and buzzwords.
24. The site provides clear feedback when a task has been completed successfully.
25. Important instructions remain on the screen while needed, and there are no hasty time outs requiring the user to write down information.
26. Fitts' Law is followed (the distance between controls and the size of the controls is appropriate, with size proportional to distance).
27. There is sufficient space between targets to prevent the user from hitting multiple or incorrect targets.
28. There is a line space of at least 2 pixels between clickable items.
29. The site makes it obvious when and where an error has occurred (e.g. when a form is incomplete, highlighting the missing fields).
30. The site uses appropriate selection methods (e.g. pull-down menus) as an alternative to typing.
31. The site does a good job of preventing the user from making errors.
32. The site prompts the user before correcting erroneous input (e.g. Google's "Did you mean…?").
33. The site ensures that work is not lost (either by the user or site error).
34. Error messages are written in plain language with sufficient explanation of the problem.
35. When relevant, the user can defer fixing errors until later in the task.
36. The site can provide more detail about error messages if required.
37. It is easy to "undo" (or "cancel") and "redo" actions.