RE: CFC - WCAG3 working draft publication

+1 to releasing as a public working draft. The conformance model issue does need greater attention to ensure we have a better defined way forward, as this will likely also need a lot of public scrutiny to ensure it is workable.
Best regards,

Mary Jo Mueller
IBM Accessibility Standards Program Manager

From: Sydney Coleman <sydneycoleman@google.com>
Date: Wednesday, February 25, 2026 at 2:08 PM
To: Illai Zeevi <illai.zeevi@evinced.com>
Cc: Andrew Kirkpatrick <andrew.kirkpatrick@evinced.com>, Alastair Campbell <alastair.campbell@thisisgain.com>, WCAG list <w3c-wai-gl@w3.org>
Subject: [EXTERNAL] Re: CFC - WCAG3 working draft publication

This Message Is From an External Sender
This message came from outside your organization.
Report Suspicious<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/AdhS1Rd-!-XFVHHiccmM1mxwxZInLnJe5WS4zFeVTje9TTisUNvS9L7lW0A8P6BKsE_3VGUxJWvEVgBEznyY55-AXGTuoZUezy4h6gZQLFWIeoDB7xqiN7E6BQpT-JnRWfO0$>

+1 to releasing the working draft for public review and reiterating Google's concerns, which I've shared in the doc, with regards to the conformance model proposals. We are most supportive of Alistair's comfornace model with serious adjustments and I've outlined our pros/cons to each approach after consulting accessibility experts across Google. I'm hopeful that this feedback will be addressed in a future call.


Sydney Coleman (she/her)

Products For All



On Wed, Feb 25, 2026 at 10:37 AM Illai Zeevi <illai.zeevi@evinced.com<mailto:illai.zeevi@evinced.com>> wrote:
+1
However I also agree with Andrew's comments..

Illai

On Wed, Feb 25, 2026 at 8:31 PM Andrew Kirkpatrick <andrew.kirkpatrick@evinced.com<mailto:andrew.kirkpatrick@evinced.com>> wrote:
+1 to releasing the working draft for public review, which is always a good idea.

Concerns about the conformance model previously stated around the upcoming charter review continue, as an “exploratory” conformance model doesn’t meet the current charter’s "define a working conformance model for WCAG 3” expectation. I’m happy that we continue to work on this important area, but want to highlight that this is a critical area where we are not completely on schedule.

Andrew

From: Alastair Campbell <alastair.campbell@thisisgain.com<mailto:alastair.campbell@thisisgain.com>>
Date: Thursday, February 19, 2026 at 17:10
To: WCAG list <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: CFC - WCAG3 working draft publication

Call For Consensus — ends 25th Feb 2026 at 5pm Boston time.

The update is to publish the latest draft of WCAG3:
https://w3c.github.io/wcag3/guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_wcag3_guidelines_&d=DwMFaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=t4UaBDErgDQlbvgEC7uvTbuxrN92SQM9v-AOWhx_Ruk&m=ukJHyvWfiCONHqBnXDy5n_BQwyu8zpU8ZS22SCKCTP3c6xtfpOm1zcf-Oy7pBuKf&s=3GmicUnZ-X3Craqtpd51pCVONRkTEPpky9w8_PrXDNk&e=>

There is a “diff” of the changes, however, a lot has changed, it is mostly useful for seeing what hasn’t changed:
https://services.w3.org/htmldiff?doc1=https://www.w3.org/TR/wcag-3.0/&doc2=https://w3c.github.io/wcag3/guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__services.w3.org_htmldiff-3Fdoc1-3Dhttps-3A__www.w3.org_TR_wcag-2D3.0_-26doc2-3Dhttps-3A__w3c.github.io_wcag3_guidelines_&d=DwMFaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=t4UaBDErgDQlbvgEC7uvTbuxrN92SQM9v-AOWhx_Ruk&m=ukJHyvWfiCONHqBnXDy5n_BQwyu8zpU8ZS22SCKCTP3c6xtfpOm1zcf-Oy7pBuKf&s=6K2F1pDPkY33U22im2-qpFStmwgYwltgxW6z3PyoUWk&e=>

Please note that any provisions marked “exploratory” will be stripped from the published version.

We have previously surveyed for blockers (https://www.w3.org/wbs/35422/wcag3-developing-review/results/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_wbs_35422_wcag3-2Ddeveloping-2Dreview_results_&d=DwMFaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=t4UaBDErgDQlbvgEC7uvTbuxrN92SQM9v-AOWhx_Ruk&m=ukJHyvWfiCONHqBnXDy5n_BQwyu8zpU8ZS22SCKCTP3c6xtfpOm1zcf-Oy7pBuKf&s=Gfm8Pa8JtgNBYCh6MuZdCdqYrNo3ylt3RSg1kr5MeeY&e=>) and run a pre-CFC call. Changes since then have included:

  *
Adding a line in the intro about the stage of development.
  *
Adding some definitions and ensuring unused ones are not included (although some still appear in the editor’s draft as they are exploratory).


To support the CFC please reply to the group with a “+1”.

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you not being able to accept this decision, please reply with a “-1” and explanation before the CfC deadline.


Kind regards,



-Alastair



--



Alastair Campbell

Accessibility

E: alastair.campbell@thisisgain.com<mailto:alastair.campbell@thisisgain.com>

[cid:ii_19c96142de84cff311]<https://urldefense.proofpoint.com/v2/url?u=https-3A__thisisgain.com_&d=DwMFaQ&c=BSDicqBQBDjDI9RkVyTcHQ&r=t4UaBDErgDQlbvgEC7uvTbuxrN92SQM9v-AOWhx_Ruk&m=ukJHyvWfiCONHqBnXDy5n_BQwyu8zpU8ZS22SCKCTP3c6xtfpOm1zcf-Oy7pBuKf&s=BQOBuFTtgeYvKwIrPm22cB4kxTmux6VfHcVbbm5bav8&e=>