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

RE: Site Maps and nested navigation

From: Stuart Smith <Stuart.M.Smith@manchester.ac.uk>
Date: Mon, 12 Dec 2005 09:23:11 +0000
To: WAI-IG <w3c-wai-ig@w3.org>
Message-ID: <20051212092311890.00000003840@MARVIN>

Hi All

The UDM menu claims to be accessible and I suppose if all you are worried about is passing some automated or to the letter interpretation of the Guidelines it is. BUT if you put it in a screen reader (I used hompage reader) and also tried with Webbie (which preps a page for a screen reader) it is a real pain. You end up with a massive list of links which has no obvious structure to it of skip ability, so lose your place blind users and you have to start again. Basically the screen reader usability seems very poor. 

There is lots that is good but definitely not a solution as far as I can see. It does seem that either lists are the wrong way to mark-up a menu or there needs to be a better method of client side tools managing the (X)HTML on arrival in a list.

Stu

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf Of Terrence Wood
Sent: 11 December 2005 00:51
To: 'WAI-IG'
Subject: Re: Site Maps and nested navigation



On 8 Dec 2005, at 11:20 AM, Rebecca Cox wrote:
> I agree - vast lists not a good thing. However, if you have to use 
> them, and also have to present them as dropdown menus, have you looked 
> at UDM?
>
> See http://www.udm4.com/

UDM is the nicest js menu around.... biggest problem is, apart from not working in Opera (the onfocus doesn't fire), how do you let users know how to use it (using arrow keys is not obvious)?

And it still doesn't solve the issue of page weight due to having the site map load with every page.

Drop down menu's - just avoid them.

kind regards
Terrence Wood.
Received on Monday, 12 December 2005 09:23:23 GMT

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