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

RE: JavaScript and Accessibility

From: William R Williams <wrwilliams@fs.fed.us>
Date: Thu, 12 Jun 2003 09:12:15 -0700
To: w3c-wai-ig@w3.org
Message-ID: <OF8E4BC5E8.4D2187CF-ON88256D43.0058DA4A@r5.fs.fed.us>

WCAG 1.0, Checkpoint 6.3 -- Ensure that pages are usable when scripts,
applets, or other programmatic objects are turned off or not supported. If
this is not possible, provide equivalent information on an alternative
accessible page. [Priority 1]

508  1194.22 (l) -- When pages utilize scripting languages to display
content, or to create interface elements, the information provided by the
script shall be identified with functional text that can be read by
assistive technology.

Are you suggesting there are significant differences between the two
standards? In reality, why would a "developer" simply identify, in a
functional manner, an instance of script usage (as required by 508) without
ensuring the information is usable as well?

======================
Bill Williams
Communications Specialist
USDA Forest Service, Region 5
707.562.9005
wrwilliams@fs.fed.us
======================

"RUST Randal" <RRust@COVANSYS.com

Jesper Tverskov said:

> 3) Why do we not have a similar guideline about scripts in
> Section 508?

This is my biggest problem with 1192.22, but I think that Javascript is
more of a usability issue than an accessibility issue.

----------
Randal Rust
Covansys Corp.
Columbus, OH
Received on Thursday, 12 June 2003 12:16:45 GMT

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