mabl automatically aggregates all of your accessibility testing results in the cloud in the accessibility dashboard, providing a single view of all issues that may impact your users and key experiences. The accessibility dashboard provides a single view of all the issues that may impact your users and key experiences, so you can spend more time focusing on issues that matter.
This article explains how to interpret the accessibility dashboard.
The accessibility dashboard
For information about configuring and running the checks that power this dashboard, visit our accessibility testing overview documentation.
The accessibility dashboard aggregates data from across your testing. There are three core pieces of the dashboard:
Filters
In addition to the filters on the accessibility dashboard, you can also use the application filter to display rule violations for a specific web app.
Filtering the accessibility dashboard by application
Rule violation history
The rule violation history represents the active rule violations according to your configured filters. As you start to understand the quality of accessibility in your app, you can update the target to set a threshold for your team to stay under.
Setting a target threshold for accessibility violations
Active rule violations
With your filters set, the list of active rule violations represents the last day in the rule violation history chart. Rule violations are defined by axe-core and sorted by severity, with critical issues always appearing first and minor issues always appearing last.
The expanded view of a rule violation includes links to the test runs the issue was last detected in.
Instances
The number of instances represents the number of unique pages that hit a violation. This number is a helpful indicator of how widespread an issue is. The more frequently the violation appears throughout your app, the greater number of instances.
URL clustering
Rather than reporting on a new violation every time multiple tests hit the same page, mabl uses a process called "URL clustering" to identify and group together accessibility rule violations that may be related to one single issue. In the following example, the accessibility dashboard automatically groups together all issues on the coverage page: /workspaces/*/coverage with a wildcard [*] to prevent overreporting.
Resolving violations
mabl keeps track of both the page and the test that the violation occurred. Violations are removed from the dashboard when the same test no longer identifies a violation on that page. Violations are completely resolved once all tests that initially detected the violation no longer detect the violation.