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

Use axe-core to set up automated accessibility testing #48

Closed
codeAbul opened this issue Jan 20, 2020 · 7 comments · Fixed by #85
Closed

Use axe-core to set up automated accessibility testing #48

codeAbul opened this issue Jan 20, 2020 · 7 comments · Fixed by #85
Labels
Resolution · Duplicate Issue or PR that already exists Type · Feature Request New feature or request

Comments

@codeAbul
Copy link
Contributor

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

@tatianamac
Copy link
Collaborator

@ovlb @dengeist I would love to hear your thoughts on this specifically!

@tatianamac tatianamac added the Type · Feature Request New feature or request label Feb 13, 2020
@ovlb
Copy link
Collaborator

ovlb commented Feb 13, 2020

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.

@mxmason
Copy link
Contributor

mxmason commented Feb 13, 2020

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.

@tatianamac
Copy link
Collaborator

Great, thank you, @dengeist and @ovlb . I'm going to add a separate issue that includes "Set up testing/linting infrastructure/workflow."

@codeAbul
Copy link
Contributor Author

@tatianamac @ovlb @dengeist thanks for the feedback! Yes @ovlb automated accessibility testing is only the first step and definitely a good starting point!

@greatislander
Copy link
Contributor

@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.

@ovlb
Copy link
Collaborator

ovlb commented Mar 5, 2020

We #74 to keep track of the single parts, so maybe having this closed gets rid of some duplication.

@tatianamac tatianamac added the Resolution · Duplicate Issue or PR that already exists label Mar 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution · Duplicate Issue or PR that already exists Type · Feature Request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants