axe DevTools for Web API/CLI 4.2
Release Date: June 23, 2021
Overview
Axe DevTools 4.2 includes updates to Usage Service, a new axe-core version, and a new node integration with Playwright.
What's New
-
Updated axe-core version
axe DevTools 4.2 comes by default with the latest axe-core version, v4.2.1. For more information on axe-core 4.2.1, see the axe-core changelog. -
Added support for event v2 inteface in Deque's Usage Service
Users of axe DevTools can now set numerous additional usage service-related parameters through environment variables.
Environment Variable | Type |
---|---|
AXE_IS_LOGGED_IN | Boolean |
AXE_KEYCLOAK_ID | String |
AXE_USER_ID | String |
AXE_SESSION_ID | String |
AXE_USER_STATUS | String |
AXE_USER_JOB_ROLE | String |
AXE_DISTINCT_ID | String |
AXE_IS_DEV_INSTANCE | Boolean |
AXE_ORGANIZATION | String |
AXE_APPLICATION | String |
AXE_METRICS_URL | String |
AXE_TRACK_USAGE | Boolean |
-
Added support for axe DevTools Integration with Playwright
It includes all the standard features for axe DevTools JavaScript-based APIs but integrates with the rapidly popularizing Playwright end to end testing framework. -
Added the ability for axe DevTools Maven HTML packages to disable scanning in iframes.
-
Added support for axe DevTools pip 4.2 a new function that allows users to transpose their results to a JSON object directly.
Bug Fixes
-
In axe DevTools NuGet, Maven HTML, and pip, a bug was fixed which prevented enabling best practice rules.
-
Two bugs were also fixed in the axe DevTools CLI.
- Verbose mode in CLI spec mode now correctly outputs verbose results.
- Errors consistent with expected behaviours are now output when invalid tags are used in CLI spec mode.
Known Issues
- Axe DevTools Cypress is still not bundled by default.
- axe DevTools Cypress requires a
cypress.json
file with empty objects{}
at the project root level to function correctly.