Java API Overview
Overview of Axe DevTools for Web for Java, including available integrations and support resources
Deque’s Axe DevTools Java integration features include:
- Industry leading, zero false positives axe-core accessibility engine
- Support for Deque's report generating functionality
- Hamcrest, Cucumber, and Selenium based testing setups
Scans run against WCAG 2.1 Level AA by default, with best-practice and experimental rules turned off. See Customizing Rules to change the ruleset or enable best practices.
To download demo projects, bundled packages, and the Axe DevTools CLI, visit the downloads page.
If you aren't sure where to start, we recommend trying a demo project to get familiar with accessibility testing with Axe DevTools. As always, for customer support you can 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 workflow.
Custom Elements and ElementInternals
Starting in Axe DevTools Java 4.13.0, scans read the ARIA semantics that web components declare in JavaScript through ElementInternals, rather than only the role and aria-* attributes present in the markup. No configuration is required, and this applies to both the Selenium and Playwright integrations. Semantics in the DOM still take precedence: an explicit role or aria-* attribute on the element overrides the value from ElementInternals.
Your components must publish their internals for any of this to take effect, and a component that stores them in a private class field cannot be read. See Testing Custom Elements That Use ElementInternals.