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

Re: feedback:Fw: Drop Down Menus

From: Jim Ley <jim@jibbering.com>
Date: Sun, 6 Jan 2002 19:12:10 -0000
Message-ID: <009001c196e6$0f265760$ca969dc3@emedia.co.uk>
To: "wai-ig list" <w3c-wai-ig@w3.org>
> ----- Original Message -----
> From: "Doug Wakefield" <wakefield@access-board.gov>
> To: <sec508@trace.wisc.edu>
> Sent: Friday, January 04, 2002 3:35 PM
> Subject: RE: Drop Down Menus
>
> > <a href="javascript:myFunction();">Take Me There!</a>
>
> In this case, the anchor link triggers the JavaScript function
> 'myFunction()'. In this case, the function (myFunction()) would have to
> lookup the selected element in the select box (via the 'quicklinks'
> name)
> after first looking up the appropriate form (via the 'form1' name)
> containing the select box.

This is complete garbage the javascript: psuedo protocol should not be
used,
the comp.lang.javascript FAQ is very clear on this (and the group isn't
even suggesting it from just an accessibility perspective, a simply code
reliability perspective is enough, quite apart from the considerable
accessibility issues with it.  http://jibbering.com/faq/#FAQ4_24

> Unfortunately, the select tag itself supports relatively few event
> handlers
> and onChange is really one of the few that works reliably (albeit,
> inaccessibly) in it. Thus, you can't use 'onClick' on a select tag
> directly
> and expect reliable behavior across different platforms.

Well you can't rely on onChange either, and onclick only realisitically
excludes NN4, and as you need a submit button in any case, it's not
disadvantaged much.  onClick is certainly reasonably safe, and duplicates
the "instant response" which people presumably want by using onchange.
Of course you need a fallback submit button, but then you do anyway for
the non javascript people.

Jim.
Received on Sunday, 6 January 2002 14:13:49 GMT

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