Re: WCAG 2.2 - tightened requirements approach

> So testers will need to test for each variation and record the results.  So we need an approach that facilitates folks doing that.  So even if we were to modify 2.4.7 testers would still need to test the different versions of it

Ok, but for people testing multiple versions of WCAG at the same time, they know the SCs pretty well?
We could mark 2.4.7 as deprecated in 2.2, and they would know where to find the previous version (and we could link to it).

We also need to consider that having a stronger requirement (which we want) means that some techniques/failure will not be compatible with older versions.

E.g. G165 for using default focus styles would be deprecated for 2.2. And we could create a new failure for a focus indicator that fails the new requirement. Those will be part of the WCAG non-normative documents, including the Quickref.

As we have one set of docs across versions, we’ll need to mark some as deprecated, or only applicable from WCAG 2.2.

Cheers,

-Alastair