Exporting Data

Link to Exporting Data copied to clipboard

After running a scan you will be brought to the "Overview" tab with your scan results. There, you will find an "Export" button. When clicked, a dialog will appear allowing you to configure which type of export you would like along with the export format.

Export types

Issue export

The issue export is supported in both CSV and JSON formats. This will contain information pertaining to each accessibility violation found from both automatic testing as well as Intelligent Guided Testing.

Supported CSV Schemas

axe DevTools Pro (default)
column name description
Rule ID The identifier for the accessibility rule
Description A description of the accessibility rule
Help Helpful information regarding the rule violated leading to issue
Help URL A URL with help for the given rule
Impact The impact or severity of the issue
Manual Whether the issue was found manually (IGT) or not
Needs Review Whether or not the potential issue needs manual review
IGT Which specific IGT was run to find issue (blank if not found by IGT)
Selector The CSS selector for the issue element
Summary Summary of issue
Source Code The HTML source code snippet of the issue element
Tags Metadata for the issue (categories, wcag checkpoint identifiers, etc.)
Found By User who peformed test in which issue was raised
Test Title The name of the saved test
Test URL The url of the page tested
Share URL The shared issue URL (only populated when issue or saved test explicitly shared)
Created At When the issue was first created
axe Reporter

This schema is compatible with the "axe Reporter" CSV generated from axe DevTools API integrations. This schema is especially useful if you are aggregating data from both the axe DevTools browser extension and APIs/CLI.

column name description
Page URL The url of the page tested
Page Title The document title of the page tested
Outcome The outcome of the issue (will be blank for axe DevTools Pro)
Impact The impact or severity of the issue
Code Snippet The HTML source snippet of the issue element
Selector The CSS selector for the issue element
Remediation Issue remediation info
Manual Whether the issue was found manually (IGT) or not
Rule ID The identifier for the accessibility rule associated with the issue
Help Helpful information regarding the rule violated leading to issue
Description A description of the accessibility rule
Help URL A URL with help for the given rule
Standard Which WCAG standard/checkpoint the issue falls within
WCAG 2 Success Criteria The WCAG success criteria for the issue
Section 508 Paragraph Applicable Section 508 information for the issue
Tags Metadata for the issue (categories, wcag checkpoint identifiers, etc.)
Date Date the issue was found
axe-core Version of axe-core used in test which raised issue
Needs Review Whether or not the potential issue needs manual review
IGT Which specific IGT was run to find issue (blank if not found by IGT)
Found By User who peformed test in which issue was raised
Test Title The title name of the test
Share URL The shared issue URL (only populated when issue or saved test explicitly shared)

Supported JSON Schema

The JSON issue export is an array of issue data with the following properties for each issue:

Property name Type Description
axeVersion string The version of axe-core used for the test in which the issue was raised.
createdAt string The date/time in which the issue was raised.
description string A description of the issue.
foundBy string User who performed the test in which the issue was raised.
help string Helpful information regarding the rule violated leading to issue.
helpUrl string A URL with help for the given rule.
igt string The name of the IGT in which the issue was rased (null if not found in IGT).
impact string The impact or severity of the issue.
isManual boolean Whether the issue was found manually (IGT) or not.
needsReview boolean Whether or not the potential issue needs manual review.
ruleId string The identifier for the accessibility rule associated with the issue.
selector array An array of CSS-Selectors to target the node associated with the violation. Read axe-core's documentation on selectors.
shareURL string The shared issue URL (only populated when issue or saved test explicitly shared).
source string The HTML source snippet of the issue element.
summary string Summary of issue.
tags array Array of string tags of metadata for the issue (categories, wcag checkpoint identifiers, etc.).
testName string The name of the saved test in which the issue was found.
testPageTitle string The title of the document in which the issue was found.
testUrl string The url of the page tested.

Saved test export

If you are looking for an export format that gives you a summary of all the testing that was done within a test record and what the outcome was of that testing, then this is the format for you. The JSON "Saved test and issues" export contains a complete breakdown of all the relevant data associated with a given saved test in the following way:

Property name Type Description
allIssues array Array of issue data (see above JSON issue schema).
axeVersion string The version of axe-core used for the test in which the issue was raised.
bestPracticesEnabled boolean Whether or not best practices are enabled for the saved test.
extensionVersion string The version of the extension used to perform the tests.
failedRules array An array of rule objects. See the rule object table below.
igtSummary array An array of IGT summary data. See the IGT summary object table below.
issueSummary object Issue summary data counts. See the issue summary object table below.
needsReview array An array of needs review issue data. See the needs review object table below.
remainingTestingSummary object Remaining testing summary data. See the remaining testing object table below.
standard string The WCAG Level used for the testing.
testingEndDate string The date/time in which the test was last updated.
testingStartDate string The date/time in which the test was first created.
url string The URL of the page tested.

Rule object

The rule object is used in the failedRules property of the saved test export. It contains the folllowing properties:

Property name Type Description
name string The name/id of the rule.
count number The number of times the rule failed.
mode string The mode in which the issue was found. Possible values are "automated" and "Manual".

IGT summary object

The IGT summary object is used in the igtSummary property of the saved test export. It contains the following properties:

Property name Type Description
name string The name/id of the IGT.
run boolean Whether or not the IGT was run at least once.
skipped string Whether or not the IGT was skipped.
tool string The name of the IGT.

Issue summary object

The issue summary object is used in the issueSummary property of the saved test export. It contains the following properties:

Property name Type Description
bestPractices number The total number of best practices found.
critical number The total number of "critical" (impact) issues found.
minor number The total number of "minor" (impact) issues found.
moderate number The total number of "moderate" (impact) issues found.
serious number The total number of "serious" (impact) issues found.
needsReview number The total number of needs review issues found.

Needs review object

The needs review object is used in the needsReview property of the saved test export. It contains the following properties:

Property name Type Description
count number The total number of times the given needs review issue was found.
mode string The mode in which the needs review issue was found. Possible values are "automated" and "Manual".
name string The name/id of the rule.

Remaining testing object

The remaining testing object is used in the remainingTestingSummary property of the saved test export. It contains the following properties:

Property name Type Description
run boolean Whether or not the remaining testing has been completed.