What's New for Release 7.5

Classic View Help

Access the Knowledge Base here.

Sign Up to receive the latest updates on axe Monitor in an email. 

Important Note: This is the last planned release for the v7.x series of axe Monitor. The product will still be supported, and patch updates will be provided for any critical bugs and security vulnerabilities. We are focusing on releasing the next major version of axe Monitor in 2024. With v8.0, axe Monitor will provide major improvements for users. You have seen some early screens for this in the Experimental View.

This also means that some of the existing features will be transformed. This includes (but is not limited to) items like Page/Issues exports and some common settings like the axe-core version. We will keep you posted on upcoming changes for v8.0 and are also planning on providing a seamless transition from v7.5 to v8.0. Where possible, we will work with you on the migration.

If you would like to know more about what is being planned for v8.0, please reach out to your Engagement Manager or Account Executive.

Bug Fixes - 7.5.5

• Scan runs now recover seamlessly from exceptions during the initial scan item publishing.
• Scan URLs with large pages now complete successfully without triggering a CLI exception.
• Scan URLs with dashes in a subdomain are now supported.
• Scans with an underscore (_) in the URL are now supported.

Bug Fixes - 7.5.4

• Axe Monitor users were previously unable to use axe-core version 4.10. This issue has been resolved, and axe-core version 4.10 is now fully compatible with axe Monitor.

Known Issues - 7.5.4

• When importing URLs, some domains are not created because the system checks if the existing domain is a substring of the URL. This causes certain URLs to be skipped during scans.

  Workaround: Manually add any missing domains to ensure all URLs are scanned.

Bug Fixes - 7.5.3

• Scanning HTML pages that redirected to PDFs previously failed without a detailed error message. This issue is now fixed, ensuring successful scans.
• Users can now perform PDF deep scans (several link levels below a starting URL) without experiencing page failures.
• Axe Monitor now supports axe DevTools for Web CLI v 4.6.3+.
• PDFs containing the query string '/?' in the URL can now be scanned.
• Axe Monitor now provides AAA conformance level support for WCAG standards for both new and existing scans.

Known Issues - 7.5.3

• axe-core version 4.10 is currently incompatible with axe Monitor.

Workaround: We recommend that axe Monitor customers use axe-core version 4.9, as it is currently the compatible version. All customers using axe-core 4.10 have been switched to version 4.9.

Bug Fixes - 7.5.2

• PDF scans can now identify missing table tags, and a false positive for color contrast has been resolved.
• For scans with extremely large headers, a 502 gateway error has been fixed.
• Scanning pages with URLs ending with "/" no longer results in a "String index out of range" error.
• The "Update axe Reports" button on the Project Dashboard is only available for Completed scans.
• In the Experimental view, users can now filter for WCAG 2.2 level AA issues on the Issues page.
• Sometimes, running a scan triggered a "405 Method Not Supported" error. This issue has been fixed.

Known Issues - 7.5.2

• axe-core version 4.10 is currently incompatible with axe Monitor.

  Workaround: We recommend that axe Monitor customers use axe-core version 4.9, as it is currently the compatible version. All customers using axe-core 4.10 have been switched to version 4.9.

Bug Fixes - 7.5.1

• Initiating a scan in axe Monitor resulted in a scan failure when the browser's language was set to anything other than English or Japanese. This issue has now been fixed.
• In the Classic View, exporting issues (Detailed or Brief) nested within multiple selectors previously led the exported files to duplicate issues and display them in multiple rows. This issue has now been fixed.
• In the Classic View, exporting issues nested within multiple selectors caused the exported files to have multiple commas between selectors, and trailing commas.
• In the Experimental View, when using the MS SQL database and exporting issues, certain selectors got truncated in the files.
• In the Experimental view, when performing bulk actions like Export on Issues or Pages, filtered selections from a previous scan were mistakenly included, even if the new scan's selections were different in the Scan Filter modal.

Known Issues - 7.5.1

• axe-core version 4.10 is currently incompatible with axe Monitor.

  Workaround: We recommend that axe Monitor customers use axe-core version 4.9, as it is currently the compatible version. All customers using axe-core 4.10 have been switched to version 4.9.

• In the Classic View, during scanning, the monitor cache service may crash or become unavailable, causing the scanning process to fail. When this happens, a "Channel is Closed" error is displayed, indicating a temporary server error.

What’s New in 7.5

Experimental View

View Page Details

Users can now easily view information about a specific page in a scan on the Pages page. Clicking on the View Page Details icon brings up the Manage Page dialog box, where you can find information such as the accessibility score, a number of critical, serious, moderate, and minor issues on the page impact, total issues within the page, total number of pages in the scan, runtime in seconds, link to the page, source URL, date the page was created, and so on. 

You can access information on all pages in the Manage Page dialog box for a scan. Navigate between the pages using the Previous Page and Next Page buttons.

View Issue Details

Users can now easily view information about a specific issue in a scan on the Issues page. Clicking on the View Issue Details icon brings up the Manage Issue dialog box, where you can find information such as the issue impact, the date the issue was created, the issue description, element location, element description, comments, etc. 

You can access information on all issues in the Manage Issue dialog box for a scan. Navigate between the issues using the Previous Issue and Next Issue buttons.

Bulk Actions on the Issues Page

Axe Monitor now includes multiple new bulk actions, allowing users to perform actions on multiple issues at the same time. The following new bulk actions have been added.

1. Delete: Use the Delete option to delete the selected issues. Be careful when doing this, as the delete command is irreversible. 

