To import audit findings from a CSV file into the Accessibility Tracker Platform, format your spreadsheet to match the required column structure, save it as a CSV, then upload it through the import option inside your project. Each row becomes a tracked issue with fields for the WCAG criterion, severity, page or screen, and description. Once the upload completes, every finding is mapped to its project and ready for prioritization, assignment, and remediation. The process turns a static audit report into a live workspace your team can act on.
| Step | What Happens |
|---|---|
| Prepare CSV | Match columns to the platform's expected fields |
| Upload file | Use the import option inside your project |
| Review mapping | Confirm columns align with platform fields |
| Confirm import | Issues populate the project as tracked items |
| Begin work | Prioritize, assign, and remediate from the dashboard |
Why Import Findings Instead of Re-entering Them?
Most audit reports are delivered as spreadsheets. Manually retyping every issue into a tracking tool wastes hours and introduces transcription errors.
A CSV import moves the entire report into the Accessibility Tracker Platform in one action. Every finding keeps its severity, WCAG reference, and description intact, and your team can start working immediately.
What Should Your CSV File Contain?
The CSV should mirror the structure of a standard audit report. At minimum, include columns for the issue description, WCAG success criterion, severity rating, and the page or screen where the issue appears.
Additional columns like recommended fixes, code snippets, or screenshots paths can be included when available. The cleaner the source file, the faster the import maps correctly.
If your auditor delivered findings in a different column order or with custom labels, you can rearrange the spreadsheet before saving it as CSV. The goal is one row per issue with consistent field names across the file.
How Does the Upload Process Work?
Inside your project, open the import option and select your CSV file. The platform reads the file and shows a preview of how columns will map to its fields.
Review the mapping. If a column needs reassignment, adjust it before confirming. Once you approve the mapping, the import runs and every row becomes a tracked issue inside the project.
The whole process can be completed in a few minutes for most audit reports, even ones with several hundred findings.
What Happens After the Import?
Once findings are imported, they appear as individual items in your project dashboard. From there you can apply Risk Factor or User Impact prioritization formulas, assign issues to developers, attach notes, and track status as work progresses.
Each issue carries its WCAG reference, so your team always knows which criterion they are working against. As remediation happens, status updates roll up into progress views that show how close the project is to WCAG 2.1 AA or WCAG 2.2 AA conformance.
This is where a CSV import pays off. The audit report stops being a static document and becomes a live record of remediation work.
Can You Import Findings From Any Auditor?
Yes. The Accessibility Tracker Platform accepts CSV files regardless of which auditor produced the report. As long as the columns can be mapped to the platform's fields, the import works.
That makes the platform useful for teams who use multiple vendors, inherit audit reports from prior projects, or want to consolidate findings from several digital assets into one workspace.
FAQs
How long does a CSV import take?
For most audit reports, the upload and mapping review takes about 5 to 10 minutes. Larger reports with several hundred rows may take slightly longer to review, but the actual import runs quickly once you confirm the column mapping.
What if my CSV has columns the platform does not recognize?
You can skip unmapped columns during the import review or rename them in the source file before uploading. Only the core fields, issue description, WCAG criterion, severity, and location, need to map for the import to complete.
Can I import findings from multiple audits into the same project?
Yes. You can conduct separate imports as new findings come in, whether from follow-up audits, additional pages, or different digital assets. Each import adds to the existing record without overwriting prior issues.
Do imported findings include AI guidance for remediation?
Once findings are inside the platform, AI features can suggest remediation approaches and help your team work through issues faster. Accessibility Tracker AI is part of what makes the platform's workflow more efficient than tracking issues in a static spreadsheet.
Importing a CSV is the fastest path from a delivered audit report to active remediation. The findings live where the work happens, and your team has everything it needs to drive a project toward conformance.
Ready to move your audit findings into a live workspace? Contact Accessibility Tracker to learn more.