- From: Shawn Lauriat <lauriat@google.com>
- Date: Fri, 6 Jan 2023 10:13:33 -0500
- To: Chuck Adams <charles.adams@oracle.com>
- Cc: Alastair Campbell <acampbell@nomensa.com>, "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <CAGQw2h=q5STtkpsdWF+kBmiJ=kmpeRFLfOy-J9_T+Yt6ueDrOg@mail.gmail.com>
+1 On Fri, Jan 6, 2023 at 10:01 AM Chuck Adams <charles.adams@oracle.com> wrote: > +1 > > > > *From:* Alastair Campbell <acampbell@nomensa.com> > *Sent:* Thursday, January 5, 2023 3:15 PM > *To:* WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org> > *Subject:* [External] : CFC - Removing 4.1.1 Parsing from WCAG 2.2 > *Importance:* High > > > > Call For Consensus — ends Wednesday January 11th at 6pm Boston time. > > > > This is specifically for WCAG 2.2 only. > > > > We have previously resolved (in meetings) to remove SC 4.1.1 Parsing from > WCAG 2.2, replacing the SC contents with a note explaining that it has been > removed: > > https://www.w3.org/2022/12/13-ag-minutes#item12 > <https://urldefense.com/v3/__https:/www.w3.org/2022/12/13-ag-minutes*item12__;Iw!!ACWV5N9M2RV99hQ!Iys50uLAESt7hGyQH_fj5NWKfzhupqt6uXuqr1vT0gbnCfMXsOiVBtoTvm-cnEwDaI8bR40KLxzJTFZGJ2C48Q$> > > https://www.w3.org/2022/11/22-ag-minutes#t08 > <https://urldefense.com/v3/__https:/www.w3.org/2022/11/22-ag-minutes*t08__;Iw!!ACWV5N9M2RV99hQ!Iys50uLAESt7hGyQH_fj5NWKfzhupqt6uXuqr1vT0gbnCfMXsOiVBtoTvm-cnEwDaI8bR40KLxzJTFaQwvnm8g$> > > > > The change can be seen in the editor’s draft: > > https://w3c.github.io/wcag/guidelines/22/#parsing > <https://urldefense.com/v3/__https:/w3c.github.io/wcag/guidelines/22/*parsing__;Iw!!ACWV5N9M2RV99hQ!Iys50uLAESt7hGyQH_fj5NWKfzhupqt6uXuqr1vT0gbnCfMXsOiVBtoTvm-cnEwDaI8bR40KLxzJTFZkw5yOSg$> > > And the understanding document (which needs some styling updates) shows > the proposed content: > > https://w3c.github.io/wcag/understanding/parsing.html > <https://urldefense.com/v3/__https:/w3c.github.io/wcag/understanding/parsing.html__;!!ACWV5N9M2RV99hQ!Iys50uLAESt7hGyQH_fj5NWKfzhupqt6uXuqr1vT0gbnCfMXsOiVBtoTvm-cnEwDaI8bR40KLxzJTFaLV2inog$> > > > > We will deal with any updates to WCAG 2.0 & 2.1 separately, this CFC is > for the new 2.2 version only. > > > > 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 > > > > -- > > > > @alastc / www.nomensa.com > <https://urldefense.com/v3/__http:/www.nomensa.com__;!!ACWV5N9M2RV99hQ!Iys50uLAESt7hGyQH_fj5NWKfzhupqt6uXuqr1vT0gbnCfMXsOiVBtoTvm-cnEwDaI8bR40KLxzJTFZmgi60NQ$> > > > > >
Received on Friday, 6 January 2023 15:13:57 UTC