Shawn Lawton Henry (Director, Web Accessibility Initiative (WAI)) and Kevin White (Senior Principal Accessibility Specialist) led an interactive session at the AccessU 2025 training conference. Learn about WAI resources to help promote that accessibility is about improving the user experiences of people with disabilities, and to support you in planning, managing, designing, developing, and training for digital accessibility. The Q&A includes the WCAG 3 approach and timeline (years away). Find out how you can contribute to W3C accessibility work. See the recording of Advancing Digital Accessibility with W3C WAI.

Digital Publishing WAI-ARIA Module 1.1 (DPUB-ARIA) and Digital Publishing Accessibility API Mappings 1.1 (DPUB-AAM) are now web standards (W3C Recommendations). DPUB-ARIA defines a set of ARIA roles to help assistive technology users navigate structural divisions of long-form digital documents, such as eBooks. DPUB-AAM defines how user agents (such as eBook readers) map the DPUB-ARIA markup to platform accessibility APIs. For an introduction to WAI-ARIA, see WAI-ARIA Overview.

W3C published an update that addresses minor technical issues in the December 2024 publication of WCAG 2.1. The 6 May 2025 publication is Web Content Accessibility Guidelines (WCAG) 2.1.

Guidance on Applying WCAG 2.2 to Mobile Applications is available as a first Draft Note. WCAG2Mobile describes how Web Content Accessibility Guidelines (WCAG) 2.2 principles, guidelines, and success criteria can be applied to mobile applications, including native mobile apps, mobile web apps, and hybrid apps using web components inside native mobile apps. We welcome your comments on the direction and approach of this in-progress resource. To comment via email or GitHub, see links in the ‘Status of This Document’ section.

Diretrizes de Acessibilidade para Conteúdo Web (WCAG) 2.2, the Brazilian Portuguese Authorized Translation of Web Content Accessibility Guidelines 2.2 (WCAG), is now available. This translation followed the W3C Authorized Translations process.

Règles pour l’accessibilité des contenus Web (WCAG) 2.2, the French authorized translation of Web Content Accessibility Guidelines 2.2 (WCAG), is now available. This translation followed the W3C Authorized Translations process.

Accessibility Roles and Responsibilities Mapping (ARRM) is ready for review. ARRM helps your team create more accessible digital products and services. ARRM provides an approach for defining roles, tasks, and responsibilities for meeting Web Content Accessibility Guidelines (WCAG). If you would like to be involved in developing ARRM, we encourage you to join the ARRM Community Group.

Collaboration Tools Accessibility User Requirements is a completed W3C Group Note. The document covers accessibility user needs, requirements, and scenarios for collaborative content creation and development tools. The solutions identified in this document are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are also relevant to software developers who contribute to developing the collaborative experience.

The W3C Accessibility Guidelines Working Group (AG WG) is addressing open issues on Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2. Most issue resolutions resulted in updates to Understanding WCAG and Techniques for WCAG. Some resulted in minor editorial updates to the WCAG standard. Today W3C published updates to: Web Content Accessibility Guidelines (WCAG) 2.1 and Web Content Accessibility Guidelines (WCAG) 2.2. For a list of updates, see the Change Log section of each document. Please share this web page as the place to start for up-to-date information on WCAG 2: WCAG 2 Overview.

An updated W3C Accessibility Guidelines (WCAG) 3.0 Working Draft is available for review. For a summary of changes, new content for review, and how to comment, see the WCAG 3 Introduction section Status: In-progress drafts.