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

Javascript and WCAG

From: Phil Evans <pae9@star.le.ac.uk>
Date: Thu, 16 Jun 2011 16:09:01 +0100
Message-ID: <4DFA1C8D.7050800@star.le.ac.uk>
To: w3c-wai-ig@w3.org
Hi again,

Complete change of tack and hopefully I'll stop bothering you soon:

Last time I looked into WCAG was under WCAG 1.0, which included this 
priority 1 point:

"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] "

I've just realised that WCAG2.0 does not seem to have an equivalent 
rule. Is this correct? (I assume this just means that javascript is now 
so mainstream that there is no obligation to cater for non-js users). 
i.e. can I be WCAG compliant without having to write non-javascript 
interfaces for all of my control forms?

Thanks again!



Phil Evans,
Swift Development Scientist
X-ray and Observational Astronomy Group,
University of Leicester

Tel: +44 (0)116 252 5059
Mobile: +44 (0)7780 980240

Follow me as a Swift scientist on Twitter: @swift_phil
Received on Thursday, 16 June 2011 15:09:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:37 UTC