2. Export: Use the Export option to export the selected issues into a CSV file. You can select the fields you want included in the CSV file using the Configure Fields option.

3. Mark/Unmark as Issue

   1. Mark as Issue: Use this option to mark a reported Needs Review item as an issue after review.

   2. Unmark as Issue: Use this option to ****change an issue back to Needs Review item. This option only changes issues that were originally identified as Needs Review and were marked as Issue by the user. 

4. Assign To: Use this option to assign the selected issues (or modify the existing assignment) to a specific user. In order to remove any existing assignments, use the option ‘Nobody’.

5. Set Status: Use the three options to set the status of the selected issues:

• Open: Use this option to set the issue's status to Open, indicating that the issue is currently open.

• Fixed: Use this option to indicate that the issue has been resolved. If these issues are identified in subsequent scan runs, they will be marked as ‘Open’ again.

• Ignored: Use this option to set the issue as ignored, indicating that the issue exists but can be ignored. Ignored issues remain as ‘Ignored’ even if they are identified in subsequent scan runs.

  

Bulk Actions on the Page

Axe Monitor has introduced two new bulk actions on the Pages page, allowing users to perform actions on multiple pages at the same time. 

1. Delete: Use the Delete option to delete the selected pages. Be careful when doing this, as the delete command is irreversible. Deleting a page results in the page and all related issues being deleted.

2. Export: Use the Export option to export the selected pages into a CSV file. You can select the fields you want included in the CSV file using the Configure Fields option.

   

New and Renamed Columns on Scans List Page

The Accessibility Score column on the Scans List page has been renamed to Score. The page also has a new column, Total, added to the list, displaying the total number of issues for a scan.

Filter Issues Based on Page Title

Users can now filter issues on the Issues Page according to the page title for all completed scans.

Classic View

Support for Kerberos Authentication

Axe Monitor now supports Kerberos authentication. Scan administrators can now scan websites that are Kerberos-protected, and retrieve the accessibility results for those sites with a correct user login and password.

Users can select the Auth type as Kerberos in the Edit Scan page.

Bug Fixes

• Multiple A11Y bugs were fixed.

• When a user tried to upload multiple files using the Upload Issues button on the Scan Overview page in the Experimental view, the page count in the Pages screen in the Classic view did not match the page count in the Runs section of the Scan Overview page in the Experimental view.

Classic View Bugs

• The Issue Details page displayed the impact for issues in PDF format incorrectly, showing it as XXX.

• System administrators who were added to guest user groups could not create organization projects and were being redirected to the Organization Settings page.

• When scheduling scans with the options "First day of the month" and "Last day of the month", the scans kept re-queuing because of an incorrect update of the next scheduled time. 

• Configuring a scan to send its output to axe Reports without setting the Scan Approval Percentage on the System Settings page, and then uploading issues using axe DevTools extension threw an error in the Project Dashboard page.

• When a scan with zero completed pages was run and submitted to axe Reports, followed by another scan with more than zero completed pages, the Project Dashboard failed to load.

• Running a scan with a PDF page containing a zero-length whitespace character in the URL led to the failure of the PDF scan.

• When scheduling scans after daylight savings time, some screens displayed incorrect Scheduled time.

• Scans scheduled to start at midnight on a specific day sometimes run two times if they complete in less than 5 minutes. 

• When the user tried to export issues from a scan with multiple selectors, the exported CSV file contained some issues with multiple rows corresponding to each selector.

• When the user tried to scan an HTML website that automatically downloads PDFs to the user's machine, the scans sometimes failed.

Experimental View Bugs

• The Issues Filter dialog box erroneously included "None" as an option for Status.

• Attempting to remove over 2100 issues on the Issues page failed in the Windows environment and resulted in an error message.

• When navigating between Pages, Issues, and Scan Overview pages, the screens would be reset each time, requiring the users to reselect scan runs on the Issues and Pages screens. The scan run details were also presented in a collapsed format. 

• Japanese translations were not visible, with only English being displayed. 

• When the user tried exporting issues on a Windows server, the downloaded file was empty.

Infrastructure Announcements

• Axe core upgraded to 4.8.2.

• Support for EN 301 549 and Trusted Tester v5 rules added. 

• WCAG 2.2 Support

 Future Deprecation Announcement

• Support for axe Monitor installs on RedHat 7.x, Windows Server 2016, and MS SQL Server 2016 will be dropped at the end of 2023.

Known Issues

• axe-core version 4.10 is currently incompatible with axe Monitor.

  Workaround: We recommend that axe Monitor customers use axe-core version 4.9, as it is currently the compatible version. All customers using axe-core 4.10 have been switched to version 4.9.

• Upon marking all issues across all pages as Ignored in the Experimental View, the Classic View incorrectly displays a non-zero count of pages. The count should be zero since all the issue statuses have been changed to Ignored.

• If a scan is triggered in ‘headful’ mode (chromedriver setting headless: false), PDF documents are sometimes not scanned by axe Monitor. This is a browser behavior issue where Google Chrome opens the PDF document as a web page in the browser PDF viewer.

  Workaround: Upgrade Chrome and Chromedriver to the latest version. Upgrade the axe DevTools CLI to 4.6+. Contact Deque HelpDesk for support. 

• If a user logs directly into the new experimental view (using the bookmarked link, for example) and then tries to navigate to the classic view, an authentication error is displayed. 

  Workaround: Refreshing the screen removes the error message and displays appropriate data.

Other Relevant Topic

• Release Summary
• Platform Support