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

Re: javascript menus and accessibility

From: David Woolley <david@djwhome.demon.co.uk>
Date: Thu, 14 Dec 2000 23:36:30 +0000 (GMT)
Message-Id: <200012142336.eBENaU126584@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org
> 
> An example (an applet version) of what I'm concerned about can be found
> at: http://www.buseco.monash.edu.au/oldTechServ/

There is no javascript on that page (as viewed with Lynx).

Javascript cannot be an applet.

The common idiom for creating popups causes accessibility problems, but
can be fixed by designing properly, i.e. write the page to work without
scripting then add the scripting whilst keeping the old function.
Specifically, never use javascript: URLs, except where client side 
scripting is of the essence of the page.  Instead, use a normal link and
override it with an onclick attribute.  Make sure the onclick returns
false to prevent the href also working on an JS enabled browser.

Note the page is cache unfriendly (no last-modified-date) and uses a
non-standard HTTP header (without an x- prefix) (window-target).
Received on Thursday, 14 December 2000 18:36:35 GMT

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