- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Thu, 16 Jun 2011 11:13:54 -0400
- To: w3c-wai-ig@w3.org
[Phil wrote] > i.e. can I be WCAG compliant without having to write non-javascript interfaces for all of my control forms? Yes, provided that the JavaScript meets all of the WCAG 2 checkpoints. (e.g. keyboard access, no keyboard trap, text equivalents, etc.) Jonathan -----Original Message----- From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf Of Phil Evans Sent: Thursday, June 16, 2011 11:09 AM To: w3c-wai-ig@w3.org Subject: Javascript and WCAG 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 -- ------------------------- 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 pae9@star.le.ac.uk http://www.star.le.ac.uk/~pae9 http://www.swift.ac.uk Follow me as a Swift scientist on Twitter: @swift_phil http://www.star.le.ac.uk/~pae9/twitter
Received on Thursday, 16 June 2011 15:14:22 UTC