Re: 4.1.1 Parsing in WCAG 2.0 and 2.1

Hi Charles,

(Taking this off the CFC thread.)

Wilco’s response in the survey was just one of the arguments, there have been others during previous discussions. I’ll try and gather those here:


  *   The SC is being actively abused now (e.g. drive-by validation), and causes the most wasted work of all the SCs. Changing only WCAG 2.2 doesn’t help with that.
  *   Removing the SC doesn’t change the underlying accessibility requirements. We’ve mapped those<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1MJ6FxO7ujQ4X9BQtAnDDoWyvpAKU44MR4h-bob9SG7M%2Fedit&data=05%7C01%7Cacampbell%40nomensa.com%7C968c22acf78b492710d108db201b2d67%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638139073343830409%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZWlv3RnK%2BFpvPgJKHMBvYHoIJcl877H2MlWND%2FyK%2BgQ%3D&reserved=0> to other WCAG 2.0 SCs. (And that’s a useful understanding doc addition we can make).
  *   There has been wide misinterpretation of the SC’s intent<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fissues%2F2525&data=05%7C01%7Cacampbell%40nomensa.com%7C968c22acf78b492710d108db201b2d67%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638139073343830409%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SBPhAuAtiI4q7k7l6kA5%2Bh22PhulXFV8Ct%2BEv7%2BuojU%3D&reserved=0>. If we don’t remove it, we should update the understanding document (potentially the SC text via errata) to clarify that, and people will realise it now achieves nothing except ‘busy work’.
  *   If we don’t make this change to WCAG 2.0 and 2.1, we will have objections to removing it from WCAG 2.2<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fissues%2F3034&data=05%7C01%7Cacampbell%40nomensa.com%7C968c22acf78b492710d108db201b2d67%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638139073343830409%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wMxJMpHZRy%2B4VAelKVMfq9UOtmg3jY4pIJ9Cnn8JsOw%3D&reserved=0>. (That is one, I’m aware of another potential member objection.)
  *   Some organisations are already ignoring the SC now, requiring customers/clients to justify changes based on user-impact rather than lack of conformance.
  *   For most people, it is simply less to do. Even from folks involved in regulations, their reaction has been (paraphrasing): People building/testing to 2.0 may continue to do something they don’t need to, people checking will be pleasantly surprised there is one less thing to do.

Chair-hat off to add my own observation:
There is a difference between WCAG and other W3C specs: If people stop using a CSS feature, it doesn’t particularly matter if it is still included in the spec, it doesn’t create work for authors. If a defunct SC remains in a spec, it creates work for thousands (millions?) of authors and testers around the world.
If we had an accessibility priority of constituencies<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Falastairc.uk%2F2022%2F12%2Fwcag-priority-of-constituencies%2F&data=05%7C01%7Cacampbell%40nomensa.com%7C968c22acf78b492710d108db201b2d67%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638139073343830409%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FQ34R6jCPB%2F3MvV0AM2or7iuFdyT9pZKUCM7l1rchPg%3D&reserved=0>, I think we’d put that work over spec purity.

Chair-hat on to look at ways forward, I can see several paths:

  *   This CFC passes;
  *   We try to compromise by not removing the SC text, but including a note that says it is not required anymore.
  *   We don’t align it with 2.2 but update it to make clear it doesn’t include the ‘content model’.

Kind regards,

-Alastair


From: Chaals Nevile
This isn't really a new argument. It is about procedure and W3C process, not the technical merits (which I don't think are in much dispute).

I'm likely to object, including as an AC rep making a formal objection to substantively changing a previously published versioned recommendation.

Wilco's reasoning, that doing so makes WCAG 2.2 compatible with WCAG 2.0/2.1 fails to convince me. What it does do is mean that earlier claims of non-conformance to WCAG 2.0 or 2.1 are no longer valid.

It also means that any organisation who are using WCAG 2.0/2.1 now, for whatever reason, need to understand that the promise underpinning a W3C Recommendation is being broken. That seems a far more serious issue than removing he promise that WCAG 2.2 will be backwards compatible, and one that affects every W3C Recommendation and so most W3C Working Groups.

I am unlikely to decide I "can live with" this. If you want an HTML-style specification that changes when you feel like it, then make one, instead of a W3C Recommendation.

cheers

Chaals

On Wednesday, 8 March 2023 18:58:40 (+01:00), Alastair Campbell wrote:
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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2023%2F03%2F07-ag-minutes%23item10&data=05%7C01%7Cacampbell%40nomensa.com%7C11e8cf50a6d14846211208db200288d4%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638138967477863783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=F5kluAQvSpr8hjA1I6Esa05U9g8a4QB9uN63O9ErLRU%3D&reserved=0>

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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fpull%2F3093&data=05%7C01%7Cacampbell%40nomensa.com%7C11e8cf50a6d14846211208db200288d4%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638138967477863783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6p5aBp2H1ITp17QrFpeA%2FIr02tvZAIkreJbzitVKO3c%3D&reserved=0>
https://github.com/w3c/wcag/pull/3094<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fpull%2F3094&data=05%7C01%7Cacampbell%40nomensa.com%7C11e8cf50a6d14846211208db200288d4%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638138967477863783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Na6thzZPxUi%2Fh9PP08t6CbqSgRbaJFyj0O1PWCKeQhM%3D&reserved=0>

Survey results: https://www.w3.org/2002/09/wbs/35422/wcag22-misc5/results#xq23<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35422%2Fwcag22-misc5%2Fresults%23xq23&data=05%7C01%7Cacampbell%40nomensa.com%7C11e8cf50a6d14846211208db200288d4%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638138967477863783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3NYFiTFXRxw87voW%2B9GaYyjldpx0sPM%2B1D7eqQOMzPo%3D&reserved=0>

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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2021%2FProcess-20211102%2F%23last-call-review&data=05%7C01%7Cacampbell%40nomensa.com%7C11e8cf50a6d14846211208db200288d4%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638138967478019989%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f%2F7ZxW6M%2FvI3Dthg56giyT7KHnqtmBZYRzKUYwlrBAw%3D&reserved=0>

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nomensa.com%2F&data=05%7C01%7Cacampbell%40nomensa.com%7C11e8cf50a6d14846211208db200288d4%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C638138967478019989%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4LttdlxOEpwdQAsVZ2N4gEzfxBZjbfQBT50jvKJAuRc%3D&reserved=0>

--
Charles 'Chaals' Nevile
Lead Standards Architect, ConsenSys Inc