Using Axe to Add Accessibility Checks to Your Existing Selenium Tests

preview_player
Показать описание
Accessibility is no longer a nice to have but rather a must have for many applications. Luckily there are things like the W3C’s WCAG (Web Content Accessibility Guidelines) that help testers understand accessibility standards. But wait, it gets better for teams that are using Selenium. This is because adding accessibility checks to your automation is both quick and easy.

In this webinar, Magenic Practice Lead Troy Walsh will show how to leverage Axe, an accessibility testing engine, to add accessibility checks to your existing Selenium test suite. You will see just how easy it is, and be left wondering why it took you so long to get started.

Key Takeaways:
- How to easily add accessibility checks to your existing Selenium suite using Axe

---------------------------------

Connect with Sauce:
Рекомендации по теме
Комментарии
Автор

i wonder, no comments so far.
so here i am, This is superb!!
i wish there will be more videos about integrating axe api to selenium in pageobject way.

niteshjain
Автор

Hi team,
Do this automation provides the same results which we do scanning manually in web browser or this automation results are different from ui manual scanning results?

zencxanalytics
Автор

@sauce Labs, Could you please help answer below question? Thanks so much!

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 have atleast 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 test case. I find this inefficient from code standpoint hence asking a 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 every single time individually?

Looking for a response. Thanks again!

dp-hyjz