RE: CFC - Removing 4.1.1 Parsing from WCAG 2.2

-1

Not disagreeing with the removal, however, I agree that removing it for 2.2 without figuring out how we are dealing with earlier versions of WCAG is problematic.

Thanks,

Sheri

-----
Sheri Byrne-Haber (She/Her)
Senior Staff, Accessibility Architect
Mobile: 650 703 2376 (please text first if you have not called me before, otherwise it may go to VM)

Upcoming OOO: PTO December 24 through January 3, 2023
Expect a delay in my replies

Phonetic pronunciation:   shei riə bUHRn heɪ buhr
Audio:   https://vimeo.com/665808784

ASL Name Sign:  https://vimeo.com/665809840


From: Alastair Campbell <acampbell@nomensa.com>
Sent: Thursday, January 5, 2023 2:15 PM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: CFC - Removing 4.1.1 Parsing from WCAG 2.2
Importance: High

!! External Email

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%7Csbyrnehaber%40vmware.com%7C997283ca713343b2983808daef6a69af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638085537583534741%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xSzj7LekwPOlO0TXicxfADBNs1lI%2FQNpxtzJxUBmZZQ%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%7Csbyrnehaber%40vmware.com%7C997283ca713343b2983808daef6a69af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638085537583534741%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=k6rnoZh5s6OSZqldAFO93mQcSpq%2FgFoFLbA2N2rGkq4%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%7Csbyrnehaber%40vmware.com%7C997283ca713343b2983808daef6a69af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638085537583534741%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Z9Go5yLu2UqKkVyZr9j%2FfTYM%2BDeUxWf%2FXIwKEh3FTXE%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%7Csbyrnehaber%40vmware.com%7C997283ca713343b2983808daef6a69af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638085537583534741%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RoPUx4jLXpEMVJ3dvZLx%2BCXWmUPFqJ2Yih8brLozZBc%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%7Csbyrnehaber%40vmware.com%7C997283ca713343b2983808daef6a69af%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638085537583690973%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oa3HrAMRSeHb9pnRlmBp3W12tZtu9llEQkSUuZmsJ5E%3D&reserved=0>



!! External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.