Re: WCAG 2.2 - tightened requirements approach

Andrew wrote:
> I think that your option 4 is the same as option 1 – Alastair detailed it as 2.4.11 in his email. Can you confirm that this is what you are talking about?

In my original email option 1 was simply adding an SC, not changing the original (except perhaps the level, as part of option 2).

The difference for option 4 would be that the current SC would be marked as deprecated in some way (or even deleted from the spec?). I put an example in my email earlier today.


Jon Avila wrote:
>People may be testing against 2.2 but may not meet 2.2 and then want to know how they conform with 2.1 or 2.0.

I don’t think we can automate that. In any case you’d have to test for different requirements to have an answer to both 2.1 & 2.2.


  *   If there is a separate SC then you’d have to test an extra set of requirements on top of focus-visible in a separate SC.
  *   If there is a modified SC then you’d have to test an extra set of requirements on top of focus-visible from the 2.1 SC.

Either way you’d have to test with & without the new requirements.

However, if you are just interested in 2.2 (or just 2.1) then having a modified SC is easier.
Similarly, having 2.4.7 clearly marked as deprecated in 2.2 is easier, if slightly cluttered.

Cheers,

-Alastair