Exporting and sharing
Getting findings out of the portal and to whoever will fix them.
Your options#
| Action | Cost | Best for |
|---|---|---|
| Export PDF | 1 credit | Clients, managers, anyone who needs a document |
| Export CSV | 1 credit | Developers; importing into Jira, Linear, or a spreadsheet |
| Download all issues | 1 credit per page | Every scanned page's issues in one spreadsheet, from the site's Overview |
| Conformance report | 10 credits a published version | Buyers, procurement and auditors: an Accessibility Conformance Report for the whole site, decided criterion by criterion — see conformance reports |
| 1 credit | Sending straight to a colleague | |
| Log defect | Free | Tracking a finding inside Zylyn |
Export PDF, Export CSV, Email and Log defect are on every report. Download all issues is on the Overview, on the Top open issues card: it shows the exact total and asks you to confirm before anything is charged. The conformance report has a screen of its own, Conformance report in the sidebar; its draft and draft PDF are free, and only publishing a version is charged.
Which format to use#
CSV for anyone who will fix things. One row per affected element (at most five per rule, with the rule's full count alongside) with the WCAG criterion, severity, the element's HTML and description — paste it into your tracker and assign rows. This is the highest-leverage export. Download all issues gives the same rows for every scanned page of the site in one file, each with its page address, scan date and element selector, open logged defects included; because rows are per element, the row count is not the dashboard's open-issue count.
PDF for anyone who will read rather than act. Formatted and readable, good for a client update or a compliance file. Bad as a work list: nobody wants to copy selectors out of a PDF.
Sharing with a client#
The honest framing matters here. If you hand a client a raw report, lead with:
- Which findings are actual WCAG failures, separated from best-practice items — see WCAG failures versus best practice. Reporting a total that mixes both overstates the problem.
- What the score does and doesn't mean. It is not a compliance certification.
- What still needs manual testing. Automated scanning covers 20–40% of WCAG criteria.
A client who is told "you have 23 issues and score 74%" panics. A client who is told "two real WCAG failures, both one-line template fixes, plus some structural improvements worth doing" acts.
Logging defects#
Log defect records a finding as tracked work inside Zylyn, at no credit cost. Useful when you want history in one place rather than exporting into an external tracker.
A note on privacy#
Reports contain fragments of your page markup, since that's what makes findings actionable. For public pages this is content anyone can view. For pages scanned via the browser extension, snippets can come from private screens — those reports are never given a public link and email addresses and long digit sequences are automatically redacted. Reports are still visible to everyone on your account, and to your managing agency if you have one.