Skip to content

aXe runner support #28

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Open
cfq opened this issue Jun 16, 2020 · 4 comments
Open

aXe runner support #28

cfq opened this issue Jun 16, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@cfq
Copy link

cfq commented Jun 16, 2020

Pa11y uses HTML_CodeSniffer by default but unfortunately HTML_CodeSniffer isn't very good when it comes to finding barriers that can be detected by automated accessibility checkers, and aXe is quite a lot better.

Pa11y has support for different runners and it would be great we could specify which one we prefer.
@ehmicky
Copy link
Contributor

ehmicky commented Jun 16, 2020

Hi @cfq,

This makes sense. Would you be interested in sending a PR to add support for this?
Thanks!

@ehmicky ehmicky added the enhancement New feature or request label Jun 16, 2020
@cfq
Copy link
Author

cfq commented Jun 16, 2020

Thanks @ehmicky, I definitely would!

@ehmicky
Copy link
Contributor

ehmicky commented Jun 16, 2020

Thanks! Please let me know if you need any help 🙏

@swyxio
Copy link
Contributor

swyxio commented Jul 9, 2020 •
edited
Loading

just for some historical context - this plugin originally used axe, and we could not get it to work in netlify's buildbot for whatever reason: #2

hence I pivoted to use pa11y AFTER spending 1 whole week failing at getting axe cli to work.

good luck, i hope you figure it out.

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cfq @swyxio @ehmicky