Conformance reports

A conformance report says, criterion by criterion, how well a website meets WCAG. Buyers, procurement teams and auditors ask for one. Zylyn builds the draft from every page's latest scan, you decide each criterion, and the portal publishes it as an accessible PDF.

Where to find it#

• Conformance report in the sidebar, under Monitor
• The Conformance report button at the top of the Pages screen
• The Open the report card beside any tracked page's report
• The footnote under the score on the Overview

It needs a tracked site with at least one scored page. Until then the screen says "Scan your pages first" and offers Scan all pages. Scans not attached to a site (ad-hoc scans) never feed a report: track the site first.

How the draft is built#

There is one working draft per site. Opening the screen for the first time builds it from the latest completed scan of every tracked page — the same pages the Overview and the Pages list count. Scans made with the browser extension count; PDF documents don't, as they are checked against a different standard.

For each of WCAG's success criteria the draft gathers the evidence: the automated rules that failed (with the pages and the number of elements), the defects you logged by hand, the checks the scanner left for manual review, and whether any automated rule tests the criterion at all. From that it suggests a conformance level and drafts the remark:

Three rules behind the table:

• Does Not Support and Not Applicable are never suggested. Both are judgements about the product, not page counts: you downgrade when you know better, and you mark a criterion not applicable — and say why — when nothing on the site is subject to it.
• "Nothing found" proves nothing while a page predates the findings index. If any included page was last scanned before Zylyn kept findings per rule, a notice says so, no row is suggested Supports, and the remark asks you to re-scan those pages and refresh the evidence.
• Automated checks cover only part of WCAG. Automated rules exist for roughly a third of the Level A and AA criteria, and even those are tested only in part. That is why every row needs a person's decision, and why the document says it was reviewed criterion by criterion.

Deciding each criterion#

The rows are listed by level — Level A, Level AA, and Level AAA when you include it. Each row's header shows its number and name, its status and what the evidence found. Open a row to decide it:

• The suggestion, with Use the suggestion. Accept every suggestion at the top takes every suggestion the undecided rows have in one go; rows you decided by hand are never touched.
• The conformance level: the template's five terms. Not Evaluated is offered on Level AAA rows only, as the template requires. Clear decision puts a row back to undecided.
• Remarks and explanations: the text that goes into the document. Zylyn drafts it from the evidence; change it as you like, and Use the generated text brings the draft back. A remark is required for Partially Supports, Does Not Support and Not Applicable, because the template asks for the reason.
• The evidence: each failed rule with the pages it was seen on, linked to their reports; the logged defects; the checks left for manual review; which automated rules test the criterion; and the W3C's own explanation of it.

Every change saves on its own: a level as you choose it, a remark when you leave the box. The filters above the rows (Needs your decision, With issues, Needs review, Evidence changed, Decided) narrow the lists, and Where the draft stands says how many rows are still undecided.

The report details#

The Report details card holds the document's header fields, pre-filled from the site: the company (named in the title), the name of the product and its version ("as scanned 2–21 October 2026", following the scans until you change it), contact information (the account owner's email, which goes to whoever receives the document), the product description, your notes, your manual testing (what you tested by hand, with which assistive technology and browsers), and an optional legal disclaimer. Each field saves when you leave it.

The edition is WCAG 2.2 by default; 2.1 leaves out the nine criteria 2.2 added. Level AAA is off by default, because the scanner tests five of its 31 criteria and most AAA rows can only say Not Evaluated; switching it on adds the rows, and decisions survive switching it off and on. The report date is set when you publish.

New scans and refreshing the evidence#

New scans never change a draft by themselves. When the site has been scanned since the draft was built, a notice says so and Refresh evidence rebuilds the evidence and the suggestions from the latest scans. Decisions stay. A remark you edited is never overwritten; one you left as drafted follows the new evidence.

A decided row whose evidence changed — a new failed rule, a new logged defect, or a criterion that moved between "issues found" and "nothing found" — is flagged Evidence changed. Read the new evidence, then either Confirm as it stands or change the decision. Nothing else clears the flag, and the report can't be published while a flagged row stands, so a published report never shows Supports beside evidence that says otherwise.

Publishing a version#

Publishing needs every row of the included levels decided, a remark wherever the level is not Supports, no Not Evaluated outside Level AAA, and no row still flagged. Publish version opens a dialog that says what still stands in the way, or shows what the version will hold: its number (and the version it supersedes), the edition, how many pages the evidence covers, the credits and your balance after, and the report date — today unless the report is dated otherwise.

• A version is frozen as it stands, with its own PDF. It is listed under Published versions with its date, edition and who published it, and the PDF can be downloaded again any time, free: the same file every time.
• Edit the draft, refresh the evidence, and publish again for the next version; its Notes say which version it supersedes. Publishing again with nothing changed is refused, so a double click or a lost answer never makes a twin.
• Download draft PDF is free at any time. The draft is watermarked DRAFT on every page and says it is not a published report.
• Anyone on the account can publish, like any export. A client user's publish bills the agency's pool. Admins are never charged.

What the document contains#

The document follows the template's structure and nothing is added to it: the title "[Company] Accessibility Conformance Report", the WCAG edition line and "(Based on VPAT® Version 2.5Rev)"; the header fields; the notes, after which Zylyn adds how many tracked pages the automated testing covered, any level not evaluated, what the version supersedes, and a disclaimer that a Supports resting on automated checks alone is not a guarantee; the evaluation methods — a fixed paragraph naming the automated rules engine, the pages and the scan window, then your manual-testing paragraph; the applicable standards; the template's terms; one table per level with every criterion, its conformance level and its remark; and the legal disclaimer when you gave one.

The PDF is tagged (PDF/UA), so it reads properly with a screen reader. An agency's white-label logo appears when one is set; otherwise the company's name stands in its place and a small "Prepared with Zylyn" line sits in the footer. The template's service-mark line for ITI is printed on every page, as its rules require.

What it costs#

If the document can't be made after you publish, the credits are returned and no version is kept. See credits and plans for every other cost.

Related#

• Reading your report — what automated scanning can and cannot find
• Exporting and sharing — the other ways findings leave the portal
• Enterprise & governance — conformance reports reviewed by a specialist before release
• Glossary — VPAT, ACR and the WCAG levels in plain English