Skip to content

Commit

Permalink
Merge pull request #1002 from w3c/iadawn-wcag3-nov-2024
Browse files Browse the repository at this point in the history 
Update to WCAG 3 intro
  • Loading branch information
@shawna-slh
shawna-slh authored Dec 12, 2024
2 parents a429b3f + c167ec2 commit 56966f4
Showing 1 changed file with 63 additions and 85 deletions.
148 changes: 63 additions & 85 deletions pages/standards-guidelines/wcag/wcag3-intro.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -38,11 +38,11 @@ footer: >
{% include box.html type="start" h="2" title="Summary" class="full" %}
{:/}

Many aspects of W3C Accessibility Guidelines (WCAG) 3 are in an exploratory phase, and will change. We published an updated [WCAG 3 Working Draft](https://www.w3.org/TR/wcag-3.0/) on 16 May 2024.
Many aspects of W3C Accessibility Guidelines (WCAG) 3 are in an exploratory phase, and will change substantially. We published an updated [WCAG 3 Working Draft](https://www.w3.org/TR/wcag-3.0/) on 12 December 2024.

WCAG 3 will have similar fundamental and specific accessibility requirements as WCAG 2. WCAG 3 will have a different structure, different conformance model, and broader scope.

Please share this page as the starting point for official information about WCAG 3 now and in the future. short link: w3.org/WAI/wcag3
Please share this page as the starting point for official information about WCAG 3 now and in the future. Short link: w3.org/WAI/wcag3

{::nomarkdown}
{% include box.html type="end" %}
Expand All @@ -64,64 +64,63 @@ Please share this page as the starting point for official information about WCAG
## Introduction
{:.no_toc}

WCAG 3 is currently an incomplete draft. WCAG 3 is intended to develop into a W3C Standard **in a few years**. The current standard, Web Content Accessibility Guidelines (WCAG 2), is introduced in the [WCAG 2 Overview](/standards-guidelines/wcag/).
W3C Accessibility Guidelines (WCAG) 3 is currently an incomplete draft. WCAG 3 is intended to develop into a W3C Standard **in a few years**. The current standard, Web Content Accessibility Guidelines (WCAG 2), is introduced in the [WCAG 2 Overview](/standards-guidelines/wcag/).

The WCAG 3 documents will explain how to make the web more accessible to people with disabilities. WCAG 3 applies to web content, apps, tools, publishing, and emerging technologies on the web.

We will update this page regularly as work on the WCAG 3 Draft progresses.

## Status: Exploratory Draft
## Status: In-progress drafts

The May 2024 [WCAG 3 Working Draft](https://www.w3.org/TR/wcag-3.0/) includes **potential** outcomes that we are exploring. The final set of outcomes in WCAG 3 will be different from this draft. Outcomes will be edited, added, combined, and removed.
In December 2024, we published updated drafts:

The purpose of this draft is to:
* better understand the scope of user needs and how they could be addressed in an accessibility standard,
* request assistance in identifying gaps, and
* request assistance locating and conducting research to validate or invalidate the drafted outcomes.
* [Requirements for WCAG 3](https://www.w3.org/TR/wcag-3.0-requirements/) describes the key principles and requirements that will help shape how WCAG 3 develops and how to determine when it is successfully complete.
* **[Explainer for WCAG 3](https://www.w3.org/TR/wcag-3.0-explainer/)** provides background information and describes the structure of the December 2024 WCAG 3 Draft. **We suggest reading the Explainer before reading WCAG 3.**
* **[WCAG 3 Working Draft](https://www.w3.org/TR/wcag-3.0/)** includes potential guidelines and requirements that we are exploring. The final requirements in WCAG 3 will be different from this draft. Guidelines and requirements will be edited, added, combined, and removed.

Some of the outcomes are marked as needing research. We are particularly interested in assistance identifying or conducting research to support or refute them.
### Summary of changes
* Explanatory content is moved to the [Explainer](https://www.w3.org/TR/wcag-3.0-explainer/).
* The term 'outcome' is changed. The current draft has 'guidelines' that are written as user-centered outcomes and 'requirements' that support the guideline.
* Requirements are indicated as 'foundational' or 'supplemental', as described in the [Explainer](https://www.w3.org/TR/wcag-3.0-explainer/).
* Accessibility support is changed in [3.1.1 Only accessibility-supported ways of using technologies](https://www.w3.org/TR/2024/WD-wcag-3.0-20241212/#accessibility-supported).

### For your review

When reviewing this update, please focus on the Guidelines section. We did not make changes to conformance related sections.
### Section status
Each normative section has a status that indicates how far along in the development process this section is, how ready it is for experimental adoption, and what kind of feedback we are looking for.
* Placeholder
* Exploratory
* Developing
* Refining
* Mature

Please consider the following questions when reviewing the outcomes in this draft:
* What outcomes needed to make web content accessible are missing?
* What research supports or refutes these outcomes?
* Are any of these outcomes out of scope for accessibility standards? If so, please explain why.
For more information on these status indicators, see the Explainer section [Current Process for Creating WCAG 3.0](https://www.w3.org/TR/2024/DNOTE-wcag-3.0-explainer-20241212/#current-process).

To provide input, please file GitHub issues at: [https://github.com/w3c/wcag3/issues](https://github.com/w3c/wcag3/issues)<br>
Or, if you are unable to use GitHub, send email to [email protected]
### For your review

Please create separate GitHub issues or email messages for each topic (rather than putting multiple topics in a single issue or email).
In this WCAG 3 Working Draft, there are four updated sections that we would particularly like feedback on. The first three sections are guidelines:

### Status of Sections
1. [Image alternatives guideline](https://w3.org/TR/wcag-3.0/#image-alternatives)
2. [Keyboard focus appearance guideline](https://w3.org/TR/wcag-3.0/#keyboard-focus-appearance)
3. [Clear meaning guideline](https://w3.org/TR/wcag-3.0/#clear-meaning)

Each normative section has a status that indicates how far along in the development process this section is, how ready it is for experimental adoption, and what kind of feedback we are looking for.
For these sections, does the information under 'Which foundational requirements apply?' make the guidelines easier to understand and use?

* **Placeholder:** This content is temporary. It shows the type of content or section to expect. Placeholder text will be replaced. It is hidden by default in the Editor's draft. No feedback is needed on placeholder content.
* **Exploratory:** The Working Group is exploring what direction to take with this section. This content is not refined; details and definitions may be missing. It is hidden by default in the Editor's draft. We invite feedback on the proposed direction.
* **Developing:** There is rough agreement on what is needed for this section, although not all high-level concerns have been settled. Details are included, yet they are not all agreed on. We invite general feedback on how understandable, usable, and reasonable the section is generally.
* **Refining:** The Working Group has reach consensus on this section. It is ready for broad public review and experimental adoption. We seek feedback on feasibility and issues with implementations.
* **Mature:** The Working Group thinks this content is ready for the final standard. Feedback should be focused on edge case scenarios the Working Group might not have anticipated.
The other section we would like feedback on is:

<img src="{{ "/content-images/wcag/dialogs2.svg" | relative_url }}" alt="" style="float: right; margin-left: 2rem; width: 30%; max-width: 220px">
4. [Conformance](https://w3.org/TR/wcag-3.0/#conformance)

**There are substantial open issues that are still being discussed, particularly about testing and conformance.**
This section explains the conformance approach we are considering for WCAG 3. There are still many details to be worked out. Do you have constructive comments about this proposed conformance approach for WCAG 3?

<!--
### Review and Comments
### Research needed

We welcome input from evaluators, developers, designers, project managers, policy makers, people with disabilities, and others.
Some of the guidelines and requirements are marked with "Needs additional research". We are particularly interested in assistance identifying or conducting research to support or refute them.

We also welcome comments on the goals and parameters in [Requirements for WCAG 3.0](https://www.w3.org/TR/wcag-3.0-requirements/).
<img src="{{ "/content-images/wcag/dialogs2.svg" | relative_url }}" alt="" style="float: right; margin-left: 2rem; width: 30%; max-width: 220px">

The best way to provide this feedback is by opening new [GitHub issues](https://github.com/w3c/wcag3/issues/new). Alternatively, e-mail [email protected]
### Comments

Please put each topic in a separate GitHub issue or e-mail.
To provide input, please [open an issue in the WCAG 3 GitHub repository](https://github.com/w3c/wcag3/issues/new). Or, if you are unable to use GitHub, email [[email protected]](mailto:[email protected]).

Additionally, we welcome comments on ways that the Accessibility Guidelines Working Group can better support your review, feedback, and inclusion in the process of creating WCAG 3. Please e-mail these to [email protected]
-->
**Please create separate GitHub issues or email messages for each topic**, rather than putting multiple topics in a single issue or email.

## WCAG 3 Draft Approach

Expand All @@ -143,74 +142,53 @@ WCAG 3 is very **different** from previous versions in some ways. It has:
* different conformance model
* broader scope, beyond just web content

### WCAG 3 Name

The name of WCAG 3 is different from WCAG 2:
* WCAG **3** is W3C Accessibility Guidelines
* WCAG **2** is Web Content Accessibility Guidelines

“W3C Accessibility Guidelines (WCAG) 3.0” was chosen:
* because of wide-spread familiarity with the “WCAG” acronym
* to encompass the broader scope beyond “content”

### Structure

This WCAG 3 draft has:
* **Guidelines**
* Solutions to accessibility problems
* More **granular** than the guidelines in WCAG 2
* Each guideline has outcomes
* **Outcomes**
* Verifiable statements
* Similar to **success criteria** in WCAG 2
* More granular and more focused on the desired results than the technical means for achieving them<br>(More _granular_ means they are more specific, instead of broad. That generally makes them simpler. It also means there will be more of WCAG 3 outcomes than WCAG 2 success criteria.)
* **Assertions**
* Formal claim of fact, attributed to a person or organization
* Assertions in WCAG 3 state that an organization has completed a procedure that can improve accessibility
* Example procedures include usability testing, assistive technology testing, and plain language reviews
* Assertions are used when the results of the same usability would be very different between testers

<!-- @@ ??? SLH needs more clarity -->

WCAG 3 supporting material includes:
* **Methods**
* Technology-specific ways to achieve an outcome
* Tests for the outcome
* Similar to **Techniques** for WCAG 2
* **How-To documents**
* Explain more about each guideline, such as how it addresses accessibility needs <!-- @@ each outcome or each guideline ? -->
* Information for designers, developers, people new to accessibility, and project planners
* Similar to the **Understanding** documents for WCAG 2
* **Functional categories** of **functional needs**
* Categorized list of needs of people with disabilities

### Draft Conformance Model {#model}

The _conformance model_ is the way to determine and communicate how well a website (or app, tool, etc.) meets WCAG. The conformance model in this draft of WCAG 3 will be very different from WCAG 2. It is intended to:
For a description of the structure of the December 2024 WCAG 3 Working Draft, see the Explainer section [WCAG 3.0 Structure](https://www.w3.org/TR/2024/DNOTE-wcag-3.0-explainer-20241212/#structure).

### Conformance approach {#model}

The _conformance model_ is the way to determine and communicate how well content, a website, an app, etc. meets WCAG.

The conformance model in WCAG 3 will be very different from WCAG 2. It is intended to:
* be more flexible for organizations (that is, owners and developers of websites, apps, tools, etc.)
* encourage more accessible user experiences

We are reworking the conformance model based on feedback and we encourage additional feedback as we iterate.
Developing and vetting the conformance model is a large portion of the work AG needs to complete over the next few years.

The December 2024 publications have updated information in:
* Explainer section [Conformance approach](https://www.w3.org/TR/2024/DNOTE-wcag-3.0-explainer-20241212/#conformance-models)
* WCAG 3 Working Draft section [Conformance](https://www.w3.org/TR/2024/WD-wcag-3.0-20241212/#conformance)

## Development

### Timeline

<img src="{{ "/content-images/wcag/calandara.svg" | relative_url }}" alt="" style="float: right; margin-left: 2rem; width: 20%; max-width: 111px">

The First Public Working Draft of WCAG 3.0 was published on 21 January 2021. The July 2023 draft has many changes that resulted from public feedback. We plan to publish updated drafts every 3-6 months.
**WCAG 3 is not expected to be a completed W3C standard for a few more years.**

**WCAG 3 is not expected to be a completed W3C standard for a few more years.**
WCAG 3 will not supersede WCAG 2 and WCAG 2 will not be deprecated for at least several years after WCAG 3 is finalized.

The Working Group will focus on creating an initial set of guidelines and outcomes. Then will focus on refining the structure and conformance model. They will provide updated drafts for review throughout this process. Once the conformance approach is more stable, the Group will focus on refining the accessibility requirements (guidelines, outcomes, assertions, and support material). We will then provide material to help those wanting to transition to WCAG 3; for example, mapping between WCAG 2 and 3 requirements.
The Accessibility Guidelines Working Group (AG WG) has created an initial set of guidelines. In the first part of 2025, AG WG will focus on developing two or three guidelines to Refining or Mature status. We will use that experience to develop a projected timeline for WCAG 3. We expect the timeline to be available by September 2025.

WCAG 3 will not supersede WCAG 2, and WCAG 2 will not be deprecated, for at least several years after WCAG 3 is finalized.
For information on current timelines and activities, see [WCAG 3 Publication Plan](https://www.w3.org/WAI/GL/wiki/WCAG_3_Timeline#Publication_Plan).

We will update this section with more specific timeline information as it is available.

### WCAG 3 Name (formerly "Silver" project)

The name of WCAG 3 is different from WCAG 2:
* WCAG **3** is W3C Accessibility Guidelines
* WCAG **2** is Web Content Accessibility Guidelines

“W3C Accessibility Guidelines (WCAG) 3.0” was chosen:
* because of wide-spread familiarity with the “WCAG” acronym
* to encompass the broader scope beyond “content”

### Who Develops WCAG 3

The WCAG technical documents are developed by the Accessibility Guidelines Working Group ([AG WG](https://www.w3.org/WAI/GL/)) (previously under the Silver Task Force) with the Silver Community Group. These Groups are part of the World Wide Web Consortium ([W3C](https://www.w3.org)) Web Accessibility Initiative ([WAI](https://www.w3.org/WAI/)). You can learn about the development process from [[How WAI Develops Accessibility Standards through the W3C Process: Milestones and Opportunities to Contribute]](/standards-guidelines/w3c-process/).
The WCAG technical documents are developed by the Accessibility Guidelines Working Group ([AG WG](https://www.w3.org/WAI/about/groups/agwg/)) (previously under the Silver Task Force) with the Silver Community Group. These Groups are part of the World Wide Web Consortium ([W3C](https://www.w3.org)) Web Accessibility Initiative ([WAI](https://www.w3.org/WAI/)). You can learn about the development process from [[How WAI Develops Accessibility Standards through the W3C Process: Milestones and Opportunities to Contribute]](/standards-guidelines/w3c-process/).

We welcome your comments on WCAG 3 Working Drafts. The best way to provide feedback is by opening new [GitHub issues](https://github.com/w3c/wcag3/issues). Alternatively, e-mail [email protected]

Expand Down

0 comments on commit 56966f4

Please sign in to comment.