W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

Re: javascript accessibility

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 23 Apr 2004 14:18:58 -0400 (EDT)
To: Maurizio Boscarol <maurizio@usabile.it>
Cc: W3C WAI <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.55.0404231413180.8894@homer.w3.org>

Jonathan Chetwynd also did a bunch of work with others on what he hoped would
one day be a techniques document for WCAG 2 on javascript. He is no longer
involved with WAI, but maintains the document:

You might find that interesting, adn I know Jonathan is still interested in



On Thu, 22 Apr 2004, Maurizio Boscarol wrote:

>Hello all.
>A student asked me about accessibility of javascript.
>I have some doubt about what can or cannot be considered accessibile in
>JS. In fact, from a point of view, JS should simply be avoided as the
>only mean to implement a relevant functionality. I.e., the same
>functionality should be available (in other ways) even if JS is not
>active on that user agent.
>On the other hand, JS events should be as modality-independent as
>possibile (onSelect instead of onClick, etc). But, still, if JS is not
>supported, this is simply not sufficient.
>I'm sure this has already been discussed in the list. I've just looked
>at wcag 2.0 draft, and have not found a simple answer, so I turn the
>question to the WG.
>Thanks all
>Maurizio Boscarol

Charles McCathieNevile  http://www.w3.org/People/Charles  tel: +61 409 134 136
SWAD-E http://www.w3.org/2001/sw/Europe         fax(france): +33 4 92 38 78 22
 Post:   21 Mitchell street, FOOTSCRAY Vic 3011, Australia    or
 W3C, 2004 Route des Lucioles, 06902 Sophia Antipolis Cedex, France
Received on Friday, 23 April 2004 14:18:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:49 UTC