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

RE: Remote Scripting -- Compliant with 508 and WCAG?

From: RUST Randal <RRust@COVANSYS.com>
Date: Fri, 5 Dec 2003 12:30:41 -0500
Message-ID: <1A729C6059E7CD4CA1DFE3985E600421034346DB@fth-ex02.covansys.com>
To: <w3c-wai-ig@w3.org>

Phill Jenkins said;

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

> Yes, <snip.  Just like 
> HTML or GUI programs, both can and cannot be made accessible, 
> it depends on what the author does.

I agree. I see it as more of an access issue, rather than a disability
issue.

> If all the 
> employees in the State, Bureau, etc. have access to a capable 
> browser & assistive technology, then the client side 
> scripting can (and should) be made directly accessible to them.

Makes sense to me.

> Interesting to see that many see a conflict, or at least an 
> oddity between WCAG 1.0 Checkpoint 6.3 and 8.1.  In other 
> words, why does one need to meet 8.1 if the site already 
> works without scripting by meeting 6.3?

Right. I wish the guidelines dealt with scripting in a more real-world
manner. Namely, a lot more people allow Javascript than don't. It should
be simple enough just to say that if you use JS, make sure the same
functionality can be performed if JS is turned off. I know it does say
that, in a roundabout way, in WCAG, but it does get contradictory.

Thanks for the extra links. I have all of those bookmarked, but it
remined me that I have them and need to revisit them.

----------
Randal Rust
Covansys Corp.
Columbus, OH
Received on Friday, 5 December 2003 12:31:28 GMT

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