Support WCAG 2.2

[werdnanoslen]

WCAG 2.2 has been officially released, and tools like pa11y rely on this to automatically check for compliance.

[ironikart]

After a very brief initial look at the new success criteria I couldn't say any of them would be a good candidate for automated testing with this library (at least not to confidently say that you could 'pass' the criteria with an automated test). If someone reads this issue and decides to open a pull request note that HTMLCS has a 'notice' warning for these kinds of criteria that require manual testing.

[werdnanoslen]

fwiw axe has one rule to check target size

[j-mendez]

Hi @werdnanoslen, A11yWatch has an engine like pa11y for the cloud kayle that uses a runner called fast_htmlcs. We rewrote the htmlcs and axecore from the ground up and it is over 100x - 1000x increased in performance with the continuation of 2.2 rules.

You can use the kayle lib to run or install the runner like you would this lib with npm i fast_htmlcs.

[Welchie32]

Do we know when Pa11y will be updated to scan for WCAG 2.2?

[kiyah]

I'm getting at least 2x the output comparing the html_codesniffer WCAG 2.1 output to the axe-core WCAG 2.2 output. It looks like this tool does a better job of pulling issues. Can we get any more details on why this library isn't a good candidate to update? It seems like the superior tool from an output perspective.