OIT > WCG > UI/UX > Task Orientation
Task Orientation Guidelines
From Userfocus' 247 web usability guidelines page:
- The site is free from irrelevant, unnecessary and distracting information.
- Excessive use of scripts, applets, movies, audio files, graphics and images has been avoided.
- The site avoids unnecessary registration.
- The critical path (e.g.login, subscription) is clear, with no distractions on route.
- Information is presented in a simple, natural and logical order.
- The number of screens required per task has been minimised.
- The site requires minimal scrolling and clicking.
- The site correctly anticipates and prompts for the user’s probable next activity.
- When graphs are shown, users have access to the actual data (e.g. numeric annotation on bar charts).
- Activities allocated to the user or the computer take full advantage of the strengths of each (look for actions that can be done automatically by the site, e.g. postcode lookup).
- Users can complete common tasks quickly.
- The task sequence parallels the user’s work processes.
- The site makes the user’s work easier and quicker than without the system.
- The most important and frequently used topics, features and functions are close to the centre of the page, not in the far left or right margins.
- The user does not need to enter the same information more than once.
- Important, frequently needed topics and tasks are close to the 'surface' of the web site.
- The path for any given task is a reasonable length (2-5 clicks).
- When there are multiple steps in a task, the site displays all the steps that need to be completed and provides feedback on the user’s current position in the workflow.
- Users of the site do not need to remember information from place to place.
- The use of metaphors is easily understandable by the typical user.
- Details of the software's internal workings are not exposed to the user.
- The site caters for users with little prior experience of the web.
- The site makes it easy for users to explore the site and try out different options before committing themselves.
- A typical first-time visitor can do the most common tasks without assistance.
- When they return to the site, users will remember how to carry out the key tasks.
- The functionality of novel device controls is obvious.
- Action buttons (such as "Submit") are always invoked by the user, not automatically invoked by the system when the last field is completed.
- Command and action items are presented as buttons (not, for example, as hypertext links).
- If the user is half-way through a transaction and quits, the user can later return to the site and continue from where he left off.
- When a page presents a lot of information, the user can sort and filter the information.
- If there is an image on a button or icon, it is relevant to the task.
- The site prompts the user before automatically logging off the user, and the time out is appropriate.
- Unwanted features (e.g. Flash animations) can be stopped or skipped.
- The site is robust and all the key features work (i.e. there are no javascript exceptions, CGI errors or broken links).
- The site allows users to rename objects and actions in the interface (e.g. naming delivery addresses or accounts).