Automated testing with aXe -- A11ycasts #15
ฝัง
- เผยแพร่เมื่อ 16 มี.ค. 2017
- 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.
ChromeDriver for Selenium:
chromedriver.storage.googleap...
Watch all A11ycasts episodes: goo.gl/06qEUW
Subscribe to the Chrome Developers TH-cam channel for updates on new episodes of A11ycasts: goo.gl/LLLNvf
thank you for the really good introduction
nice explanation. Thank you!
Thank you for the great info.
Hey Rob, Very nice series of lectures.
your work is awesome
Hay Rob. Thanks for making these videos. Most of the webpages we work with needs credentials to login to it. How can we do it with axe-selenium combo?
very good explanation
This is awesome..thanks so much
How can I get Element source and location in results while performing automated execution?
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.
For the axe-cli, is there a way to only output violations? and is there a way to have the results outputted nicely into a file rather than in the command line output?
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.
Do you know how to install this with java ? Instead of js..
Does it also output keyboard accessibility issues?
Anything like this for Android and IOS?
9:38
Hi Rob, I installed Axe as Chrome-Extensions, but it looks like axe is no longer free to use. Is that right?
when I run the axe-webdriverjs tests the exact same way it returns null to the console. it also throws an error when using
Interesting !
Google Chrome Developers is using apple mac