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

Re: javascript accessibility

From: Tom Croucher <tom.croucher@sunderland.ac.uk>
Date: Thu, 22 Apr 2004 15:57:24 +0100
To: w3c-wai-gl@w3.org
Message-id: <BCAD9BE4.4960%tom.croucher@sunderland.ac.uk>

Jens said:

> well, of course there are things to be considered when using JavaScript.
> Unfortunately, I'm somewhat disposed, but you should at least regard that
> you don't generate markup via JS (a fact several 'natural persons' and
> 'corporate bodies' often disobey) since that markup's just not present using
> any UA not capable (anymore) of JS, of course not.

I don't entirely agree with this. I view JavaScript as a means to provide
convenience rather than exclusive function. However one of the most
accessible ways I know to do it is have JavaScript generate the elements
which are providing that functionality. For example if you have a button
which links to javascript.this.print(); then if it is also generated with
JavaScript only the people able to use it will have it included in their
content. In this way I think it is extremely valid to provide redundant or
more convenient functionality which is also provided by some other server or
user agent function.

Tom
Received on Thursday, 22 April 2004 10:58:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:29 GMT