Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support WCAG 2.2 #315

Open
werdnanoslen opened this issue Oct 11, 2023 · 4 comments
Open

Support WCAG 2.2 #315

werdnanoslen opened this issue Oct 11, 2023 · 4 comments

Comments

@werdnanoslen
Copy link

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

@ironikart
Copy link
Contributor

ironikart commented Oct 11, 2023

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
Copy link
Author

fwiw axe has one rule to check target size

@j-mendez
Copy link

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants