Export Formats
Export a TestKase accessibility report as a PDF report or a CSV summary.
A completed report exports as a PDF summary or a CSV summary from the report header. Two more exports live elsewhere: the History tab exports the run list as CSV, and a consolidated report has its own PDF and CSV. None of them contains per-issue detail.
Best for: stakeholder handoffs, audit archives, printed reports.
A summary-level report, styled like the on-screen Summary tab and paginated for print (A4, page numbers in the footer). It contains:
- Accessibility score, plus the passed / failed / score-impact table per severity
- Issue summary by severity
- Affected pages (URL, score, issue count)
- Affected components (top 30 selectors by issue count)
- WCAG conformance summary
- Issues by category
- Needs-review and hidden-issue counts
The PDF does not contain the per-issue detail (rule ID, selector, HTML snippet, failure summary), and it does not contain the page snapshots — those live only in the web report. There is no table of contents.
PDF export works on Website Scanner reports. Reports saved from the Chrome Toolkit (Workflow Analyzer) export as CSV only — even though their Export menu still offers Export as PDF. That item calls the Website Scanner's PDF route with the analyzer report's id, so it either fails or returns an unrelated Website Scanner report of your own that happens to share the number. See Using the panel.
CSV
Best for: spreadsheets, quick roll-ups, sharing headline numbers with stakeholders.
The CSV is a multi-section summary of the report (not a per-issue dump). It contains four blocks, one after another in a single file:
- Scan Summary —
Name,Score,Total Issues,WCAG Version,Status,Date. - Issue Summary by Severity — one row per severity (
Severity,Count). - Rules Breakdown — per severity:
Severity,Passed,Failed,Score Impact. - Affected Pages — per scanned URL:
#,URL,Score,Issues.
CSV is UTF-8, comma-separated, and safe to open in Excel / Google Sheets / Numbers. It carries no byte-order mark, so a scan name with non-ASCII characters can render oddly in Excel on Windows — Google Sheets and Numbers are unaffected.
History CSV
Best for: tracking a scan's score across releases outside TestKase.
The Export CSV button on the report's History tab exports the run list, not the findings. Columns: SCAN #, DATE & TIME, TRIGGER, SCORE, ISSUES, Δ, STATUS, AUTHOR. Dates are rendered in your own timezone, so the file and the screen always agree.
Two things shape what you get:
- Tick runs first and the button becomes
Export N selected— otherwise you get every run in the current date range. - At most 200 runs are exported in one file. A scan with more history than that needs a narrower date range.
Consolidated report exports
A consolidated report exports as a PDF (same summary sections as a single-scan PDF, across the combined data) or as a CSV. The consolidated CSV adds an Included Scans block — ID, Name, Score for each scan in the roll-up — ahead of the usual severity, rules and affected-pages blocks.
The version comparison report has no export.
rule_id, selector, html_snippet, WCAG tags, etc.) for programmatic consumption and imports into other trackers. Today there is no full-detail export in any format: both the PDF and the CSV are summaries, and per-issue data is available only in the web report and via the API.When each is available
Both the PDF report and the CSV summary are available from the report header on completed scans. If an export button is disabled, a tooltip explains why (for example, the scan hasn't finished yet). See Plans and pricing and Scan limits.