W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2004

Re: DHTML drop down menus ADA compliant

From: Jim Ley <jim@jibbering.com>
Date: Wed, 14 Jan 2004 20:02:55 -0000
Message-ID: <029001c3dae2$f73a6810$60fea8c0@Snufkin>
To: <w3c-wai-ig@w3.org>

"Juan Ulloa" <julloa@bcc.ctc.edu>
> You can have a website with DHTML dropdown menus that is accessible.  Some
> things you need to keep in mind are.
> The menu's (not the dropdowns) themselves cannot be generated by

The menus could be generated by javascript but it may well not be the most
efficient (they could rewrite links from another place on the page, perhaps
moving the dynamic menus to a different logical position, or just adding
extra navigation to the partial navigation in the document - for example
adding links to sub-topics instead of just topics.

> And if javascript is turned off, you should be able to click on the menu
> item and allow you to go to webpage that has the options listed on the
> dropdown.

I'm slightly concerned by your description here, it seems a rather narrow
restriction on alternative mechanisms for providing the same functionality
to the user.  My concern is generally more about keyboard and voice browser
access to the menus in an accessible manner (ie can you tab to each menu
item in a sensible order, and does the voice browser render the links
distinct enough and in a sensible order.)

> Two dropdown menu scripts that can be used in an accessible website are:
> one generated by Macromedia Fireworks and the one created by Opencube.com

I'd be interested in the definition of accessible in the cases of the above
2 menus, neither (unless they have been consideralby improved in recent
times) would be considered accessible by me.

Received on Wednesday, 14 January 2004 16:13:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:27 UTC