Re: CFC - Update WCAG 3 Working Draft

+1 under the assumption that the pre-cfc email “didn’t” raise additional concerns, which I assume was a typo.

Best regards,

Mary Jo Mueller
IBM Accessibility Standards Program Manager


From: Bradley Montgomery, Rachael L <rmontgomery@loc.gov>
Date: Monday, July 17, 2023 at 1:41 PM
To: WCAG <w3c-wai-gl@w3.org>, Silver TF <public-silver@w3.org>
Subject: [EXTERNAL] CFC - Update WCAG 3 Working Draft
Call For Consensus — ends Thursday July 21st at 2pm Boston time. We previously agreed update the WCAG 3 Working Draft from the Editor's Draft Our pre-cfc email did raise any additional concerns. The next step (in a future CFC) will be to agree
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
    Report Suspicious  <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!1a-vTt5zRvmblYv7-IHljtcGZuZhWYs_FljqdtFWDhHEHmbNC1KJWbBNtr1AQ2xGQjWnl6H091W9ezYoaQRp5pHIyhjZxzlfYDfHWV5t74JzMFdsJCJmQXLjTmaGJF2mfcu1P54DkacFxg$>   ‌
ZjQcmQRYFpfptBannerEnd

Call For Consensus — ends Thursday July 21st at 2pm Boston time.



We previously agreed update the WCAG 3 Working Draft from the Editor's Draft<https://w3c.github.io/silver/guidelines/>



Our pre-cfc email did raise any additional concerns.




The next step (in a future CFC) will be to agree the re-publishing of WCAG 2.1 & 2.0 in order that these notes (and all the previous errata) are visible in the latest versions of each.



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 live with” this decision, please let the group know before the CfC deadline.



Kind regards,



-Alastair