RE: Call for feedback on accessible DHTML menus

I think that is a poor argument for not using features like that. Users
can still quite happily refer to a piece of information or section of a
site, they just may not be able to refer to a specific widget. However
the sort of inexperienced user likely to refer to part of a widget is
likely to be confused by varying screen resolutions, different browsers,
a whole assortment of things. 

Tom

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
Behalf Of Charles McCathieNevile
Sent: 24 September 2003 14:43
To: tcroucher@netalleynetworks.com
Cc: gdeering@acslink.net.au; 'James Craig'; 'WAI Interest Group'
Subject: Re: Call for feedback on accessible DHTML menus


The problem with not getting the same functionality is that it becomes 
very difficult to work together - if I describe following a link on a 
page that someone else doesn't have on that page, then there is a lot 
of confusion.

Cheers

Chaals

On Tuesday, Sep 23, 2003, at 15:35 Europe/Zurich, Tom Croucher wrote:

> Accessibility and functionality are not the same.
>
> A site can be accessible with dhtml menus if one can still use the 
> site.
> You should think of drop down menus as more link options. If the main
> links (at the top of the menu) are still usable it doesn't matter.
Most
> of this is completely a mute point for screen readers which often see
> the entire menu anyway since the dhtml menus usually just visually
hide
> the extra options they don't want on screen at any point.
--
Charles McCathieNevile                          Fundación Sidar
charles@sidar.org                                http://www.sidar.org