Understand Results

Each time you run your test suite, you will generate results that are pushed to Developer Hub. Here, you can view new and existing accessibility issues and track trends over time.

Understanding Your Project Structure

Developer Hub organizes your accessibility data differently depending on whether your end-to-end tests use Git for version control:

If using Git, you will be able to view different branches of your project, and individual commits made on these branches. The structure is as follows:
Project → Branches → Commits → Issue List → Issue Details

If not using Git, you will see individual test runs and can navigate to the issues found in each run. The structure is as follows:
Project → Test Runs → Issue List → Issue Details

Project Page

When you open a project, you'll see either a list of branches (Git projects) or test runs (Gitless projects).

Your Results at a Glance

You will see the following information returned from your acessibility testing:

• For Git projects: Branch name, latest commit SHA, and commit message for the end-to-end test being run
• For Gitless projects: Timestamp of the test run
• Number of issues exceeding the accessibility threshold
• Package and version information for the accessibility toolkit you are using
• Comparison summary showing total issue count and scan count, as well as new issues introduced and issues that were resolved
• 'View Commits' button (Git projects only) to drill down into individual commits
• 'View Issues' button (for Gitless projects) to see the full issue list

Pipeline Information

For teams whose tests are using Git, all runs can be compared against the CI/CD runs on the default branch, to ensure newly merging code isn't introducing additional accessibility issues. To set up the comparison, a project admin must set the accessibility toolkit to run on the repository's default branch - this is usually the main (or master) branch. This instance of the toolkit must be set up as a pipeline run.

Once scan data comes in from the designated pipeline run on the default branch, the results will display at the top of the page. Users can choose to view various result sets by API key and see how they compare to the pipeline run on the default branch.

Understanding Comparisons

The comparison information helps you understand what changed:

• For Git projects:
  • On the page displaying all of your project's branches, you are able to see how the latest commit on each branch compares to the latest pipeline run on the default branch.
  • When you select an individual branch to view, you are able to see how each unique commit on that branch compares to the commit that came before it.
• For Gitless projects: Each test run is compared to the previous run.

If you do not see any comparison data, it is likely no previous scan was available to compare it to, or a pipeline scan hasn't yet run on the default branch.

Learn more about using comparisons to track trends.

Learn More About Accessibility Issues

After clicking View Issues from a branch, commit, or test run, you'll see a summary page listing and grouping accessibility violations by rule and impact level.

Comparison Table (Web Projects Only)

Web projects display a comparison table at the top showing:

• Total issues in current and baseline scans
• New issues introduced
• Previously existing issues
• Issues that were resolved
• All of these are grouped by impact severity (Critical, Serious, Moderate, Minor)

Note: Mobile projects do not include this comparison table.

Rules List

Below the comparison section (or at the top for mobile), you'll see all violated accessibility rules grouped by:

• Rule name (which you can select to view individual issues)
• Impact level
• Number of violations found for that rule

Filtering and Exporting

With web projects, use the filter controls to focus on specific issues:

• Filter by impact level (Critical, Serious, Moderate, Minor)
• Show only new issues
• Select specific page states

With mobile projects, use the filter to select one or multiple screens in the list, and hone in on certain results.

Export your results:

• Web
  • Export JSON to easily share detailed results in human-readable format
  • Export CSV for spreadsheets and reporting
• Mobile
  • Export Axe Universal JSON format for integration with other tools

Exports will align with your current filters.

Single Issue Page

Click any rule name in the list of issues to see detailed information about each violation.

Finding Issues in Your Code

Web projects provide:

• Element source code (HTML snippet)
• CSS selector for locating the element
• XPath expression as an alternative locator
• All with copy buttons for easy use in your development tools

Mobile projects provide:

• Screenshot with the issue highlighted
• Details view: Gives context for the problematic element
• Inspect Hierarchy view: Shows the hierarchy tree for you to pinpoint the exact location and see detailed element properties

Remediation Guidance

Each issue includes:

• Rule description explaining the accessibility problem
• Links to Deque University or Mobile Rule pages for comprehensive guidance and code examples
• Impact level and accessibility tags (WCAG criteria, best practices)
• Navigation to step through all instances of this violation (e.g., "1 of 5")

Sharing Issues

Click Copy issue link at the top of the page to share with your team or add to your issue tracking system.

Sharing permissions: Issue links respect your organization's sharing settings. Team members need appropriate permissions to view issues. Admins can configure sharing settings in:

• Global Configuration - Set organization-wide sharing defaults
• Project Settings - Access and update settings for individual projects in Axe Developer Hub