The switch from Selenium.Axe to Deque.AxeCore is, by design, really straight forward. This is because Deque.AxeCore is a fork of Selenium.Axe so the interfaces to both are very similar.
- Add Deque and Html packages
- Deque.AxeCore.Commons
- Deque.AxeCore.Selenium
- TWP.Selenium.Axe.Html
*Only if you are using the current HTML report functionality
- Remove Selenium.Axe package
- Update usings
- Remove
using Selenium.Axe;
- Add
using Deque.AxeCore.Commons;using Deque.AxeCore.Selenium;using TWP.Selenium.Axe.Html;
*Only when creating HTML reports
- Deque is officially taking on the .Net bindings
- Yes
- Selenium.Axe actually uses Deque’s Axe core under the hood
- This should help keep the .Net bindings at feature parity with the other official supported binding, such as Java and JavaScript
- The new Deque project will support both Selenium and Playwright
- A standalone HTML reporter library has been created and will be maintained until the Microsoft HTML reporter gets released.
Automated web accessibility testing with .NET, C#, and Selenium. Wraps the axe-core accessibility scanning engine and the Selenium.WebDriver browser automation framework.
Compatible with .NET Standard 2.0+, .NET Framework 4.7.1+, and .NET Core 2.0+.
Inspired by axe-selenium-java and axe-webdriverjs. Forked from Globant.Selenium.Axe.
- Getting Started
AxeBuilderReference- Working with
AxeResultobjects - Creating a HTML report
- Contributing
This project would not exist in its current form without the generous support of
