The Accessibility Tracker Platform lets you export your accessibility issues to a spreadsheet in a few clicks. From the project dashboard, select the issues you want to download, choose the export option, and the platform generates a structured file you can open in Excel or Google Sheets.
Exporting is useful when you need to share audit data with developers, leadership, or external vendors who do not have direct access to the platform. It also gives you a local backup of your WCAG conformance data at any point in a project.
| Detail | What to Know |
|---|---|
| Where to export | Project dashboard inside the Accessibility Tracker Platform |
| File format | Spreadsheet file compatible with Excel and Google Sheets |
| What is included | Issue descriptions, WCAG criteria, severity, status, and remediation notes |
| Who benefits | Developers, project managers, and teams collaborating on remediation |
| Time to export | Under a minute from start to download |
Why Export Accessibility Issues to a Spreadsheet?
Not everyone on a team has access to the Accessibility Tracker Platform. Developers may work inside a different project management tool. External vendors may need a standalone file they can reference without logging in.
A spreadsheet gives you a portable, filterable copy of all the issues an audit identified. You can sort by severity, filter by WCAG 2.1 AA or WCAG 2.2 AA criteria, and assign columns for developer ownership. Accessible.org clients often use exported spreadsheets to coordinate remediation across multiple teams.
How Do You Export Issues from the Platform?
Open your project inside the Accessibility Tracker Platform. Navigate to the issues view where all identified issues are listed with their WCAG criteria, severity ratings, and current status.
Select the issues you want to export. You can select all issues or filter by a specific status, such as open or in progress. Then click the export button. The platform generates the file and triggers a download.
The exported spreadsheet preserves the same data structure you see inside the platform: issue title, description, associated WCAG success criterion, severity, page or screen reference, and any remediation guidance attached to the issue.
What Data Comes Through in the Export?
Each row in the spreadsheet represents a single accessibility issue. The columns typically include the issue title and description, the WCAG success criterion (for example, 1.1.1 Non-text Content), the severity or priority rating, the affected page or screen URL, the current status (open, in progress, resolved), and any remediation notes or guidance.
This structure makes it easy to plug the data into your existing workflows. If your development team tracks work in Jira or a similar tool, the spreadsheet columns map cleanly to issue fields there.
When Should You Export?
There are a few natural points in a project where an export is valuable. Right after an audit report is uploaded is one. This gives your developers a full picture of the issues that were identified before remediation starts.
Mid-project exports are helpful for progress reporting. You can compare the current state of issues against the original count and show leadership how the project is tracking. And a final export before validation gives you a clean record of what was addressed.
Accessible.org recommends keeping at least one exported snapshot per project phase. These records are useful for ADA compliance documentation and for tracking conformance over time.
Using Exported Data for Remediation Planning
Once you have the spreadsheet, you can layer in your own columns. Many teams add a “Developer Assigned” column, a target completion date, and notes about dependencies. This turns the export into a lightweight remediation plan without needing a separate document.
The severity and WCAG criteria columns are especially useful for prioritization. Issues with higher severity ratings and those tied to core user flows should be addressed first. The platform’s Risk Factor and User Impact prioritization formulas are reflected in the severity data, so the spreadsheet carries that intelligence with it.
Sharing Spreadsheets with External Teams
If you work with an outside development team or a consulting partner, the exported spreadsheet is the cleanest way to get them the information they need. No login required. No platform walkthrough.
Upload the file to a shared drive, attach it to a project kickoff email, or import it directly into whatever tracking tool the vendor uses. The data is self-contained and structured consistently, which reduces back-and-forth questions about what each issue means.
Does the Spreadsheet Stay Synced with the Platform?
No. An export is a snapshot. Once you download the file, it reflects the state of your project at that moment. If issues are updated inside the Accessibility Tracker Platform after the export, those changes will not appear in the downloaded spreadsheet.
For ongoing collaboration where real-time status matters, working directly inside the platform is better. Use exports for reporting, handoffs, and archival purposes.
Can I export issues for a single page instead of the whole project?
Yes. Filter the issues view by page or screen before exporting. The platform will only include issues that match your current filter in the exported file.
What file format does the export use?
The Accessibility Tracker Platform exports to a spreadsheet format that opens in both Microsoft Excel and Google Sheets. You do not need any special software to view or edit the file.
Is the exported data enough to start remediation without platform access?
It is. Each issue includes the WCAG criterion, a description of the problem, the affected location, and remediation guidance. A developer with this information can begin addressing the issues immediately.
Exporting accessibility issues from the Accessibility Tracker Platform gives your team a flexible, portable record of exactly where a digital asset stands against WCAG conformance. Whether you need the data for developer handoffs, progress reports, or compliance documentation, the spreadsheet gets the information where it needs to go.
Contact Accessible.org to learn more about using the Accessibility Tracker Platform for your accessibility projects.
