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

CSS nested list menus, how much is too much?

From: Rebecca Cox <rebecca@signify.co.nz>
Date: Fri, 12 Aug 2005 09:57:58 +1200
To: <w3c-wai-ig@w3.org>
Message-Id: <20050811215805.E92FE78E3@hume>

Hi peops

With the new method that a lot of people are using to create "accessible,
semantic" dropdown menus I am wondering if its all good in accessibility
terms or not.

Say you have your site navigation marked up as nested unordered lists, and
this is on every page of your site. A lot of people are applying CSS and a
touch of javascript to this to create dropdown menus (ie with the nested
list content hidden until the user interacts with the top level of the

Just ignoring the dropdowns aspect of this, is there any problem where for
example you might have every page in your site linked in a big nested list
of for example 100 or more items ? 

I am thinking it might be better to cut down the number of links in the HTML
as it's a lot to tab through for example. And possibly not the best with
some screen readers?

An example (just the HTML, no dropdowns effect applied) is at
http://www.reb.net.nz/navigation/ - most sites would have more navigation
items so it would be worse than here.

I'm interested in whether others see this as a problem, and if so what
solutions people are using.

Received on Thursday, 11 August 2005 21:58:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:26 UTC