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

Remote Scripting -- Compliant with 508 and WCAG?

From: RUST Randal <RRust@COVANSYS.com>
Date: Fri, 5 Dec 2003 11:03:43 -0500
Message-ID: <1A729C6059E7CD4CA1DFE3985E600421034346D5@fth-ex02.covansys.com>
To: <w3c-wai-ig@w3.org>

Many of the Web applications that we build are conversions of
Client/Server apps to Web apps. The biggest issue that we have to deal
with lies in people not understanding that you cannot do client-side
processing on the Web.

However, it is possible to do it when Remote Scripting is used. But
Remote Scripting relies on Javascript. In my mind, this violates 508,
Guideline L and WCAG 6.3.

But what if the client said it was OK, and required all users to keep
Javascript turned on? Keep in mind that all users of the application are
employees of the State, Bureau, etc.

Would it be possible to use Remote Scripting and still retain
compliance? Can assistive technologies handle it? 

----------
Randal Rust
Covansys Corp.
Columbus, OH 
Received on Friday, 5 December 2003 11:03:51 GMT

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