WCAG 3 Timeline

From WCAG WG

Overview

The Accessibility Guidelines Working Group intends to follow an agile approach for developing WCAG 3.0. Our goal is to work in a way that allows us to rapidly develop new concepts, to test those, gather feedback about them, and iterate on those concepts. This is done in a structured approach, such as through temporary subgroups, and by using status levels.

Priorities are decided, not years in advance, but as new concepts are developed and as feedback comes in. Our processes themselves are regularly evaluated and iterated on to optimize our ability to develop WCAG 3 into a high quality, future-proof, and equitable standard. In deciding priorities, the accessibility guidelines will ensure regular and open collaboration with stakeholders, including people with disabilities, industry, and the W3C Advisory Committee.

Publication Plan

Note: This plan is a living document and will be updated as needed.

Quarter Guidelines Conformance

2023 Q4

  • Work in subgroups to create initial outcomes for exploration
  • Create initial outcome format and standardize wording
  • Create criteria for guidelines and outcomes that will be worked on initially (example: research or self evident)
  • Begin Requirements Discussion
    • Resolve issues raised in Github
    • Address concerns raised in Conformance Challenges Document
  • Begin conversation on WCAG 3 core issues in GitHub
    • Publication Approach
    • Evaluating Proposed Conformance Models
2024 Q1
  • Organize and deduplicate outcomes list
  • Publish next exploratory guidelines, user needs and/or outcomes (Exactly what will be published TBD)
  • Select and prioritize outcomes for work based on selection criteria (Initial set)
  • Deep dive into a single outcome using writing testable outcomes process (Rewrite writing testable outcomes must be done first)
  • Conclude Requirements Discussion
  • Begin discussion of WCAG 3 core issues in meetings
    • Publication Approach
    • Evaluating Proposed Conformance Models
2024 Q2
  • Subgroups begin work on outcomes that meet selection criteria
  • Initial list of assertions for consideration
  • Discuss contributors list format
  • Continue discussion of WCAG 3 core issues in Github and meetings (topic TBD)
  • Discuss conformance models
2024 Q3
  • Subgroups continue work on initial outcomes
  • Retrospective (TPAC)
  • Publish updated exploratory conformance model(s) or options
  • Publish updated WCAG 3 Explainer (Including release plan)
  • Continue discussion of Core Issues
2024 Q4
  • Subgroups continue work on initial outcomes
  • Continue discussion of Core Issues
  • Review and address public comments (including Silver, WCAG3 and WCAG2.next)
2025 Q1
  • Publish initial developmental list of outcomes
  • Retrospective (CSUN)
  • Continue discussion of Core Issues
  • Review and address public comments
2025 Q2
  • Review and address public comments
  • Subgroups start work on additional outcomes
  • Continue discussion of Core Issues
  • Review and address public comments
2025 Q3
  • Review and address public comments
  • Subgroups start work on additional outcomes
  • Retrospective (TPAC)
  • Continue discussion of Core Issues
  • Review and address public comments
2025 Q4
  • Publish updated developing outcomes list
  • Subgroups start work on additional outcomes
  • Publish developing conformance model(s) or options
  • Publish updated WCAG 3 Explainer
  • Update this wiki with a data driven schedule for WCAG 3

Status

Decisions made on WCAG 3 at the exploratory and developmental stages help shape the direction we are moving in and may be revisited and changed as the group learns more. As we progress, changing directions will occur less frequently. Below is a list of the decisions made to date.

Retrospective

This space is the parking lot for discussions that we are postponing until the next retrospective.

Risk Register

  • Keeping pace with technology in the next few years
  • Cost and difficulty of conforming to two versions at once
  • Regulator adoption
  • Transition

Other Questions

  • What more we can do to alleviate concerns when publishing drafts while remaining transparent?