Re: Survey on Scheduling Approaches

Hello Detlev,

Each scope is defined in reference to WCAG 2.2.  I’ve added clarifications to each below. If those make more sense, I’ll add them to the document as well. If they do not make sense, please let me know what remains confusing so we can better make the document as clear as possible.

Thank you for writing to ask for clarification.

Kind regards,

Rachael

From: Detlev Fischer <detlev.fischer@testkreis.de>
Date: Sunday, June 29, 2025 at 4:28 AM
To: Bradley Montgomery, Rachael L <rmontgomery@loc.gov>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Survey on Scheduling Approaches

CAUTION: This email message has been received from an external source. Please use caution when opening attachments, or clicking on links.
Based on the comparison of scheduling options document, I don‘t understand the differences between approach 1-3 sufficiently to make an informed decision. All seem to use WCAG 2.2 AA (or equivalents) in some way as foundational, but there are differences in wording that I cannot suss out.

Incremental
„This approach would likely use WCAG 2.2 A&AA as foundational requirements until they are rewritten.“

This approach uses WCAG 2.2 A & AA Success Criteria, as is, until they are replaced by WCAG 3 requirements.  This is the only approach that creates a hybrid document with WCAG 3 referring back to WCAG 2 when needed.

WCAG2AA-Topical
„This approach sets the initial scope as comparable to WCAG 2.0 A & AA but assumes some flexibility to add high priority content.“

This approach uses WCAG 2.0 A & AA to scope the requirements that the group will focus on rewriting in an initial release. It includes some flexibility to include higher priority items, items from AAA that overlap with A & AA,  and related assertions.

WCAG2AA-Migration
„This approach sets the initial scope as comparable to WCAG 2.0 AA for a first publication, then adds in AAA and assertions later“

This approach uses WCAG 2.0 A & AA to scope the requirements that the group will focus on rewriting in an initial release but keeps the scope to strictly A & AA. It does not include related AAA or assertions.


I think it is about the vagueness of the terms „would likely use“, „until“, „initial scope“ „comparable to“, „some flexibility“, „then adds…later“ that makes it very difficult for me to form a distinct image of the first three different approaches. I honestly don‘t know how to answer this survey, and I hope this is just a personal comprehension problem.

Within what I wrote above:

  *   Initial scope = the scope of the initial fully published release based on the proposal.
  *   Comparable to and some flexibility = the group has some flexibility to expand the scope to related items.
  *   Strictly = we are following the scope exactly.
  *   Adds later references a future release. Releases for each option are outlined in the proposal document.


best, Detlev

Sent from phone


Am 27.06.2025 um 17:05 schrieb Bradley Montgomery, Rachael L <rmontgomery@loc.gov>:

Hello,

Chairs have pulled together the options for the scheduling approaches that were discussed on Tuesday and tried to add enough information to reduce some of the confusion that was occurring. Please take a few minutes to read through the details and answer this WCAG 3 Scheduling Approach Survey<https://urldefense.com/v3/__https:/www.w3.org/wbs/35422/wcag3_schedule_25/__;!!EDx7F7x-0XSOB8YS_BQ!Yu0Ha2bX-PMh6jtKFsamGsXEfPNo9oVmGxCdG4UDS7XrrfBrgIH-GobZY1v0oSYJmr-buqcTfrMs34xhUPeoKtWWhL_KuWTW$> before next Friday.

Chairs will consider the results and use them to draft the charter for the group to consider and discuss.

Kind regards,

Rachael