RE: WCAG 2.2 acceptance criteria

Hi David,

I agree that it probably won’t come up. From looking at the proposed SCs, the COGA ones are all interface / task-oriented SCs, so I don’t think this will come up for 2.2 anyway.

As a side note:
One source of my concern is from experience of testing at AAA, and SC such as:
3.1.6 pronunciation, where you have to read every word on the page and work out whether it could be mis-understood as another word. (E.g. is “Desert” used as “abandon” or “arid region”?)

It is *really* easy to miss instances, and very hugely time consuming to test, especially if you are doing it to the side of your day job (like most of the people I train). If there were a tool that could highlight those words from a set list, that would be a massive improvement. That is the type of thing that could pull the requirement up a level as it would be more feasible and applicable across scenarios.

NB: I’m not assuming that SC is something that helps folk with neuro-cognitive issues, it is just an example where available tools would make a difference.

Cheers,

-Alastair