Release Notes for axe DevTools Linter

4.9.3 (September 9, 2024)

• On-prem versions of axe DevTools Linter no longer set up analytics.

4.9.2 (August 12, 2024)

• Allow users to specify a directory when installing the on-prem server.

4.9.1 (June 17, 2024)

• The deprecated /status REST endpoint is temporarily mapped to return the same value as the /healthcheck endpoint. The /status endpoint will be removed in a future version of axe DevTools Linter.

4.9.0 (May 8, 2024)

• Added missing attributes to the definition of the MUI TablePagination component. (The definition was missing all attribute definitions, and aria-* and other common attributes were added.)

• Updated dependencies to resolve their known critical and high-security issues:

  Dependency	CVE	Severity
  ansi-regex	CVE-2021-3807	HIGH
  cookiejar	CVE-2022-25901	HIGH
  get-func-name	CVE-2023-43646	HIGH
  glob-parent	CVE-2020-28469	HIGH
  http-cache-semantics	CVE-2022-25881	HIGH
  ip	CVE-2023-42282	CRITICAL
  lodash.pick	CVE-2020-8203	HIGH
  minimist	CVE-2021-44906	CRITICAL
  minimatch	CVE-2022-3517	HIGH
  normalize-url	CVE-2021-33502	HIGH
  nth-check	CVE-2021-3803	HIGH
  postcss	CVE-2021-23382	HIGH
  semver	CVE-2022-25883	HIGH
  trim-newlines	CVE-2021-33623	HIGH
  word-wrap	CVE-2023-26115	HIGH

• Fixed the on-prem installer to include missing environment variables. The missing variables would cause the server to restart repeatedly. The missing values are written to the axe-linter.service file and are:

  • DEPLOY_ENV (default value: prod)
  • PORT (default value: 3000)

• Bumped the axe-linter-connector version to 4.9.0.

• Bumped the IntelliJ plugin version to 4.9.0.

4.8.3 (March 14, 2024)

• Bundled the LSP server with the plugin for JetBrains IDEs (IntelliJ IDEA Ultimate and WebStorm). (The LSP server was previously downloaded upon the first run of the plugin.)

4.8.2 (February 29, 2024)

• Fixed problem when linting Vue with TypeScript.
• New plugin for linting with IntelliJ IDEA Ultimate and WebStorm.

4.8.1 (January 5, 2024)

• Fixed errors that appeared when running the on-premises Dockerfile.
• Allow default attributes in custom components to be boolean values.
• Fixed start-up problems with the on-premises server, where it required several unnecessary environment variables to be set (among other issues).

4.8.0 (October 3, 2023)

• axe DevTools Linter now supports these new rules:
  • aria-conditional-attr
  • aria-deprecated-role
  • aria-prohibited-attr
• You can now use multiple config files with axe DevTools Connector and axe Accessibility Linter for VS Code. These tools will now locate the nearest axe-linter.yml file: the one in the current directory or, if there is none, will walk up the directory tree to find one. This allows you to place a config file in the root of your project and override it with config files in different subdirectories.
• Fixed a problem in the VS Code extension that prevented encoded URLs from being decoded properly.

4.7.3 (August 23, 2023)

• axe DevTools Linter Connector has a new option: --stdout for redirecting output to standard output (stdout). The following is example output for a file with one accessibility error:

  ::error title=Axe Linter::meta-refresh (https://dequeuniversity.com/rules/axe/4.7/meta-refresh?application=axe-linter-connector) - Ensures <meta http-equiv="refresh"> is not used for delayed refresh,file=./rules/meta-refresh/meta-refresh.html,line=4,endLine=4,col=4,endColumn=59::
  ::debug::Found 1 issues.

• Previously, axe DevTools Linter Connector displayed a count of files that failed to lint even if the count was zero. This behavior has been changed to only show the count if it's not zero.

• Fixed a problem with validating API keys that caused linting to fail.

4.7.2 (July 12, 2023)

• There is a new configuration option, overrides, which allows you to change the type of linter used for the specified files (individual files or files matching a glob pattern). See overrides for more information.
• A Docker image for on-prem axe DevTools Linter usage is now available. For more information, contact your Deque representative directly, ask us via our support desk, or send us an email.
• In this release, we fixed several bugs that affected only internal users.

4.7.1 (May 23, 2023)

• The exclude configuration option now allows a string. (Previously, it only allowed an array of strings). See exclude for more information.
• Fixed a custom component linting bug in .jsx files that caused <text> mappings to be ignored.
• Fixed a bug where the exclude configuration option was ignored.
• Fixed a bug where the VS Code extension wasn't running in the correct ExtensionMode.

4.7.0 (April, 26, 2023)

• @mui/material Component Support
  axe DevTools Linter now includes definitions for the MUI components in the @mui/material package. See Material UI for more information.
• React Native Support
  Test for accessibility issues in your React Native apps even earlier in the development cycle with axe DevTools Linter. Combine this with automated testing using axe DevTools Mobile to catch more advanced accessibility issues in your apps.
• Several bugs across all axe DevTools Linter packages were fixed in v4.7.
• Known Issue: Exclude configuration from axe-linter.yml does not work in VS Code plugin or axe DevTools Linter.

4.6.0 (February 1, 2023)

• New Rules
  axe DevTools Linter 4.6 implements a new rule. For complete details, refer to empty table header.
• Cauldron React Custom Component Library Support
  Deque’s open-source library of React components called Cauldron React now has full support in axe DevTools Linter. No manual custom component configuration is required, just a single configuration step. More component libraries are coming soon.
• Fixed several internal bugs.