What We're Working On
Accessibility Activities and Publications, December 2024

Introduction

We hope you’ll find accessibility work on this page that you are interested in contributing to through W3C WAI. After each item is the acronym of the responsible Working Group (WG) and some Task Forces (TF). Information about the groups is later in this page — first, let’s look at some of the work itself.

Current Work Highlights

Updating Core Guidelines and Other Standards

Developing New Standards

Documenting Additional Guidance for People with Cognitive Disabilities, Low Vision, and Mobile Devices

Updating Guidance on Applying WCAG to ICT and on EPUB Accessibility

Defining User Requirements (AUR) and Exploring Emerging Technologies

Documenting the user needs of people with disabilities helps develop standards to meet those needs. It also helps designers, developers, and others better understand and meet user needs in order to support accessibility. XR Accessibility User Requirements and more listed at Digital Accessibility User Requirements.

Testing Accessibility, Evaluation Tools

Translating Resources

Existing translations of W3C accessibility resources are listed in All WAI Translations. We are currently working with volunteer translators to translate more resources and update existing translations, including translations of WCAG and of educational resources. See WCAG 2 Translations and Translating WAI resources.

Upcoming Publications

We plan to publish the following documents in 2024 or early 2025.

Recent publications and other announcements are listed on the News page.

Get Updated

To get news via e-mail, LinkedIn, Mastodon, or Atom/RSS feed when these and other accessibility documents are ready for review or published as final, see Get WAI News.

Wait, Wait, There’s More

This page only lists about half of the active work on accessibility at W3C. Much of the work happens in the accessibility groups that are introduced in the W3C Working Groups page.

To learn more about what the Working Groups are working on right now, see:

Surprise! We already have a resource for that

Did you know the WAI website has: videos, tips, tutorials, tools (for generating reports and accessibility statements), translations (over 35 languages), training (a free online course), and so much more. There are resources for content authors, designers, developers, evaluators, testers, managers, policy makers, trainers, educators, web users, advocates, and people with disabilities.

Discover accessibility resources that you didn’t even know existed from the annotated list of WAI Resources. When you find helpful information, would you share it with others.

How to Get Involved

To learn about contributing to W3C WAI accessibility work generally, see Participating in WAI.

Links to each Working Group’s “How to Participate” page are in the Participating in Working Groups section. If you are interested in a Task Force, see participation information for the parent Working Group.

We also offer ideas for Promoting and Implementing Web Accessibility.

Translations: If you might want to volunteer to contribute to translations, please see Translating WAI resources. You can send questions via e-mail to group-wai-translations@w3.org We are currently seeking translators in all languages and reviewers for draft translations in Czech, Greek, Indonesian, Korean, and Simplified Chinese.

We look forward to your contributions to making the web more accessible to people with disabilities!

Who is We

“We” is:

Making the Web Accessible

Strategies, standards, and supporting resources to help you make the Web more accessible to people with disabilities.

W3C

The World Wide Web Consortium (W3C) develops international standards for the Web: HTML, CSS, and many more.

WAI

The W3C Web Accessibility Initiative (WAI) develops standards and support materials to help you understand and implement accessibility.

You

You can use W3C WAI resources to make your websites, applications, and other digital creations more accessible and usable to everyone.

Updates to this page (changelog)

Back to Top