In-progress updates to the document may be viewed in the publicly visible editors' draft. If filing issues in GitHub is not feasible, send email to ( comment archive). It is free to create a GitHub account to file issues. Although the proposed Success Criteria in this document reference issues tracking discussion, the Working Group requests that public comments be filed as new issues, one issue per discrete comment. To comment, file an issue in the W3C WCAG GitHub repository. The Working Group plans to advance past Candidate Recommendation when the Candidate Recommendation Exit Criteria have been met. Two success criteria are marked as " at risk" due to concerns around implementation and testing challenges, andy they could revert to previous versions if testing does not document sufficient implementation. The change log summarizes changes since the previous Candidate Recommendation. This version integrates changes in response to comments received on the 25 January 2023 Candidate Recommendation. This is a third Candidate Recommendation of Web Content Accessibility Guidelines 2.2 (WCAG 2.2) from the Accessibility Guidelines Working Group. Publications and the latest revision of this technical report can be found This section describes the status of thisÄocument at the time of its publication. The W3C also encourages use of the most current version of WCAG when developing or updating Web accessibility policies. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 to maximize future applicability of accessibility efforts. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternate means of conformance. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. WCAG 2.2 extends Web Content Accessibility Guidelines 2.1, which was published as a W3C Recommendation June 2018. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. WCAG 2.2 success criteria are written as testable statements that are not technology-specific. Following these guidelines will also often make Web content more usable to users in general. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations but will not address every user need for people with these disabilities. Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. W3C Candidate Recommendation Draft More details about this document This version: Latest published version: Latest editor's draft: History: Commit history Implementation report: Latest Recommendation: Editors: Chuck Adams ( Oracle) 3.3.Web Content Accessibility Guidelines (WCAG) 2.2.1.2.7 Extended Audio Description (Prerecorded).1.2.3 Audio Description or Media Alternative (Prerecorded).1.2.1 Audio-only and Video-only (Prerecorded).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |