-
Notifications
You must be signed in to change notification settings - Fork 252
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
pa11y WCAG 2.1 support #425
Comments
Hi @nicolocarpignoli - thanks for using Pa11y! Glad you find it useful ❤️ We don't support WCAG 2.1 yet, but we do plan to. We rely on HTML_Codesniffer for our rulesets, and they're working on the WCAG 2.1 update now, so it'll arrive shortly. We also plan to incorporate aXe Core as an optional test runner, and I believe they include WCAG 2.1 in their current ruleset. We're not quite ready to merge that work yet, but you can follow the PR if you'd like to keep up to date on how it's going 😄 |
thanks! good luck :) |
First I would like to say thanks, this is a great tool and I appreciate the work you do. I was looking through HTMLCodeSniffer's ruleset.js on their master branch https://github.com/squizlabs/HTML_CodeSniffer/blob/master/Standards/WCAG2AA/ruleset.js It appears that they have added WCAG 2.1 rules to their test set. When I pull down Pa11y and look at the ruleset.js for WCAG2AA HTMLCodeSniffer it states Is there a certain version of HTMLCodeSniffer being pulled down as part of Pa11y? |
Though WCAG 2.1 AA has been added to the |
Hi, thanks for your work, it's really helpful.
I see from the readme and using pa11y for a while that it uses WCAG 2.0, a version from 2008. From June 2018 we also have WCAG 2.1 standard available.
Does pa11y support new rules from this new version of the standard? If not, do you have in plan to add them in the future?
Reference: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/
Thanks
The text was updated successfully, but these errors were encountered: