Current Work

(updated monthly)

SeeWhat We're Working On – Accessibility Activities and Publications

Digital Publishing WAI-ARIA Module 1.1 (DPUB-ARIA) andDigital 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, seeWAI-ARIA Overview.

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.

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

The changes are listed in theChange Log section of WCAG 2.1.

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 theW3C Authorized Translations process.

Other translations of WAI resources are listed inAll WAI Translations.

WAI thanks all who contribute to translations, and encourages translations of W3C accessibility standards and resources in all languages. If you might be interested in translating resources, seeTranslating WAI Resources.

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 theW3C Authorized Translations process.

Other translations of WAI resources are listed inAll WAI Translations.

WAI thanks all who contribute to translations, and encourages translations of W3C accessibility standards and resources in all languages. If you might be interested in translating resources, seeTranslating WAI Resources.

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 theARRM 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.

• Getting Started
• Content Writers
• Designers
• Developers
• Evaluators, Testers
• Managers
• Policy Makers
• Trainers, Educators
• Web Users, People with Disabilities, Advocates
• Everyone (All WAI Resources)
• Other Languages

Captions are the audio information in text that is synchronized with the audio and visual content. Captions are called "subtitles" in some regions.

Video Captions are essential for people with disabilities and benefit everyone in a variety of situations.