Edit comment LC-2667 for Accessibility Guidelines Working Group

Previous: LC-2666 Next: LC-2659

Comment LC-2667: Comment Shortname:; Commenter: Duff Johnson <djohnson@commonlook.com>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Comment:
DOCUMENTS AND SOFTWARE – THE SAME RULES?

The WCAG2ICT attempts to apply WCAG 2.0 not only to non-web documents but also to “software aspects of products”. The notion that the same Success Criteria are usefully applicable across these domains is risible at best. Without substantial justification and development of the theoretical and practical underpinnings of this move, such a massive expansion of scope beyond web content can only reflect poorly on the organization making the attempt.

Does Tim know what you guys are doing?; Related issues: LC-2663
(space separated ids); WG Notes: Previous proposed resolution: With regard to the application beyond web content, see previous comments above. With regard to the application of the same rules across non-web documents and software we will be providing additional discussion to make this clearer. One thing is clear is that documents and software are rapidly converging. We expect that many books will contain complete interactive environments, experiments, and other things normally associated with software and games.; Proposed Resolution: The W3C did not initiate the concept of applying WCAG outside of Web Content. Rather it was the US Access Board who noted that the guidelines for electronic documents and software in the TEITAC report paralleled WCAG 2.0. The Access Board has proposed that WCAG 2.0 be used as the standard for non-web content and software in the Section 508 refresh process. Current drafts of European Mandate 376 (M376) standards are following the US lead. Through this task force, the W3C is developing a common understanding of how WCAG 2.0 might apply to non-web ICT for organizations and entities who are already seeking to so adopt and apply WCAG 2.0. By doing this we increase the likelihood that these applications of WCAG 2.0 will be consistent, and in keeping with the Principles, Guidelines, and Intent of WCAG 2.0. If you feel that WCAG 2.0 should not be used for non-web content and software, then we would suggest that you address your comments to the U.S. Access Board and EU M376 standards development team. Comments on the use WCAG 2.0 for non-web content and software, can be sent to the U.S. Access Board and/or submitted as part of the EU M376 review process.; (Please make sure the resolution is adapted for public consumption)