- From: Avneesh Singh <avneesh.sg@gmail.com>
- Date: Mon, 5 Feb 2018 19:16:49 +0530
- To: "PubWG" <public-publ-wg@w3.org>
For information of the group, WCAG 2.1 has entered CR stage. PWG accessibility TF collaborated with AG for machine readable accessibility metadata. With regards Avneesh -----Original Message----- From: Xueyuan Sent: Tuesday, January 30, 2018 17:10 To: w3c-ac-forum@w3.org Cc: chairs@w3.org Subject: Web Content Accessibility Guidelines (WCAG) 2.1 is a W3C Candidate Recommendation (Call for Implementations) Dear Advisory Committee Representative, Chairs, I am pleased to announce that Web Content Accessibility Guidelines (WCAG) 2.1 is a W3C Candidate Recommendation: https://www.w3.org/TR/2018/CR-WCAG21-20180130/ The approval and publication are in response to this transition request: https://lists.w3.org/Archives/Member/chairs/2018JanMar/0035.html Please provide feedback by 30 March 2018 as follows: File issues at https://github.com/w3c/wcag21/issues/new or send email to public-agwg-comments@w3.org. The Accessibility Guidelines Working Group especially invites feedback from the following groups with dependencies: Accessible Platform Architectures Working Group ARIA Working Group Cascading Style Sheets Working Group Publishing Working Group Education and Outreach Working Group Internationalization Activity WAI Interest Group Web Platform Working Group Some objections were raised in the Working Group on proceeding to Candidate Recommendation with this version, as these guidelines did not adopt as many as hoped of the Success Criteria proposed for persons with cognitive and learning disabilities. In accepting the Group Chairs' conclusion to proceed while acknowledging those objections, the Director concurs that the material in the CR is a useful incremental improvement in accessibility for the areas that have been addressed. The Chairs and Team will work with the Group during the Candidate Recommendation period to clarify the claims made in the abstract and will continue to work with the Group and stakeholder communities to advance additional Success Criteria on the Recommendation Track in subsequent versions of the standard. Patent disclosures relevant to this specification may be found on the Accessibility Guidelines Working Group's patent disclosure page in conformance with W3C policy: https://www.w3.org/2004/01/pp-impl/35422/status This Call for Implementations follows section 6.4 "Candidate Recommendation" of the W3C Process Document: https://www.w3.org/2017/Process-20170301/#candidate-rec Thank you, For Tim Berners-Lee, Director, and Philippe Le Hégaret, Project Management Lead; Xueyuan Jia, W3C Marketing & Communications ============================================== Quoting from Web Content Accessibility Guidelines (WCAG) 2.1 W3C Candidate Recommendation 30 January 2018 This Version: https://www.w3.org/TR/2018/CR-WCAG21-20180130/ Latest Published Version: https://www.w3.org/TR/WCAG21/ Abstract: Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make your Web content more usable to users in general. WCAG 2.1 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [WCAG20], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0, and therefore to policies that reference WCAG 2.0. Until WCAG 2.1 advances to W3C Recommendation, the current and referenceable document is Web Content Accessibility Guidelines 2.0 [WCAG20], published as a W3C Recommendation December 2008. Editor's note The introduction to WCAG 2.0 says "even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive, language, and learning areas." While WCAG 2.1 provides additional guidance, it is still true that it does not provide universal coverage. The Working Group plans to add additional clarification about this in the next publication. Status of This document: This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/. This is a Candidate Recommendation of Web Content Accessibility Guidelines 2.1 (WCAG 2.1) from the Accessibility Guidelines Working Group. This version integrates some changes in response to comments received on the 7 December 2017 Working Draft and earlier drafts. Some Success Criteria are marked as "at risk" due to concerns around implementation and testing challenges, and could be removed if testing does not document sufficient implementation. The Working Group plans to advance past Candidate Recommendation when the Candidate Recommendation Exit Criteria have been met. Publication as a Candidate Recommendation indicates that the AG WG believes it has addressed sufficient substantive issues and that the document is ready for trial implementations. The first public Working Draft of WCAG 2.1 was published 28 February 2017. Since then, the AG WG has published six additional Working Drafts, addressed more than 500 issues, and developed support information for the guidelines while adhering to a strict timeline. See How WAI Develops Accessibility Guidelines through the W3C Process for more background on document maturity levels. To comment, file an issue in the W3C WCAG 2.1 GitHub repository. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org (comment archive). Comments are requested by 30 March 2018. In-progress updates to the document may be viewed in the publicly visible editors' draft. This document was published by the Accessibility Guidelines Working Group as a Candidate Recommendation. This document is intended to become a W3C Recommendation. Comments regarding this document are welcome. Please send them to public-comments-wcag20@w3.org (subscribe, archives). W3C publishes a Candidate Recommendation to indicate that the document is believed to be stable and to encourage implementation by the developer community. This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 30 March 2018. Please see the Working Group's implementation report. Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. This document is governed by the 1 March 2017 W3C Process Document. ==============================================
Received on Monday, 5 February 2018 13:48:09 UTC