What's New for Release 2.22
Access the Knowledge Base here.
Sign Up to receive the latest updates on axe Auditor in an email.
Bug Fix - 2.22.2
- Axe Auditor has improved security to help prevent unauthorized actions on the database.
Bug Fix - 2.22.1
- Axe Auditor has optimized its database queries for performance, resulting in faster page load times and a more seamless user experience.
What's New
Enhanced Elements Section
The following are the new features added to the Add New Issue and Edit New Issue modals:
-
You can add multiple elements to an issue using the + Add Element button. Each issue can have a maximum of 3 elements.
-
The Auto Detect button automatically detects an element's selector, source code, and screenshots. When clicked, it opens the URL in a new tab in the same browser, allowing you to select an element, which is then automatically added to the issue.
New Elements Section on the Individual Issues Page
When viewing individual issues, the screen now contains the "Elements" section. This section displays the selector, source code, and screenshots under each element in the issue.
Increased Screenshot Limit Per Issue to 15
Users can now include additional screenshots per issue while adding or editing an issue. This number has been increased from the limit of 10 to 15 screenshots per issue.
Bug Fixes
-
Multiple A11y bugs were fixed in this release.
-
Anonymous users (users who are not logged into axe Auditor) can now view screenshots on the Issues page when using an incognito browser by clicking the "View" button.
-
The extra option that appeared in the "Issue Type" dropdown on the Add Issue, Edit Issue, and Issues List screens has now been successfully removed.
Known Issues
-
When a user copies an issue and changes the screenshot name in the copied issue, the screenshot name in the original issue is also incorrectly updated.
-
On the View Issues page, clicking the delete button multiple times when deleting a comment displays multiple delete notifications, even though the comment is only deleted once.
Workaround: Avoid clicking the delete button multiple times as clicking it once successfully deletes the comment.
-
The filter function is not working on the Checkpoint tab for flagged issues.
-
Performing automated testing on a component behind an iFrame throws an error, and the loading icon is displayed indefinitely.
Browser/Driver Support
The following table describes the minimum version and the recommended version on which axe Auditor is actively tested and best supported.
| Browser | Min Version | Recommended Version |
|---|---|---|
| Chrome | 102.0.5005.184 (LTS) | 130.0.xx |
| Firefox | 102.15.1 (ESR) | 131.0x |
| Safari | 16 | 18.0 |
| Edge | 110.0.1587.41 (ESR) | 129.0.x |
Note: Automated testing is only supported on Chrome and Firefox.
Infrastructure Upgrade
- Deque Way version upgraded to 3.16.0.
Detailed Deque Way 3.16.0 Release Notes
Testing Notes:
- 1.3.2.a Reading Order
- Adds a note under Things to Think About: “It is acceptable for hidden content to be only provided for screen readers, such as headings or instructions.”
- 1.4.12.a Text Spacing
- Adds HTML datalist to the list of exceptions: “Options inside an HTML select dropdown or datalist dropdown”
- 2.4.11.a Focus not Obscured (Minimum)
- Adds a note to the testing methodology: “When the color of the element and the background it is on are the same, it may not be obvious while tabbing through a page what the boundary of an element is, for example: a link hit area that extends beyond the link text. Use the mouse hit or hover area to determine the actual boundary of the element.”
- 3.3.2.a Visible Labels
- Adds a note to the remediation recommendations: “It is permissible for labels to appear only when a field is hovered and focused. For example, the "Select all messages" checkbox on the Gmail Inbox screen. Keep in mind, this may not be a viable solution for mobile web.”
- EU Web Accessibility Directive - Accessibility Statement
- Clarifies that, if assessing a mobile application, the Accessibility Statement must directly address the mobile application. Information about a corresponding website does NOT satisfy this requirement.
- EN 301 549 5.3 Biometrics
- Removes the word "accessible" from the final test step.