Re: CFC - Removing 4.1.1 Parsing from WCAG 2.2

+1 to the CFC to remove 4.1.1. I understand the concern about backward compatibility but given that we have established that there are no end-user impacting issues that aren’t caught by other SC I am comfortable with the WG regarding this not impacting practical backward compatibility.

Thanks,
AWK

Andrew Kirkpatrick
Director, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk



From: Alastair Campbell <acampbell@nomensa.com>
Date: Thursday, January 5, 2023 at 5:16 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC - Removing 4.1.1 Parsing from WCAG 2.2
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Thursday, January 5, 2023 at 5:15 PM


EXTERNAL: Use caution when clicking on links or opening attachments.



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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F12%2F13-ag-minutes%23item12&data=05%7C01%7Cakirkpat%40adobe.com%7C68c6d5060aa14f0051d308daef6a652d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638085537611963611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=YV6rUZx2z5LgBo%2B2shE1AJPcJ3y4m3WTqLMzYCLygT0%3D&reserved=0>

https://www.w3.org/2022/11/22-ag-minutes#t08<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2022%2F11%2F22-ag-minutes%23t08&data=05%7C01%7Cakirkpat%40adobe.com%7C68c6d5060aa14f0051d308daef6a652d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638085537611963611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=dojUOqlkwnYHTboBTCuDhckwNCzox3xxrFqGD3ZMqIA%3D&reserved=0>



The change can be seen in the editor’s draft:

https://w3c.github.io/wcag/guidelines/22/#parsing<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag%2Fguidelines%2F22%2F%23parsing&data=05%7C01%7Cakirkpat%40adobe.com%7C68c6d5060aa14f0051d308daef6a652d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638085537611963611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=I3tIBJdncusxSTpbF7wWL%2BKDKKDlp3aWDFw8ZUxmDHE%3D&reserved=0>

And the understanding document (which needs some styling updates) shows the proposed content:

https://w3c.github.io/wcag/understanding/parsing.html<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwcag%2Funderstanding%2Fparsing.html&data=05%7C01%7Cakirkpat%40adobe.com%7C68c6d5060aa14f0051d308daef6a652d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638085537611963611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=3eJfD7ON7F4dX6lIH5m%2BsVVqu1ZFbMgqVnMgVSPQHc8%3D&reserved=0>



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://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nomensa.com%2F&data=05%7C01%7Cakirkpat%40adobe.com%7C68c6d5060aa14f0051d308daef6a652d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638085537611963611%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=AZJxLu9f9rudDpwh4q7Fdq%2BDsZw5nPUBD7G5JNiWFgU%3D&reserved=0>