Import an audit
An audit done by a tester, in-house or by an agency, already holds a lot of work: the problems it found and a result for each criterion. Import an audit brings that work into a site. Findings become issues, or join the issue the site already has for the same problem. Results become Review verdicts, named as the audit’s in every report.
Nothing is written until you have seen what each row will become.
Before you start
Section titled “Before you start”- A finished scan. An import is checked against the site’s latest completed scan, so a finding the scan already has joins that issue instead of making a second one.
- The right role. Owners, admins and members can import. See Team and roles.
- The audit as a spreadsheet or a VPAT. An Excel workbook (.xlsx), CSV, or a Word document (.docx) whose tables hold it, such as a VPAT or ACR: findings, criterion results, or both. Each file can be up to 10 MB. From Google Sheets, download it as Microsoft Excel; from Numbers, export it to Excel. An older .xls or .doc file, or one with a password, needs saving as .xlsx, .docx or CSV first. A report written as text rather than tables, or a PDF, can’t be imported yet.
Open a site, then Review in its sidebar, and choose Import an audit under Audits.
The template
Section titled “The template”Any column names work: the import matches them, and you can change each match. These are the names it reads as they are.
Findings, one row per problem:
| Column | What it holds |
|---|---|
| Reference | The audit’s own ID for the row, such as A-12. A second import of the same audit uses it to know a row is already in. |
| Criteria | One or more WCAG criteria, such as 1.4.3 or 3.3.1, 4.1.3. |
| Title | The problem in a line. |
| Description | What the tester saw. |
| Pages | The page or pages, separated by commas, semicolons or new lines. Leave it empty, or write “site-wide”, for a problem on every page. |
| Element | A CSS selector, or the element in words. |
| Severity | Critical, serious, moderate or minor, or the audit’s own words for them. |
| Status | Still a problem, or fixed. |
| Screenshot link | A web address for a screenshot. |
| Environment | The browser and assistive technology the row was tested with. |
Criteria results, one row per criterion, or per criterion and page:
| Column | What it holds |
|---|---|
| Criterion | The WCAG criterion. |
| Result | Pass, fail, not applicable or not tested. VPAT words work too: Supports is a pass, Partially Supports and Does Not Support are a fail, Not Evaluated is not tested. |
| Notes | How it was checked. |
| Page tested | The page the result is for. Several rows for one criterion combine into one result. |
Importing
Section titled “Importing”1. The audit. Name it as reports should, such as “Acme Audits, August 2026”, and add the assessor, the dates tested, the standard the audit used, what it was tested with and the pages it tested. Reports print all of these beside every verdict the audit brings in.
2. The file. Add the findings file, the criteria file, or both. A workbook with both on separate sheets needs adding once: the import reads the sheet that fits, and offers the other sheet for the other file. A cell that shows words over a link, such as “Screenshot”, imports the link, and a page merged down beside several findings goes with each of them. Keep a copy of the file with the audit stores it in your workspace’s region, and it is deleted with the site. Untick it if the file holds anything you would rather not keep.
Screenshots are optional: a ZIP of them, or the images themselves
(PNG, JPEG, GIF, WebP or PDF, up to 10 MB each), each named by its
finding’s reference, such as A-12.png, A-12 (2).png or a folder
named A-12. Once the import is done, each goes on the issue its
finding became or joined. A reference that is only a number, such as
12, needs to start the file’s name.
3. Columns. Check what each column imports as, and what each severity, status and result word means. Files from Excel on Windows, with semicolons or title rows above the header, are read as they are; change the separator, or the sheet, or the header row if a guess is wrong. Before you can continue, the import asks:
- which column holds the reference, or to number the rows R1, R2, R3;
- what each other domain in the file is: a copy of this site, such as staging, matched by path, or a different site, such as a payment page, imported without matching.
A cell that looks like a login is pointed out, with the choice not to keep a copy of the file.
4. Check. Every row says what it will become. Change any row; it stays where it is, and the change is announced. Import waits while a row needs a choice. Screenshots are counted on their rows, and any that name no finding are listed.
5. Done. What was created, joined, recorded, kept and left out, with Undo.
A VPAT
Section titled “A VPAT”Add a VPAT or ACR in Word as the criteria results. Its WCAG tables, one for each level, are read together, and its Section 508 and EN 301 549 chapter tables are left out; choose a single table under Table in the next step if you need to. Where a row answers for several kinds of product, such as “Web: Supports” and “Electronic Docs: Not Applicable”, the import takes the Web answer, and the VPAT’s own words are kept for your VPAT.
A VPAT has no findings, so a Partially Supports or Does Not Support row waits until the site has a finding on that criterion. A Supports row whose remarks are empty waits for a note on how it was checked. In the check step you can write one note, such as the VPAT’s evaluation methods, and use it for every row that needs one. Name whoever wrote the VPAT as the assessor, since reports print the assessor beside every verdict it brings in, and say so when it is the product’s own team.
How findings are matched
Section titled “How findings are matched”- A row joins an issue that has the same criterion and element, on the same page or with the row site-wide. Its details go on the issue as a comment, and a scan finding that waited for a person to confirm it is confirmed: the audit found it.
- A row with only the same criterion and page is a possible match. Tick the issue it is, or create a new one. View shows the issue beside the row, field by field.
- An issue your team dismissed is offered, never joined on its own. Joining lifts a dismissal of that issue only; a wider one stays.
- Anything else creates an issue, marked as from the audit, with a priority from its severity, so it sorts with the scan’s issues.
- A row the file calls fixed is not imported on a first import, unless you choose to keep a record of it.
- A row naming a criterion outside the audit’s standard, an EN 301 549 clause other than 9, or a Section 508 number is not imported, and says why.
How results are recorded
Section titled “How results are recorded”Each result is recorded with the same checks as Review, as method “imported”. Some wait instead, with the reason:
- A fail needs a finding: in the file, or confirmed on the site.
- A pass or not applicable needs a note on how it was checked.
- A pass waits while the site has open findings on the criterion, or ones waiting to be confirmed, or the file has findings on it.
- Not applicable waits while the latest scan finds what the criterion is about.
- A criterion assigned to someone else waits for them.
- A criterion answered in Review keeps its answer unless you choose the audit’s.
A criterion with an imported verdict leaves Next up and sessions. Its checks come back only if something contradicts it: a new finding, the subject appearing on a page, or a fix to retest.
The audit’s page
Section titled “The audit’s page”Every audit is listed under Audits in Review, with the number of rows still waiting. Its page shows what the audit is, each finding with the issue it became, where that issue stands now and what last moved it, and the verdicts it recorded. From there:
- Waiting rows. Each says where it stands now. Record it once its reason has cleared, writing the note if it needs one, or set it aside.
- Retest. The audit’s open findings, page by page, to check on the site as it is now. Fixed verifies the issue as a retest; Still a problem reopens one marked fixed, or notes it on one still open. A page not found in the latest scan is named.
- Retest report. A PDF or HTML document to hand over: where each of the audit’s findings stands now, and every retest since the import. Fixed problems say how they were confirmed: by a retest here, by the audit’s own retest, or because the scan no longer finds them. A fix nobody has retested is named as claimed, not confirmed.
- Import a newer file. For a retest or a later version of the same audit. Rows new to it are imported; rows already in it stay as they are. A row the file now calls fixed can mark its issue fixed, to retest here, or verified by the audit’s retest. A row that joined an issue the scan found is left to the scan, which closes it once the problem is gone.
- Undo. Archives the issues the import created, removes the screenshots it added, deletes its comments, puts back the scan findings it confirmed and the dismissals it lifted, sets its verdicts back and reopens what a newer file marked fixed. Anything someone has changed since is left as it is, and the undo says what it left.
In reports
Section titled “In reports”The VPAT, readiness reports and accessibility statement name the audit, its assessor, its dates and who imported it for every verdict it brought in. The VPAT keeps the file’s own wording, such as Does Not Support, and a note that refers to the file’s references names the issues instead. Problems verified by an audit’s retest are counted apart from those verified by a retest here.
One import sends one notification, to the people watching the issues it commented on. The weekly digest counts imported issues separately, and nothing is sent to a tracker such as Jira or Linear on its own.