Provide a summary of the web page, put critical content and navigation at the top of the web page, avoid forcing the user to scroll more than 3 times, provide something to look at while the web page is loading and give the web page an informative title.
Written by Philip Chalmers who is based in the Medway area of Kent, England, United Kingdom.
|
Provide a summary
Put critical content and navigation at the top Avoid forcing the user to scroll more than 3 times Make it easy to move within the page |
What does Jorn Barger do to make The WWW page-length debate more usable, and what else could he have done?
The page contains 2 summaries:
Yes, the page starts with a summary and a table of contents which functions as a menu.
You have to scroll a whole lot more to see all the content of The WWW page-length debate
But was there a better alternative? We don't think so:
This is a good example of how you have to make trade-offs when deciding how long a page should be.
We think this is the one trick Jorn Barger missed. There are no links back to the table of contents. Suppose you read a section, have a look at the table of contents, then decide you want to continue with the next section. You can't use the Back button to return to where you were reading. You have only 2 options:
The page certainly does that - you can instantly see what the subject is and the range of topics covered.
The first line of the page tells you what the page is about.
So does the title in the browser window's title bar.