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

Re: javascript menus and accessibility

From: Charles McCathieNevile <charles@w3.org>
Date: Sun, 17 Dec 2000 09:18:27 -0500 (EST)
To: Dey Alexander <dey.alexander@its.monash.edu.au>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0012161342341.27193-100000@tux.w3.org>
Some problems:

If the scripts/applets are required in order to get to the menus, then some
users won't ever see them - there are a number of text-to-speech browsers
without javascript support. And there are a number of people who can more or
les only navigate using the keyboard, so using mouse events is a big

It is not always clear that a dropdown has appeared/disappeared.

There is a known problem with the use of onChange selectors for menus in
Javascript, when a user is navigating via the keyboard. What happens is that
they select the menu, and move from the first entry to the second. That fires
the selector. So in allist of countries, it is the first one that is always
selected, since it is impossible to get past that.


Charles McCN

On Fri, 15 Dec 2000, Dey Alexander wrote:


  I was wondering if anyone could tell me whether drop down menus, of the
  type that are activated by a javascript or applet rollover, present
  accessibility problems for text-to-speech browsers.

  An example (an applet version) of what I'm concerned about can be found
  at: http://www.buseco.monash.edu.au/oldTechServ/


Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
September - November 2000:
W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France
Received on Sunday, 17 December 2000 09:18:33 UTC

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