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 17:24:58 -0400 (EDT)
Message-ID: <1180.>
To: <pjenkins@us.ibm.com>
Cc: <sdale@stevendale.com>, <david@djwhome.demon.co.uk>, <w3c-wai-ig@w3.org>

Phill Jenkins said:
>>why do we NEED client side scripting?
> One example why we need client side scripting is the same reason we need
>  client side image maps - so the processing is done on the client and
> not  on the server - saves processing time to not have to go to the
> server for  everything each time.  What does this have to do with
> disabilities -  nothing unless the configuration doesn't handle client
> side scripting. In  other words it is a configuration issue - not a
> disability issue.

And this is a mandatory requirement?  It is not NEEDED,  granted it could
be helpful, but the question was and still is why is it NEEDED?

>> Can someone give me an example that requires Client Side Scripting
>> while
> remains accessible when the scripting
> is used?
> Some of this confusion may be in the term "accessible".  Jimthatcher.com
>  [note 2] discusses some examples that are perfectly supported with
> properly configured assistive technology & browsers and create no
> disability barriers.

The configuration may be valid on PC UAs, but what about Cell Phones and
PDAs?  There is not much memory available to bloat the UAs so that
frivoless features can be made accessible.

> The ibm.com/able guidance [note 1] for scripting is
>  also useful.  For example, checking the required fields in a form on
> the  client before sending the data to the server is common and creates
> no  disability issues.

This is a good case of not NEEDED but useful.

>Scripts that add interactive visual highlighting
>  (onMouse over's) improve usability and benefit the learning disabled.
> Notice I didn't use the term "accessible" in the sentences.
This can be done via CSS giving the user the ability to easily modify the
highlighting color using their own stylesheets.

> So, if the application or situation requires quicker throughput,  better
>  ease of use, etc. then client side processing is the answer.  In other
> words, that is why it was invented, to reduce the burden on the server.
Another way to limit the burden of the servers is to limit access to
websites for those with disabilities.
Received on Tuesday, 1 June 2004 17:25:33 UTC

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