Now Available in axe Monitor 8.5
What’s New in Axe Monitor 8.5
Support for RGAA 4 Testing Standard
Axe Monitor now supports testing against RGAA 4, the official standard for digital accessibility in France. This update enables organizations operating in France to assess website compliance with RGAA guidelines directly within axe Monitor. A new RGAA-specific template has been introduced for this standard. RGAA testing is supported only in the latest axe-core version (4.11.0) and will be included in all future axe-core releases.
Find Text in Scans like “Accessibility Statement”
The Find Text setting allows scan admins to search for a specific word or phrase across all pages in upcoming scan runs. This setting makes it easier to verify whether certain terms or statements such as “Accessibility Statement,” “Accessibility Officer,” or “WCAG” appear on a website. Organizations can use this feature to ensure compliance with internal or regulatory content requirements (for example, confirming that an Accessibility Statement is present on all government websites). Users can configure scans to look for exact text matches, and identify whether the specified term exists anywhere within the scanned pages.
Exclude Common Components from Scan Results
Axe Monitor now makes it easier for site teams to focus on issues within their control. If your team does not work on Common Components, you can now specify common components, and choose to exclude them from future results. Previously, teams had to manually filter to “Uncommon” issues when reviewing scan results. With this improvement, axe Monitor streamlines the review process for development and site teams that are not responsible for managing shared components.
Bug Fixes
- CSV export filenames now display the scan name and date of the scan run.
- Formatting was improved on the issue detail view for users navigating at 400% zoom.
- Missing or incorrect translations to French, Spanish, Italian, German, and Japanese were corrected across several areas of axe Monitor.
- Double-clicking the “Save” button on a scan no longer creates a duplicate scan.
- When non-valid environment variables are added to a scan, they can now be removed without an error.
- Occasionally, the setting to limit scanning to a domain was not working after upgrade to version 8. This has been corrected.
- Exporting more than 50,000 pages or issues previously produced an improperly formatted CSV file. This has been corrected.
- The template URL was not removed from a scan after deleting the associated preset. This issue has been corrected to ensure the template URL is also deleted from the scan settings along with the preset.
- Previously, a small number of axe Monitor issues we not always properly sending data to axe Reports. This issue is fixed with an upgrade to axe Monitor 8.5.
- Scans which are assigned to presets with common components can now be deleted without first removing the scan from the preset. Presets & common component settings are now maintained when scans are deleted in version 8.5.
- When a user runs a scan with the “Save page content” option enabled and then renames the scan, the saved page content does not appear. This issue has now been resolved and now the page content displays appropriately.
Known Issues
- Public Share Links are only available once a scan run has been completed.
- Users with the Scan viewer permission are not able to assign issues to other users.
- “Comment” field content on individual issues does not currently persist across scan runs.