W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2005

Re: CSS nested list menus, how much is too much?

From: David Woolley <david@djwhome.demon.co.uk>
Date: Fri, 12 Aug 2005 20:50:51 +0100 (BST)
Message-Id: <200508121950.j7CJopu01941@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> navigation, Furnas showed that it is ideal to show only small views (a
> relatively small number of choices) that the number of navigation steps

I think the problem is that on commercial web pages, the bloat factor,
with scripting etc. means that every distinct web page takes a long time
to load, so putting a multilevel menu on the home page, once you've take
the initial download time hit, is faster than having a true web
(probably directed acyclic graph or tree) of navigation pages.

On the other hand, using Lynx, on a site with clean HTML, spreading
the navigation over multiple pages is very responsive, even on a 33K
modem.

(The other problem is that designers don't want to separate navigation
from content, so every content page carries a navigation overhead - my
own view is that the missed opportunity was for browsers to use link
elements to find the immediate superior navigation page and automatically
display it in windowed environments.)
Received on Friday, 12 August 2005 19:59:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:22 GMT