Re: Removing 4.1.1 Parsing from WCAG 2.2

On Friday, 6 January 2023 14:06:16 (+01:00), Wilco Fiers wrote:


We promised WCAG 2.2 would be backward compatible. What I'm hearing you say 
is that with the current decisions, it won't be.


This is, by far, the best reason NOT to remove 4.1.1 from WCAG 2.2 - and I 
would not object to a group decision keeping the requirement in, noting 
that it is explicitly to ensure that conformant WCAG 2.2 documents are 
conformant to WCAG 2.1 and 2.0, rather than because it still serves a known 
purpose directly.


However, doing this would push the question of what to do with a 
requirement that has no benefit onto implementors, and it would be 
reasonable for many of them to say "it's important to almost-meet WCAG 2.2, 
but don't worry about 4.1.1". Such an approach would legitimately call into 
question the quality of our current work. I think that's a worse outcome 
than deciding we're not going to maintain compatibility after all for a 
decade-old requirement, since the world has actually changed.


So I am changing my vote on the CfC slightly. I still think endorse 
removing the requirement to meet 4.1.1, but I think the text should explain 
more clearly what it was, and that it is required if people want to conform 
to 2.0/2.1.


cheers


Chaals

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