- From: Christopher Loiselle <chris.loiselle@oracle.com>
- Date: Thu, 3 Jun 2021 15:05:56 +0000
- To: Jonathan Avila <jon.avila@levelaccess.com>, "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <BN0PR10MB5287E0D69A2E39FB4C5CC633F73C9@BN0PR10MB5287.namprd10.prod.outlook.com>
I have reviewed the draft of changes , I have no objections regarding the CfC. From: Christopher Loiselle Sent: Thursday, June 3, 2021 10:30 AM To: Jonathan Avila <jon.avila@levelaccess.com>; WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org> Subject: RE: CFC - WCAG 3.0 Heartbeat publication I agree with Jonathan regarding terminology used. If it is working draft, call it that to simplify. Is heartbeat defined as a glossary term internally or externally? Status of document reads as editor’s draft currently per https://w3c.github.io/silver/guidelines/ . Working Groups<https://www.w3.org/2020/Process-20200915/#GroupsWG> and Interest Groups<https://www.w3.org/2020/Process-20200915/#GroupsIG> may make available Editor’s drafts<https://www.w3.org/2020/Process-20200915/#editors-draft>. Editor’s drafts (ED) have no official standing whatsoever, and do not necessarily imply consensus of a Working Group<https://www.w3.org/2020/Process-20200915/#GroupsWG> or Interest Group<https://www.w3.org/2020/Process-20200915/#GroupsIG>, nor are their contents endorsed in any way by W3C. 6.2.1. Maturity Levels on the Recommendation Track Working Draft (WD) A Working Draft is a document that W3C has published<https://www.w3.org/2020/Process-20200915/#publishing> on the W3C’s Technical Reports page<https://www.w3.org/TR/> [TR]<https://www.w3.org/2020/Process-20200915/#biblio-tr> for review by the community (including W3C Members), the public, and other technical organizations, and for simple historical reference. Some, but not all, Working Drafts are meant to advance to Recommendation<https://www.w3.org/2020/Process-20200915/#RecsW3C>; see the document status section<https://www.w3.org/2020/Process-20200915/#DocumentStatus> of a Working Draft for the group’s expectations. Working Drafts<https://www.w3.org/2020/Process-20200915/#RecsWD> do not necessarily represent a consensus<https://www.w3.org/2020/Process-20200915/#def-Consensus> of the Working Group<https://www.w3.org/2020/Process-20200915/#GroupsWG> with respect to their content, and do not imply any endorsement by W3C or its members beyond agreement to work on a general area of technology. Nevertheless the Working Group<https://www.w3.org/2020/Process-20200915/#GroupsWG> decided to adopt the Working Draft<https://www.w3.org/2020/Process-20200915/#RecsWD> as the basis for their work at the time of adoption. A Working Draft<https://www.w3.org/2020/Process-20200915/#RecsWD> is suitable for gathering wide review<https://www.w3.org/2020/Process-20200915/#dfn-wide-review> prior to advancing to the next stage of maturity. For all Working Drafts a Working Group: * should document outstanding issues, and parts of the document on which the Working Group does not have consensus, and * may request publication of a Working Draft even if its content is considered unstable and does not meet all Working Group requirements. The first Working Draft of a technical report is called the First Public Working Draft (FPWD), and has patent implications as defined in the W3C Patent Policy [PATENT-POLICY]<https://www.w3.org/2020/Process-20200915/#biblio-patent-policy>. From: Jonathan Avila <jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>> Sent: Thursday, June 3, 2021 9:44 AM To: WCAG list (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>) <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: [External] : RE: CFC - WCAG 3.0 Heartbeat publication +0 I agree with Melanie, we need some paragraph explaining what has been updated and something acknowledging that feedback is in process. The paragraph Melanie points to is the type of thing that would clear up a lot of confusion. The term heartbeat publication is also confusing. I believe this is a working draft compared to an editor’s draft which I think means that there has been some agreement on what has changed in it (although it can and will continue to change). So communicating this in that introductory paragraph would really help folks in my opinion. Jonathan From: Melanie Philipp <melanie.philipp@deque.com<mailto:melanie.philipp@deque.com>> Sent: Thursday, June 3, 2021 9:24 AM To: Chuck Adams <charles.adams@oracle.com<mailto:charles.adams@oracle.com>> Cc: Silver TF <public-silver@w3.org<mailto:public-silver@w3.org>>; WCAG list (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>) <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: Re: CFC - WCAG 3.0 Heartbeat publication CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. -1 The status content Michael Cooper shared on June 1<https://urldefense.com/v3/__https:/www.w3.org/2021/06/01-ag-minutes.html*t01__;Iw!!GqivPVa7Brio!IwsVNaHh4NK5XEBEjzb-IEcBG8HOxSJolv3YsCfNmKfaKd045FwYJeeEA_edOnnLBBg$> is missing as far as we can tell. Melanie Philipp, CPACC, WAS | Director, Services Methodology | 540-848-5220 Deque Systems - Accessibility for Good www.deque.com<https://urldefense.com/v3/__http:/www.deque.com__;!!GqivPVa7Brio!IwsVNaHh4NK5XEBEjzb-IEcBG8HOxSJolv3YsCfNmKfaKd045FwYJeeEA_edG31hKU8$> On Tue, Jun 1, 2021 at 2:18 PM Chuck Adams <charles.adams@oracle.com<mailto:charles.adams@oracle.com>> wrote: Call For Consensus — ends Friday June 4, midnight UTC. The Working Group has discussed the publication of the first WCAG 3.0 Heartbeat, which can be found in full here: W3C Accessibility Guidelines (WCAG) 3.0<https://urldefense.com/v3/__https:/w3c.github.io/silver/guidelines/__;!!GqivPVa7Brio!IwsVNaHh4NK5XEBEjzb-IEcBG8HOxSJolv3YsCfNmKfaKd045FwYJeeEA_edEWf2jp0$> The changes for the first Heartbeat publication are: * Acknowledgements section https://w3c.github.io/silver/guidelines/#acknowledgements<https://urldefense.com/v3/__https:/w3c.github.io/silver/guidelines/*acknowledgements__;Iw!!GqivPVa7Brio!IwsVNaHh4NK5XEBEjzb-IEcBG8HOxSJolv3YsCfNmKfaKd045FwYJeeEA_eddxDA89s$> (Reviewed/discussed: https://www.w3.org/2021/05/11-ag-minutes.html#item04<https://urldefense.com/v3/__https:/www.w3.org/2021/05/11-ag-minutes.html*item04__;Iw!!GqivPVa7Brio!K8z0bkIH96h4vvm4L9CQ6Ga3B05zT7KKZn5FfcyreiArzveoX4DLARtwcCbbKZ5Kyw$>) * Editorial updates https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fwcag-3.0%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fsilver%2Fguidelines%2F<https://urldefense.com/v3/__https:/services.w3.org/htmldiff?doc1=https*3A*2F*2Fwww.w3.org*2FTR*2Fwcag-3.0*2F&doc2=https*3A*2F*2Fw3c.github.io*2Fsilver*2Fguidelines*2F__;JSUlJSUlJSUlJSUl!!GqivPVa7Brio!K8z0bkIH96h4vvm4L9CQ6Ga3B05zT7KKZn5FfcyreiArzveoX4DLARtwcCZjwpWbiQ$> Most of the changes remove content that went into the explainer that is NOT part of this heartbeat publication. We will do a more thorough review of the document before publishing the explainer as a separate TR note. Kind regards, Charles Adams
Received on Thursday, 3 June 2021 15:06:50 UTC