Installation Options for Axe DevTools for Web for Java

Deque offers these installation options for Axe DevTools Java:

• Download complete demo project pre-integrated with Axe DevTools: For customers who need the shortest path to produce value with Axe DevTools, we offer canned demo projects pre-integrated with Axe DevTools. We curate several examples to approximate virtually any testing environment. With one of these demo projects downloaded, you can produce accessibility scan reports for your own web pages in as little as ten minutes.
• Download bundled package of Axe DevTools and its dependencies: Designed for evaluation focused customers who want to integrate Axe DevTools into their own testing environments as simply as possible, as well as customers who have limited access to public artifact repositories. This installation option requires no additional dependencies and can be delivered through the largest number of avenues.
• Configure your artifact repository for users to download Axe DevTools from it: Our standard option is to configure your Nexus instance to distribute Axe DevTools to your organization's developers. This option is highly scalable and sustainable once Axe DevTools is set up within your artifact repository.
• Download Axe DevTools from Deque's Agora artifact repository: Designed to serve customers without their own artifact repository, this option leverages Deque's internal artifact repository. With access to this repository, developers are able to access Axe DevTools packages with the simplicity of a much larger organization's custom artifact repository instance.

How to choose

If it isn't clear which installation option you should choose, contact your Deque representative directly, ask us via our support desk, or send us an email. We'll be happy to help you select the best option for your environment.

Dependency Whitelist for Axe DevTools Java

If your artifact repository restricts access to public repositories like Maven Central, you need to whitelist every package Axe DevTools Java depends on before you can install it. Because this dependency set changes with each Axe DevTools Java release, generate it yourself rather than relying on a fixed list:

1. On a machine with normal, unrestricted internet access, add the Axe DevTools Java dependency for the integration you're using (Selenium, Hamcrest, Cucumber, or Playwright, see the installation options above) to a scratch project's pom.xml, pinned to the version you intend to install.
2. Run mvn dependency:tree -Dscope=compile to resolve the complete, version-exact set of groupId:artifactId:version coordinates that version depends on.
3. Provide that list to whoever administers your artifact repository to whitelist.