Hyperlink Text: When creating documents, choose the "hot-link" text carefully. Make your links meaningful -- that is, that they avoid On-Line-specific references, and that they don't detract from readability. Links consist of the anchor containing the Uniform Resource Locator (URL) for the document and the hotspot (explanatory text for the link that is usually highlighted or underlined) in the browser. Hotspots should be a descriptive and integral part of the text. They should inform users of what they'll be getting, whether it's further information from the same provider, a related document from another provider, a Gopher server, Telnet session, or WAIS search. You may also want to let the reader know beforehand if they'll be loading an extremely large file [xxx KB] (though not necessarily in the hotspot text). Avoid extra spaces inside the anchors- normal word spacing should occur outside the anchors. Try to make linking words or phrases part of a meaningful sentence, so that the user has a clear understanding of where they are going once they connect to another page. Make no mention of the links themselves in the text. The paragraph in which a link is contained should be as readable as if there were no links present at all. For example, avoid sentences like, "You can find out more about Baltimore by clicking here (which is also bad because it refers to "clicking", which assumes that everyone is using a mouse with their browser!). A much better style is: More information is available from Central Computer's Page.
Link Maintenance: It can be very irritating for the user to find several of a site's links are dead. Check the embedded links periodically. Currently there are tools being developed to automate this process and assist the webmaster with this task.
Redundancy: If another site has several relevant resources - don't point to them all. Just include one link to the higher level. Many sites are now specializing in well-defined subject areas; e.g. Revolutionary War Web Site
Separators: Use horizontal rules <HR> and bitmap dividers (e.g. =========== ) to partition the page between subject headings. Use graphical lines sparingly to keep the download time down. The use of graphical bullets is accepted, keeping in mind the size and quantity of the bullets on the page. Each graphical line and bullet must be subsequently downloaded and each adds to the rendering time.
Sea of Blue Syndrome: Avoid making everything a hyperlink. Calculated and inventive phrasing will allow the use a key phrase to be used a the hyperlink in place of an entire sentence. Choosing a hot-link word(s) first allows the author to develop a context sentence around the hot-link, preserving the integrity of the link text.
Based partially on The World-Wide Web Unleashed, by John December and Neil Randall, published by SAMS.
"Meet the user's needs." Play to the audience. The web must be designed to serve the users, not the authors, editors, designers, or developers. When building web pages always ask yourself, "what will help users accomplish their objectives?"
"Efficiently use resources." Web users want to acquire information easily, efficiently--and elegantly, if possible. Determine which features will allow them to do so and implement them. Always consider time, space, and maintenance requirements--the users' and your own.
"Create a consistent, pleasing, and efficient look and feel." The organization of the web must be the product of a common vision. The design should be visually appealing and operationally elegant. Each page should be part of a coherent whole, yet capable of being identified and understood independent of the context of the web.
This document was produced using HTML Transit