-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Use axe-core to set up automated accessibility testing #48
Comments
@ovlb @dengeist I would love to hear your thoughts on this specifically! |
I would be careful to say «any violations» as automatic testing can only find a subset of violations/problems with the accessibility of a site. Besides from nitpicking though, I think it makes sense to build up a testing/linting infrastructure, and axe should be a part of it. |
Agreed! Linting is mainly here to help us catch the low-hanging fruit, but that's fine; getting it in place will allow us to better claim responsibility for the rest of the app's accessibility. |
Great, thank you, @dengeist and @ovlb . I'm going to add a separate issue that includes "Set up testing/linting infrastructure/workflow." |
@tatianamac @ovlb @dengeist thanks for the feedback! Yes @ovlb automated accessibility testing is only the first step and definitely a good starting point! |
@tatianamac I think this actually needs to be re-opened as @codeAbul was going to tackle it once the other CI had been set up. |
We #74 to keep track of the single parts, so maybe having this closed gets rid of some duplication. |
I think axe-core( https://github.com/dequelabs/axe-core ) is a lovely little tool we could incorporate into our dev workflow to catch any accessibility violations at the earliest. Would love to hear thoughts on this
The text was updated successfully, but these errors were encountered: