Release Notes for axe DevTools for Web CLI

Link to Release Notes for axe DevTools for Web CLI copied to clipboard

Release notes describing the changes in the CLI for version 4.7.0 and later

4.9.0 (April 5, 2024)

  • Updated the axe-core dependency to 4.9.0.

4.8.2 (February 13, 2024)

  • Upgraded @axe-core/cli dependency to version 4.8.5.
  • Upgraded to axe-core version 4.8.3.

4.8.1 (January 30, 2024)

  • Fixed problem when URL specified specified with the --axe-reports-url command-line option ended with /reports.
  • Fixed a problem where the process would sometimes not exit when processing large spec files.
  • Added fetchUrlTime and actionTime to the JSON results file.
  • Added duration, fetchUrlTime, and actionTime to standard output when using the ‑‑verbose command-line option.
  • Upgraded to axe-core version 4.8.2.
  • Upgraded @axe-core/cli dependency to version 4.8.4.

4.8.0 (October 24, 2023)

  • Added additional error messages for invalid bulk-reports options.
  • Added the Trusted Tester v5 ruleset.
  • Added the EN 301 549 ruleset.
  • Upgraded to axe-core version 4.8.2.
  • Upgraded the @axe-core/cli dependency to 4.8.1.

4.7.2 (August 28, 2023)

  • Fixed a problem on Windows that prevented the CLI from uploading JSON results to axe-reports.
  • Added YAML support to the bulk-spec command.
  • Added new option to add set the dimensions field in JSON results (--axe-reports-dimensions).

4.7.1 (June 15, 2023)

  • Add verbose logging option to bulk-reports.
  • Upgraded to axe-core 4.7.2.
  • Upgraded the axe-core integrations to 4.7.3.

4.7.0 (May 12, 2023)

  • Upgraded to axe-core 4.7.0.
  • bulk-spec
    A problem on Windows that caused the bulk-spec command (batch processing of spec files) to skip processing of spec files has been fixed.
  • Updated Command-Line Options
    Several command-line options have been changed to make their use clearer and more consistent:
    • The --user-agent option is now always used by Chrome regardless of the headless setting or whether a remote proxy has been configured.
    • The --accept-untrusted option is always used regardless of the browser or headless setting. (Previously this option required the --headless option to be set.)
    • The --remote-proxy is always used by Chrome (no longer depends on the --headless option or whether an https site is being scanned).