Published on March 17, 2017 by Chrome

aXe on GitHub: goo.gl/0FDyHW

Manually reviewing a site for accessibility issues can be a time consuming process. Automated tools help streamline the work and make it easier to catch subtle mistakes. Today on A11ycasts we’ll show one of those tools, a library called aXe, and how you can use it as a drop in script, a Selenium runner, or from your command line.

Watch all A11ycasts episodes: goo.gl/06qEUW

Subscribe to the Chrome Developers YouTube channel for updates on new episodes of A11ycasts: goo.gl/LLLNvf

Leave a Reply

15 Comments on "Automated testing with aXe — A11ycasts #15"

Notify of
avatar

John Dillick
Guest
John Dillick
11 days 2 hours ago

brew install chromedriver

Homer Gaines
Guest
Homer Gaines
28 days 11 hours ago

The aXe Chrome extension is my go-to choice for automated testing. I used WAVE once and it had way too many false positives and was very noisy visually.

Silvio Aprigio
Guest
Silvio Aprigio
27 days 20 hours ago

Homer Gaines

robrez
Guest
robrez
1 month 2 days ago

does this tend to generate fewer false positives than wct a11ySuite (chrome dev tools)?

Marcy Sutton
Guest
Marcy Sutton
1 month 18 hours ago

Yes. And aXe tests a wider range of things.

Ranger2000
Guest
Ranger2000
1 month 2 days ago

thank you for the really good introduction

Rami Nas
Guest
Rami Nas
1 month 5 days ago

i have very good idea for chrome inter face

Rami Nas
Guest
Rami Nas
1 month 5 days ago

google joke= jokela

Rami Nas
Guest
Rami Nas
1 month 5 days ago

hey rob im traying to contact you for creat google joke becouse google image not helping isend request on facebook

TheJaredWilcurt
Guest
TheJaredWilcurt
1 month 7 days ago

Damn, I just released Koa11y a few days ago, it's built on top of Pa11y. Now I'm thinking it may make more sense to add in aXe support. Maybe a future version.

Neil Osman
Guest
Neil Osman
6 days 1 hour ago

right

José Bolos
Guest
José Bolos
6 days 1 hour ago

Neil, minor correction, pa11y doesn't use a11y, it uses squizlabs.github.io/HTML_CodeSniffer/

Marcy Sutton
Guest
Marcy Sutton
1 month 18 hours ago

SVG title wasn't always exposed, that's why aXe does that. We have an open issue to collect data on support so we can add it, here: github.com/dequelabs/axe-core/issues/20

Neil Osman
Guest
Neil Osman
1 month 1 day ago

Very Nice! Do note that Pa11y (which is dependent on a11y) does not recognize aria-label as a legit source for accName, so Koa11y has too many false positives. BTW, aXe also has some false positives like not recognizing SVG title nodes as a legit source for accName.

Denis TRUFFAUT
Guest
Denis TRUFFAUT
1 month 7 days ago

Interesting !

wpDiscuz