W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2004

Javascript alternatives not necessary?

From: Fentress, Robert <rfentres@vt.edu>
Date: Mon, 19 Jul 2004 11:04:58 -0400
Message-ID: <E7BD4EDD62660F44922C0B11258FBE8F401215@fangorn.cc.vt.edu>
To: <w3c-wai-gl@w3.org>

I just noticed there is no 2.0 equivalent to the WCAG 1.0 guideline:

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]

Is this intentional?  If so, it is wonderful.  6.3 always struck me as quite unreasonable in that it made conforming to other standards such as SCORM, which uses javascript as part of its specification, impossible.  The important thing is that the scripts are made accessible, particularly by allowing keyboard access to all the functionality, not that all functionality be available when javascript is not supported.  That makes many kinds of web applications impractical.

Sorry if this is ground that has already been covered, but I am new to the list and wanted to make sure I am understanding the standard correctly.

Received on Monday, 19 July 2004 11:05:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:50 UTC