Link-Optimisation
Link-optimising means - among other things - letting the user know what to expect at the end of the link.
Provide a brief, one-line preview of the content to be found after selecting the link to motivate the user to continue.
Page-Chunking
Make text short without sacrificing depth by splitting the information into multiple nodes connected by hypertext links.
Each page can be brief and yet the full hyperspace can contain much more information than would be feasible in a printed article.
Long and detailed background information can be relegated to secondary pages; similarly, information of interest to a minority of readers can be made available through a link without penalising those readers who do not want it.
Hypertext should not be used to segment a long linear story into multiple pages.
Having to download several segments slows reading and makes printing more difficult.
Proper hypertext structure is not a single flow "continued on page 2"; instead, split the information into coherent chunks that each focus on a certain topic.
The guiding principle should be to allow readers to select those topics they care about and only download those pages.
In other words, the hypertext structure should be based on audience analysis.
Additionally, each hypertext page should be written according to the "inverted pyramid" principle that is commonly taught in journalism schools.
Start with a short conclusion so that users can get the gist of the page even if they do not read all of it; then, gradually add detail.
The guiding principle should be that the reader can stop at any time and still have read the most important pieces of information.
Ten Usability Heuristics:
by Jakob Nielsen
Ten general principles for user interface design: "Heuristics" are more like rules-of-thumb than specific guidelines.
System-Status Visibility
Always inform users what is going on. Use appropriate feedback, in a reasonable time.
Match Between System & the Real World
Speak the users' language with familiar words, phrases & concepts, rather than system-oriented jargon. Follow real-world conventions; making information appear in a natural & logical order.
User Control & Freedom
Users often mistakenly choose a system function so need a clearly marked "emergency exit" without going through an extended dialog. Support undo & redo.
Consistency & Standards
Users waste valuable time wondering whether different words, situations or actions are the same. Follow platform conventions.
Error Prevention
Even better than good error messages is careful design that prevents problems occurring in the first place. Either eliminate error-prone conditions or check for them - and present users with confirmation options before committing.
Recognition rather than Recall
Minimize user memory-load by making objects, actions & options visible. Users trying to remember information from one part of the dialog to another distracts from the job-in-hand. Instructions should be visible or easily-retrievable, whenever appropriate.
Flexibility & Efficiency-of-Use
Accelerators - unseen by the novice user - may speed up expert-user interaction; catering to both inexperienced & experienced alike. Allow users to tailor frequent actions to their abilities.
Esthetic & Minimalist Design
All extra information in a dialog competes with relevant information and diminishes their relative visibility & value. Remove irrelevant or rarely-needed information from dialog boxes.
Help Users Recognize, Diagnose & Recover from Errors
Error messages should be expressed in plain language, precisely indicate the problem & constructively suggest a solution.
Help & Documentation
No documentation is the ideal, but it may be necessary to provide help. Any such information should be easy-to-search, user-task focused, list concrete steps to undertake & be brief.
No comments:
Post a Comment