- From: Siegman, Tzviya <tsiegman@wiley.com>
- Date: Wed, 8 Mar 2023 20:01:58 +0000
- To: Alastair Campbell <acampbell@nomensa.com>, "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <SN4PR0201MB8711825C41CAF81FE9F931C2D5B49@SN4PR0201MB8711.namprd02.prod.outlook.>
+1 Tzviya Siegman Information Standards Principal Wiley 201-748-6884 tsiegman@wiley.com<mailto:tsiegman@wiley.com> From: Alastair Campbell <acampbell@nomensa.com> Sent: Wednesday, March 8, 2023 12:59 PM To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org> Subject: CFC - 4.1.1 Parsing in WCAG 2.0 and 2.1 Importance: High ⛔ This is an external email. Call For Consensus — ends Friday Wed 15th at midday Boston time. The group has discussed what to do with 4.1.1 Parsing in WCAG 2.0 & 2.1 now that it has been removed from WCAG 2.2. From the discussion: https://www.w3.org/2023/03/07-ag-minutes#item10<https://urldefense.com/v3/__https:/www.w3.org/2023/03/07-ag-minutes*item10__;Iw!!N11eV2iwtfs!ugTba4q53qozcGQqEMEEyasXd33losP4RZNX-n0rUudD53Ypjem-rTaYQTM6JowML9H_10C7jmfez9VGJw$> Following the same approach as WCAG 2.2 was the preferred approach, where the SC text would be removed and replaced with a note that says why it has been removed. The specific changes are detailed in these two pull requests: https://github.com/w3c/wcag/pull/3093<https://urldefense.com/v3/__https:/github.com/w3c/wcag/pull/3093__;!!N11eV2iwtfs!ugTba4q53qozcGQqEMEEyasXd33losP4RZNX-n0rUudD53Ypjem-rTaYQTM6JowML9H_10C7jmdMiSXedg$> https://github.com/w3c/wcag/pull/3094<https://urldefense.com/v3/__https:/github.com/w3c/wcag/pull/3094__;!!N11eV2iwtfs!ugTba4q53qozcGQqEMEEyasXd33losP4RZNX-n0rUudD53Ypjem-rTaYQTM6JowML9H_10C7jmcNvvv_-g$> Survey results: https://www.w3.org/2002/09/wbs/35422/wcag22-misc5/results#xq23<https://urldefense.com/v3/__https:/www.w3.org/2002/09/wbs/35422/wcag22-misc5/results*xq23__;Iw!!N11eV2iwtfs!ugTba4q53qozcGQqEMEEyasXd33losP4RZNX-n0rUudD53Ypjem-rTaYQTM6JowML9H_10C7jmewMpiCqg$> 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. Assuming the group agrees to this change, there is likely to be a public review before we can re-publish WCAG 2.0 & 2.1. https://www.w3.org/2021/Process-20211102/#last-call-review<https://urldefense.com/v3/__https:/www.w3.org/2021/Process-20211102/*last-call-review__;Iw!!N11eV2iwtfs!ugTba4q53qozcGQqEMEEyasXd33losP4RZNX-n0rUudD53Ypjem-rTaYQTM6JowML9H_10C7jmcpGrAkRg$> Kind regards, -Alastair -- @alastc / www.nomensa.com<https://urldefense.com/v3/__http:/www.nomensa.com__;!!N11eV2iwtfs!ugTba4q53qozcGQqEMEEyasXd33losP4RZNX-n0rUudD53Ypjem-rTaYQTM6JowML9H_10C7jmfGTPcEDg$> ________________________________ The contents of this email and any attachments are confidential and intended only for the person or entity to whom it is addressed. If you are not the intended recipient, any use, review, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this message in error, please immediately notify the sender and permanently delete all copies of the email and any attachments. Click here for translations of this disclaimer.<https://secure.wiley.com/email-disclaimers> ________________________________
Received on Wednesday, 8 March 2023 20:02:21 UTC