Exporting and sharing

Getting findings out of the portal and to whoever will fix them.

Your options#

All four are on every report.

Which format to use#

CSV for anyone who will fix things. One row per finding with the WCAG criterion, severity, selector, and description — paste it into your tracker and assign rows. This is the highest-leverage export.

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:

1. 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.
2. What the score does and doesn't mean. It is not a compliance certification.
3. 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.