For Review: Inaccessibility of CAPTCHA Working Draft
Inaccessibility of CAPTCHA is being reviesd and updated. A Working Draft is available for review. Since the last publication, the abilities of robots to defeat CAPTCHAs has increased, and new technologies to authenticate human users have come available. This update brings the document up to date with these new realities. For more information, see the blog post?Updated and extensively revised “Inaccessibility of CAPTCHA” Published. Please submit any comments by 31 July 2018.
WCAG 2.1 is a Web Standard “W3C Recommendation”
Web Content Accessibility Guidelines WCAG 2.1 was published today as a “W3C Recommendation” web standard. All requirements (“success criteria”) from 2.0 are included in 2.1. There are additional success criteria in 2.1. They are introduced in What’s New in WCAG 2.1. For information about this publication and next steps, see the blog post WCAG 2.1 is a W3C Recommendation.
W3C WAI Website and Resources Redesigned
The redesigned W3C WAI website makes it easier to get information to help you improve web accessibility. The visual design, information architecture, navigation, and overall user experience is all new. Much of the content is revised, and we plan to revise more in the coming months. The redesign makes it easier to skim pages, read content, find specific information, and discover new resources. It’s also easier for the community to be involved in improving resources. Please see W3C WAI Website Redesign Information for:
- Planned Changes and Known Issues
- How to Comment
Candidate Recommendation: WAI-ARIA Graphics Module and Graphics Accessibility API Mappings
The ARIA WG has published WAI-ARIA Graphics Module 1.0 and Graphics Accessibility API Mappings 1.0. The Working Group targets 27 April 2018 to complete the testing process and produce the implementation report.
For Wide Review: Accessible Name and Description Computation
The ARIA WG has published a wide review draft of Accessible Name and Description Computation 1.1. This document describes how user agents determine the names and descriptions of accessible objects, where information comprising that name can come from various characteristics of the content, in order to lead to a consistent result across implementations. The document previously included Accessibility API Mappings, which have been moved to Core Accessibility API Mappings, so this document only describes the procedure to determine accessible name and description, not how to expose it. Please comment by 13 April 2018.
See All News