Re: CFC - Removing 4.1.1 Parsing from WCAG 2.2

+1
________________________________
From: Kersey, Ian (TR Product) <Ian.Kersey@thomsonreuters.com>
Sent: Monday, January 9, 2023 14:36
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: RE: CFC - Removing 4.1.1 Parsing from WCAG 2.2


+1



. . . . . . . . . . . . . . . . . . . . . .



Ian Kersey

Senior Accessibility Specialist

Pronouns: he/him/his



Thomson Reuters



Ian.Kersey@thomsonreuters.com<mailto:Ian.Kersey@thomsonreuters.com>



thomsonreuters.com<https://urldefense.com/v3/__https://nam02.safelinks.protection.outlook.com/?url=http*3A*2F*2Fthomsonreuters.com*2F&data=04*7C01*7CIan.Kersey*40thomsonreuters.com*7C621477c6cd4747a7f04908d9cedc9488*7C62ccb8646a1a4b5d8e1c397dec1a8258*7C0*7C0*7C637768269042108162*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=vnIKuakf4B0L5LToeU8b*2BvinZN*2BbmDyDnBeDl*2FJuDHM*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSU!!GFN0sa3rsbfR8OLyAw!YGT-hBxA1vlQCWsCJ96fCFmsHVUjg9HRhRJs4iAkHGRptzYRhKWO4tZyeClaOS3ja7Zclw3sQK4ZRN2rUCOXsOTy0MK7cUZqJQ$>

facebook.com/thomsonreuters<https://urldefense.com/v3/__https://nam02.safelinks.protection.outlook.com/?url=http*3A*2F*2Ffacebook.com*2Fthomsonreuters&data=04*7C01*7CIan.Kersey*40thomsonreuters.com*7C621477c6cd4747a7f04908d9cedc9488*7C62ccb8646a1a4b5d8e1c397dec1a8258*7C0*7C0*7C637768269042108162*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=FGwvaF*2FBWQwAyJoaApmaqvmGeMcUZpoJot4N8i0pfcc*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUl!!GFN0sa3rsbfR8OLyAw!YGT-hBxA1vlQCWsCJ96fCFmsHVUjg9HRhRJs4iAkHGRptzYRhKWO4tZyeClaOS3ja7Zclw3sQK4ZRN2rUCOXsOTy0MKu0shsVA$>

twitter.com/thomsonreuters<https://urldefense.com/v3/__https://nam02.safelinks.protection.outlook.com/?url=http*3A*2F*2Ftwitter.com*2Fthomsonreuters&data=04*7C01*7CIan.Kersey*40thomsonreuters.com*7C621477c6cd4747a7f04908d9cedc9488*7C62ccb8646a1a4b5d8e1c397dec1a8258*7C0*7C0*7C637768269042108162*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=55n0WEZzeqRxmA9vpTKmh92ir8pgyv8F*2FYhsoRpTSi4*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUl!!GFN0sa3rsbfR8OLyAw!YGT-hBxA1vlQCWsCJ96fCFmsHVUjg9HRhRJs4iAkHGRptzYRhKWO4tZyeClaOS3ja7Zclw3sQK4ZRN2rUCOXsOTy0MJIG0v5NA$>

linkd.in/thomson_reuters<https://urldefense.com/v3/__https://nam02.safelinks.protection.outlook.com/?url=http*3A*2F*2Flinkd.in*2Fthomson_reuters&data=04*7C01*7CIan.Kersey*40thomsonreuters.com*7C621477c6cd4747a7f04908d9cedc9488*7C62ccb8646a1a4b5d8e1c397dec1a8258*7C0*7C0*7C637768269042108162*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000&sdata=IVURCjXgkYj2vpOyatsz3M6AlLlD*2F6vV8F*2B*2FXCF*2BJKk*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!GFN0sa3rsbfR8OLyAw!YGT-hBxA1vlQCWsCJ96fCFmsHVUjg9HRhRJs4iAkHGRptzYRhKWO4tZyeClaOS3ja7Zclw3sQK4ZRN2rUCOXsOTy0MLbsGqMzQ$>



. . . . . . . . . . . . . . . . . . . . . .



From: Ben Tillyer <ben@accessibility.org.uk>
Sent: Monday, January 9, 2023 10:54 AM
To: Storr, Francis <francis.storr@intel.com>
Cc: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [EXT] Re: CFC - Removing 4.1.1 Parsing from WCAG 2.2



External Email: Use caution with links and attachments.



+1



Kind Regards,

Ben Tillyer





On 9 Jan 2023, at 16:22, Storr, Francis <francis.storr@intel.com<mailto:francis.storr@intel.com>> wrote:



+1



From: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Date: Thursday, January 5, 2023 at 14:16
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: CFC - Removing 4.1.1 Parsing from WCAG 2.2

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!!GFN0sa3rsbfR8OLyAw!YKDLUWXJ8gN56F-uydtpd-ncAo48HRaOW2KO1Dnok3t_1cYAn6G4MRqBjagOo6fCp8cUDB1aLQDTAqW7AR3QP7cI5w$>

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!!GFN0sa3rsbfR8OLyAw!YKDLUWXJ8gN56F-uydtpd-ncAo48HRaOW2KO1Dnok3t_1cYAn6G4MRqBjagOo6fCp8cUDB1aLQDTAqW7AR1JDdKTMQ$>



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!!GFN0sa3rsbfR8OLyAw!YKDLUWXJ8gN56F-uydtpd-ncAo48HRaOW2KO1Dnok3t_1cYAn6G4MRqBjagOo6fCp8cUDB1aLQDTAqW7AR1nBMkOoQ$>

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__;!!GFN0sa3rsbfR8OLyAw!YKDLUWXJ8gN56F-uydtpd-ncAo48HRaOW2KO1Dnok3t_1cYAn6G4MRqBjagOo6fCp8cUDB1aLQDTAqW7AR21RFqKkg$>



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__;!!GFN0sa3rsbfR8OLyAw!YKDLUWXJ8gN56F-uydtpd-ncAo48HRaOW2KO1Dnok3t_1cYAn6G4MRqBjagOo6fCp8cUDB1aLQDTAqW7AR3hfw8tVA$>