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

Re: Accessible road maps

From: Steven Dale <sdale@stevendale.com>
Date: Tue, 1 Jun 2004 13:17:38 -0400 (EDT)
Message-ID: <4650.>
To: <pjenkins@us.ibm.com>
Cc: <david@djwhome.demon.co.uk>, <w3c-wai-ig@w3.org>

This is all a nice argument for the sake of debate.

But my question still has not been answered,
why do we NEED client side scripting.  Can someone give me an example that
requires Client Side Scripting while remains accessible when the scripting
is used?


Phill Jenkins said:
> Matt wrote:
>> So, what do we do? Banish scripting from the Web? Certainly not. We
>> may
> David responded:
> <clip>
> Remember that HTML and thus the web were created in deliberate rejection
> of more sophisticated tools...
> Phill replies:
> I view HTML's purpose a little differently and I believe it has evolved.
>  For example, events such as onClick, onKeyPress, etc are actually part
> of  the HTML spec [see note 1].  I had thought they were part of the
> JavaScript spec but they are not!
> David continued with:
> Most web sites nowadays are computer programs, not documents, and
> attempt to override the viewing tool's user interface.
> Phill replies:
> That is exactly Matt's point.  You seem to be supporting his argument.
> Many WAI individuals have focused on "banning" interactivity of web
> sites  created from events and scripting that now we are late coming up
> with  better techniques and specs to solve the problems.  Same thing
> happened  over a decade ago when command line PC DOS applications were
> replaced with  Window GUI's.
> Regards,
> Phill Jenkins
> [Note 1] HTML 4 spec on Events
> http://www.w3.org/TR/REC-html40/interact/scripts.html#h-18.2.3
Received on Tuesday, 1 June 2004 13:19:17 UTC

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