Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
{{ message }}
Update update.md #943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Update update.md #943
Changes from all commits
6e46bd76e1cb8bFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
{::nomarkdown} {% include box.html type="start" title="Summary" class="" %} {:/}
This page highlights some current work at the W3C Web Accessibility Initiative (WAI). It points out how you can contribute to making digital technology more accessible to people with disabilities.
{::nomarkdown} {% include box.html type="end" %} {:/}
{::nomarkdown} {% include toc.html type="start" title="Page Contents" %} {:/}
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
W3C Accessibility Guidelines (WCAG) 3 is in an exploratory phase, and will change substantially. It's years away from being finalized. Please see information on the latest draft and review questions in [WCAG 3 Introduction] [AG WG]
ARIA 1.3 — We're working on additional support for Braille and other new features for ARIA 1.3. [ARIA WG]
Developing New Standards
WAI-Adapt enables users to adapt (or ‘personalize’) how content is presented to meet their needs and preferences. [WAI-Adapt Overview] [APA WG, WAI-Adapt TF]
Spoken Presentation technical standards will enable screen readers and voice assistants to pronounce words correctly. [Pronunciation Overview] [APA WG, Spoken Presentation TF]
Documenting Additional Guidance for People with Cognitive Disabilities, Low Vision, and Mobile Devices
Updating Guidance on Applying WCAG to ICT and on EPUB Accessibility
WCAG2ICT describes how Web Content Accessibility Guidelines (WCAG) 2 can be applied to non-web information and communications technologies (ICT). We are updating it to include WCAG 2.1 and WCAG 2.2. [WCAG2ICT Overview] [AG WG, WCAG2ICT TF]
WCAG2ICT describes how Web Content Accessibility Guidelines (WCAG) 2 can be applied to non-web information and communications technologies (ICT). In October 2024 we published an update that includes all WCAG 2.2Level A and AA success criteria. We are now working on Level AAA success criteria. [WCAG2ICT Overview] [AG WG, WCAG2ICT TF]
EPUB Fixed Layout Accessibility aims to help publishers address challenges for people with cognitive disabilities and low vision. EPUB Fixed Layout Accessibility Editor's Draft [EPUB3 WG, FXL A11y TF]
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.
Natural Language Interface Accessibility User Requirements ("NAUR") is a Working Draft. A natural language interface is a user interface in which the user and the system communicate via a natural (human) language. The user provides input as sentences via speech or other input, and the system generates responses as sentences delivered by speech, text, or another modality. About NAUR, NAUR Editor's Draft [APA WG, Research TF]
Collaboration Tools Accessibility User Requirements ("CTAUR") is a Working Draft. It describes user needs in tools that provide support for one or more specific collaborative features. These features include real-time editing of content by multiple authors, the use of comments or annotations, and revision control. CTAUR Editor's Draft [APA WG, Research TF]
How People with Disabilities Use the Web helps you understand user needs broadly. We're updating this resource and publishing new videos to go along with it. [How People with Disabilities Use the Web - previous version], in-progress update of How People with Disabilities Use the Web
How People with Disabilities Use the Web helps you understand user needs broadly. We've updated this resource and published new videos to go along with it. We are making minor revisions to the user stories. [How People with Disabilities Use the Web].
Testing Accessibility, Evaluation Tools
Translating Resources
Existing translations of W3C accessibility resources are listed in All WAI
Transations. We are currently working with volunteer translators to translate more resources and update existing translations, including translations of WCAG and of educational resources. See Translating WAI resources.Upcoming Publications
We plan to publish the following documents in
2024.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 {#participate}
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 and
Korean.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.
{%- include_cached icon.html name="hp-book" class="mwa-icon mwa-icon-book" -%} W3C
The World Wide Web Consortium (W3C) develops international standards for the Web: HTML, CSS, and many more.
{%- include_cached icon.html name="hp-tools" class="mwa-icon" -%} WAI
The W3C Web Accessibility Initiative (WAI) develops standards and support materials to help you understand and implement accessibility.
{%- include_cached icon.html name="hp-computer" class="mwa-icon mwa-icon-computer" -%} You
You can use W3C WAI resources to make your websites, applications, and other digital creations more accessible and usable to everyone.
{% include_cached excol.html type="start" id="changelog" %}
Updates to this page (changelog)
{% include_cached excol.html type="middle" %}
commendation, Web Standard.mplementations and are ready to go from CR to PR.{% include_cached excol.html type="end" %}