-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
WCAG 2.0 validation #366
Comments
Just found https://github.com/accesslint/accesslint.rb, which might be able to take some of the load. |
And that links to a set of rules at https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules. |
I could knock together a PR that uses |
I'll have to think about this a bit. On the one hand, I care about accessibility, and have hand-rolled or used other tooling to support this for CI. On the other hand, I added HTML validation to Proofer, and it ended up being a bad idea due to a bunch of false positives and work-arounds. I'd like to avoid that sort of situation here too, if it's possible. 😅 |
Yeah, it's not really a hard-and-fast validation, so the potential for false positives is high. I know what you mean... |
I recommend closing the issue as out of project scope (recommended scope discussed at #422). This is still a great idea and can be implemented as a third-party module (and mentioned here on a wiki) if anyone is interested to work on it. |
Closing this issue now based on the approved project scope. I do also care about accessibility. Please see the brand new wiki pages which discuss how to extend html-proofer. mailto-awesome in there is a simple example you can copy from to implement this additional check. I think a lot of people will want to use it and I would personally add it to my https://github.com/fulldecent/lightning-sites and https://github.com/fulldecent/html-website-template projects. |
I found http://tenon.io the other day for validating sites against accessibility guidelines, which is great. It would be amazing if html-proofer could do this as part of a CI workflow. There are guidelines on accessibility evaluation at https://www.w3.org/WAI/eval/Overview, but I don't know if there is a specific set of pass/fail type tests for this stuff - I'm far from an expert...
The text was updated successfully, but these errors were encountered: