Automated testing with aXe -- A11ycasts #15

Рет қаралды 44,429

7 жыл бұрын

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 KZfaq channel for updates on new episodes of A11ycasts: goo.gl/LLLNvf

Пікірлер: 34

@Ranger2060 7 жыл бұрын

thank you for the really good introduction

@sureshgarine 5 жыл бұрын

nice explanation. Thank you!

@gotchyared 4 жыл бұрын

Thank you for the great info.

@devduttanatu7058 6 жыл бұрын

Hey Rob, Very nice series of lectures. Is there exclusively any plugin or tool just like 'axe' to test the complaince category wise i.e whether it is 'a', 'aa' or 'aaa' complaince ?

@ramalakshmitammineni9288 3 жыл бұрын

your work is awesome

@adityabarbadikar9848 5 жыл бұрын

How can I get Element source and location in results while performing automated execution?

@art-o-holic1242 4 жыл бұрын

This is awesome..thanks so much

@sudheendrasubramanya2556 Жыл бұрын

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?

@varungudisena9463 4 жыл бұрын

very good explanation

@doreenfarfan4593 6 жыл бұрын

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?

@RizzyClipz 4 жыл бұрын

Did you ever find a solution

@sainaasaimaa 5 жыл бұрын

Do you know how to install this with java ? Instead of js..

@markuslemcke 2 жыл бұрын

Hi Rob, I installed Axe as Chrome-Extensions, but it looks like axe is no longer free to use. Is that right?

@armatearjun 7 жыл бұрын

Anything like this for Android and IOS?

@ashishgujar6540 4 жыл бұрын

Does it also output keyboard accessibility issues?

@thejaredwilcurt 7 жыл бұрын

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.

@neilosman4440 7 жыл бұрын

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.

@MarcySutton 7 жыл бұрын

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

@JoseBolos 7 жыл бұрын

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

@neilosman4440 7 жыл бұрын

right

@xircle 7 жыл бұрын

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.

@silvioaprigio7179 7 жыл бұрын

Homer Gaines

@dp-hy8jz 3 жыл бұрын

Hey Homer, do you test accessibility as part of your CI? If yes, could you share more details?

@ihowaonaro4511 4 жыл бұрын

when I run the axe-webdriverjs tests the exact same way it returns null to the console. it also throws an error when using results.violations. Pls how can I sort this out?

@faria_aki 2 жыл бұрын

same here

@DenisTRUFFAUT 7 жыл бұрын

Interesting !

@error.418 7 жыл бұрын

9:38 you don't have to restart your terminal to ensure changes to your .bash_profile take affect. Just use the command "source ~/.bash_profile"

@dp-hy8jz 3 жыл бұрын

Hello, could you please help answer the below question? Appreciate your time and help! Do we have an ability to write an automation code that will let Axecore scan all pages with in an Automation test case OR do we have to specify the individual page every single time? For example my cucumber test case (Ruby on Rails) have at least 10+ automation scenarios and each scenarios open several pages of the application being tested. Currently we are calling the step definition that scans the page, every time a single page is referenced. So we end up calling the Axe core step definition multiple times within a single test case. I find this inefficient from code standpoint hence asking a question. QUESTION: Do we have an ability to write an automation code that will let Axecore scan all pages with in a Cucumber Automation test case OR do we have to specify the scanning step definition for every single page individually? Looking for a response. Thank you again!

@error.418 3 жыл бұрын

@@dp-hy8jz How much are you paying and why are you recruiting in the KZfaq comments?