Public documentation
Exports and local data
How evidence exports, diagnostics, local issue state, and previous scan data should be handled.
Export types
| Export | Contains | Primary use | Sensitivity |
|---|---|---|---|
| CSV issue export | Issue rows, classification, severity, source, selector, and review fields where available. | Ticket triage and spreadsheet review. | Can include page URLs, selectors, snippets, and issue text. |
| JSON evidence export | Structured scan evidence, provenance, review/advisory/limitation separation, diagnostics, and metadata. | Engineering handoff or repeatable evidence review. | Potentially high sensitivity because it preserves detailed evidence. |
| QA report HTML export | Structured review deliverable built from selected module context plus scan evidence, diagnostics, and screenshot where captured. | QA handoff for remediation and release review. | Can include page URLs, selectors, snippets, WCAG/POUR mappings, notes, diagnostics, and PNG screenshot data. |
| Diagnostics export | Runtime, permission, scan support, errors, limitation context, and contrast diagnostics where exported. | Support and reproduction of scanner behaviour. | Can reveal browser/runtime details and page context. |
| Local issue-state export/import | Reviewer workflow status and local triage state. | Move or restore local review state. | May reveal project workflow and page references. |
| Screen Reader Review export | Guided review observations and notes where visible. | Assistive technology review handoff. | Can include page structure and user notes. |
Local data lifecycle
- 1
Scan
Evidence is produced from the current page state.
- 2
Add module evidence when needed
Feature panels can add supported outputs to the QA report. Non-confirmed contrast review and unable-to-determine rows require explicit item-level selection.
- 3
Store temporarily
Issue state, history, contrast inspector review/report item state, workflow notes, or comparison data may be stored locally where supported.
- 4
Export if needed
The user chooses whether to create CSV, JSON, QA report HTML, diagnostics, or state files.
- 5
Share responsibly
Send exports only to authorised recipients.
- 6
Clear when done
Use clear local data controls when review evidence is no longer needed.
Export handling warning
After an export leaves the browser, A11Y Cat no longer controls retention, access, sharing, or deletion. Treat exported evidence according to your organisation's data-handling rules.