Reports
Every document is built from two things: the verdicts your team records in Review, and the latest scan. None of them claims more than those two sources support, and none of them is a certification.
Open Reports in the sidebar. Each site has a card listing its documents. Inside a site, Report in its sidebar shows the same documents as cards, each with when to use it:
| Document | What it is for | Plans |
|---|---|---|
| Progress report | One page to forward: what the review has found, fixed and tested, and what is left | Every plan |
| Readiness reports · UK, US, EU | Where the site stands against each region’s law, criterion by criterion, with the evidence | Every plan |
| Accessibility statement | The statement you publish with your site | Every plan |
| Accessibility status page | A public page: when the site was last scanned and the claim the results support | Every plan |
| VPAT | The Accessibility Conformance Report (ACR) procurement teams ask for | Pro and Enterprise |
| Evidence pack | The documents above in one zip, with a CSV of open issues | Every plan (the VPAT only on Pro and Enterprise) |
If a scan finishes, or a verdict is recorded in Review, after you save a statement or a VPAT, its row shows Out of date, with a Regenerate link. What is still to check opens the criteria Review is still waiting on.
Who can do what
Section titled “Who can do what”| Task | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| Read the statement and the VPAT | Yes | Yes | Yes | Yes |
| Generate the Progress report, readiness reports and the evidence pack | Yes | Yes | Yes | No |
| Preview the status page | Yes | Yes | Yes | No |
| Draft, edit and export the statement and the VPAT | Yes | Yes | No | No |
| Publish public pages and answer access requests | Yes | Yes | No | No |
Progress report
Section titled “Progress report”The numbers from What this review has done as a single page, in PDF or HTML, with your workspace’s logo and colour. It says how each number is counted, so someone who has never seen the product can read it. It reports work done: it is not a certification and makes no conformance claim. It names who signed the evaluation, or says Draft if nobody has or the review has changed since.
What a scan can settle, and what it cannot
Section titled “What a scan can settle, and what it cannot”The documents treat scan results differently, on purpose: a procurement document and a public status page answer different questions.
| A criterion that is… | Readiness reports | Statement (full claim) | VPAT |
|---|---|---|---|
| Passed by a person in Review | Pass | Settled | Supports |
| Clean on the scan, fully covered by it, no verdict | Not assessed, with a note that the scan checked it | Settled | Not Evaluated |
| Clean on the scan, but covered only in part | Not assessed, naming the part not checked | Still to check | Not Evaluated |
| Nothing to test on the scanned pages, no verdict | Not assessed, with what the scan found | Still to check | Not Evaluated |
| Failed by a person | Fail | Blocks a full claim | Partially Supports |
| Not checked yet | Not assessed | Still to check | Not Evaluated |
The status page says the same in its own words, criterion by criterion: Passed, checked by a person, Passed, accepted from the scan’s suggestion (every answer accepted a suggestion without its check being opened), Passed, settled by the scan, Partly checked by the scan, Nothing to test on the monitored pages, Fails or Not checked yet. Its count of settled criteria uses the same rule as a full claim, so a criterion with nothing to test counts as waiting until a person records Not applicable for it in Review. The scan only knows about the pages it reached: not pages past a page limit, not pages behind a sign-in, and not code a page adds after it loads.
In short, the readiness reports and the VPAT count only what a person recorded. A clean scan supports a full conformance claim only for the criteria a machine can check completely; every other criterion needs a person’s verdict. How we test lists which criteria a scan can settle on its own.
Readiness reports: UK, US and EU
Section titled “Readiness reports: UK, US and EU”Three reports, one for each region, built from the same verdicts:
| Report | Framed for | Scope |
|---|---|---|
| UK | The Equality Act 2010, the Disability Discrimination Act 1995 in Northern Ireland and the public sector accessibility regulations | WCAG 2.2 Levels A and AA |
| US | Section 508 and the ADA | WCAG 2.1 Levels A and AA |
| EU | The European Accessibility Act | EN 301 549 clause 9 (WCAG 2.1 Levels A and AA) |
Each report uses its own scope, whatever standard the site is set to day to day. Each covers web content only, and says so.
The UK report reads WCAG 2.2 A and AA because that is what GOV.UK guidance sets for public sector websites and what the Government Digital Service monitors against. If the site’s Review works to WCAG 2.1, Review has not asked about the six criteria WCAG 2.2 added at those levels: the report lists them as not assessed and says so. To have Review ask them, set the site’s Primary standard to WCAG 2.2 Level AA in its settings.
Making one
Section titled “Making one”- In Reports, choose Generate on the site’s Readiness reports · UK, US, EU row. In Review, Report then Export opens the same dialog.
- Choose the Regulation.
- Tick the box to confirm you understand the document describes the current assessment state and is not a certification.
- Choose Generate preview, then Download HTML or Download PDF.
Reports are built fresh each time, so they always reflect the latest verdicts and scan.
What is in it
Section titled “What is in it”- Cover: the service and its URL, your workspace as the provider, the standard and the date.
- Summary: how many criteria have a recorded assessment (passes, fails and not applicable), how many are unassessed or need reassessment, and the open critical and serious issues.
- Assessment methodology: the automated testing, the human assessment, the sample of pages (in WCAG-EM terms) and the linked documents.
- Per-criterion assessment: a table for each WCAG principle, with the recorded outcome, the evidence and outstanding work, who assessed it and when, and the reviewer’s notes.
- Evidence index: files and links attached to criteria in Review, the review history, the problems reviewers logged (with what they tested with: browser, assistive technology and platform), and the retests of problems marked fixed.
- Known non-conformities: every criterion with a Fails verdict or open issues.
- Accompanying documentation: whether a statement and a VPAT exist, and when they were prepared. The statement’s claim is given as its public page shows it: a full claim that no longer holds is described as being reassessed, never repeated.
A recorded verdict is marked requires reassessment when something has changed since it was given: new issues on the criterion, a failed check, what the criterion is about appearing on the site, a fix waiting for a retest, or a Passes with open findings under it, for example. A verdict from the guided checks also needs reassessment when its checks are rewritten or answered after it, because it rests on them. A verdict recorded by your own method, or imported from an audit, rests on its note instead, so rewritten checks alone do not put it in question.
Linked documents
Section titled “Linked documents”The scan notes the PDF, Word, Excel, PowerPoint and similar files your pages link to, by the file name in each link. It does not open or test them. The reports say how many there are and what the evaluation did with them, which you choose in Review’s Report view, under Sample: Not assessed (the default), Out of scope (with a reason, such as published by third parties) or Assessed separately (with a note on how). The statement puts the same sentence in the right section. While they are Not assessed, neither the statement nor the VPAT can claim full conformance (see A full conformance claim).
Retests
Section titled “Retests”For problems logged in Review and later marked fixed, the reports say how many were verified by a retest, how many were marked verified without one, how many were reopened, and which are still waiting. Issues the scan found are verified by scans instead, and are not counted here.
Accessibility statement
Section titled “Accessibility statement”The statement comes in two formats, chosen under Statement format:
- W3C model (the default): what you do to support accessibility, your conformance status, known limitations, how to give feedback and the enforcement procedure.
- GOV.UK model, for UK public sector bodies: the model accessibility statement, with the wording GOV.UK says must not be changed. Choose Great Britain or Northern Ireland for the enforcement procedure. See The GOV.UK model.
- In Reports, choose Draft on the site’s Accessibility statement row (once the site has a completed scan). The editor has two tabs, Statement and VPAT / Conformance.
- Fill in the Factual fields. Legal entity name, contact email and the date it was prepared are required; phone, contact URL, assessment approach, technologies, a feedback response target and (in the W3C model) an enforcement body URL are optional. They appear in the statement exactly as you type them.
- Choose the Conformance claim: Partially conforms (the default), Fully conforms or Does not conform. In the GOV.UK model it is the Compliance status: Partially compliant, Fully compliant or Not compliant.
- Choose Generate draft. AI writes the introduction, measures, conformance summary and known limitations from your scan and Review; then every criterion with a Fails verdict, how many criteria are still to be checked by a person, and what was done with linked documents are added word for word.
- Read every claim and edit any block of the prose. Save changes (under the factual fields or under the prose) saves the factual fields, the format and your edits together.
- Tick the confirmation, and choose Export PDF, Export HTML or Export Markdown.
The GOV.UK model
Section titled “The GOV.UK model”The statement is laid out in the model’s order: who runs the website, how accessible it is, feedback and contact information, the enforcement procedure, technical information with the compliance status, non-accessible content, what you are doing to improve, and how the statement was prepared. These are filled in for you, word for word:
- the compliance status: “This website is fully compliant”, “partially compliant … due to the non-compliances listed below” or “not compliant … The non-compliances are listed below”, with the Web Content Accessibility Guidelines version and AA standard;
- the enforcement procedure: the Equality and Human Rights Commission and the Equality Advisory and Support Service, or for a body in Northern Ireland the Equality Commission for Northern Ireland, with a link;
- the commitment under the 2018 regulations, the statement’s scope, and when it was prepared and last reviewed (the export date, or on the hosted page the last time it was saved or exported).
Non-compliance with the accessibility regulations lists the known limitations, including every criterion with a Fails verdict in Review. The statement never lists disproportionate burden, because that is your own assessment: if you have made one, add it to the exported statement. Content outside the regulations’ scope is listed only for the linked documents you mark in Review’s Evaluation as published before 23 September 2018 and not essential to your services: they go under the model’s Content that’s not within the scope of the accessibility regulations heading, with PDFs and other documents under it, once the prose is regenerated. Add any other exempt content yourself. A website that is fully compliant has no non-accessible content section, unless it has those documents.
GOV.UK guidance asks public sector bodies to test against WCAG 2.2 AA. The statement names the WCAG version of the site’s standard, because that is what was tested; the editor warns when it is not 2.2. Set the site’s Primary standard to WCAG 2.2 Level AA, then regenerate the prose. The GOV.UK model needs a WCAG Level AA standard: a Level A standard is refused.
A full conformance claim
Section titled “A full conformance claim”Fully conforms (or Fully compliant) is refused, with the reason, while any of these is true:
- the latest scan has open issues in scope;
- a criterion has a Fails verdict in Review;
- a criterion is still to be checked: every criterion must be passed by a person or settled by the scan;
- the latest scan’s pages link to documents that are still Not assessed: in Review’s Report view, under Sample, choose Out of scope (with its reason) or Assessed separately. A scan that found no documents, or one from before the scan looked for them, does not hold the claim back.
A partial claim, or a claim that the site does not conform, is always allowed.
Keeping it current
Section titled “Keeping it current”The statement’s wording is not rewritten by itself. When a scan finishes, or a verdict is recorded, after you saved it, Reports marks it Out of date and the editor says what changed. The editor also says when the choice for linked documents changed after you saved it and the statement does not say it yet: the statement keeps the choice it was generated with. Choose Regenerate prose to bring it in.
Hosting it
Section titled “Hosting it”Under Public pages in the editor, set a Page slug, tick Publish this statement publicly. (you can once the statement is complete) and choose Save public pages. The statement is served at:
https://app.theaccessibility.company/statement/<workspace handle>/<slug>It shows your latest saved statement. There is a badge snippet to copy, to link to it from your own site. If a full conformance claim stops holding (a new issue, say, a Fails verdict, or linked documents that are not assessed), the hosted page withholds the claim and says it is being reassessed until you update the statement.
Accessibility status page
Section titled “Accessibility status page”The status page shows anyone how the site is looked after: when it was last scanned and how often, how the site is tested, and the claim the results support under the site’s own standard and under the standards used in the UK (WCAG 2.2 AA), the US (WCAG 2.1 AA) and the EU (EN 301 549). It needs no statement.
Turn it on in the same Public pages panel: tick Publish the
Accessibility status page. It is served at
/status/<workspace handle>/<slug>, with a badge of its own.
Preview status page shows it as it stands, published or not.
- The claim for each standard is Fully conforms only when a full claim would be allowed (see above), Partially conforms when a criterion fails, and Assessment in progress otherwise.
- Every criterion, while List every criterion on the status page is ticked (it is by default): where each one stands (passed by a person, settled by the scan, fails, not checked yet, and so on) and since when. It is all or nothing: failing and unchecked criteria are listed with the passes.
- No scores and no issue counts.
Request access
Section titled “Request access”The status page lists the documents a visitor can ask for: the three readiness reports and, on Pro and Enterprise once a VPAT has been generated, the ACR. The visitor gives their name, work email and organisation, and optionally why they need them. Nothing is shared until you approve.
Owners and admins are emailed each request and decide under Access requests in the statement editor: choose what to Share and how long the Link works for (7, 30 or 90 days), then Approve and email the link; or Decline. The link renders each document fresh when it is opened, and you can revoke it at any time.
Report a problem
Section titled “Report a problem”Every published page has a Report a problem button. By default it opens an email to your statement’s contact address. Tick Take reports on a form to use a form instead: the visitor says what happened and, if they like, which page, what they were using (a screen reader, keyboard only, zoom) and how to reach them.
Reports wait in the site’s Visitor reports, under Fix, and owners and admins are emailed each one. Every site’s reports are together under Issues, in Visitor reports, in the workspace’s sidebar. File as issue turns a report into an issue, without the reporter’s name or email; Close, no issue closes it. Nothing a visitor sends is published, and a report changes nothing in your documents until someone files it.
VPAT 2.5 / ACR
Section titled “VPAT 2.5 / ACR”On Pro and Enterprise, owners and admins can generate an Accessibility Conformance Report based on VPAT® 2.5: choose Generate on the site’s VPAT row, which opens the VPAT / Conformance tab of the editor.
If the workspace moves to a plan without the VPAT, a VPAT made earlier can still be read and discarded. It cannot be edited, regenerated, exported, shared from an access request or put in the evidence pack until you upgrade again.
The edition follows the site’s standard: the WCAG Edition for a WCAG standard, the Revised Section 508 Edition for Section 508, and the EU (EN 301 549) Edition for EN 301 549. It covers Levels A and AA.
A report on WCAG 2.0 or 2.1 (Section 508 and EN 301 549 included) lists 4.1.1 Parsing as Supports, in the editor and the export alike, with a remark citing W3C’s September 2023 errata, which say it is always satisfied for content using HTML or XML. WCAG 2.2 removed it, so a WCAG 2.2 report leaves it out.
How verdicts become conformance levels
Section titled “How verdicts become conformance levels”| In Review | In the VPAT |
|---|---|
| Passes | Supports |
| Fails | Partially Supports. You can change it to Does Not Support, but to nothing else. |
| Not applicable | Not Applicable |
| Passes or Not applicable that needs reassessment | Treated as no verdict, so never Supports |
| No verdict, with open issues | Partially Supports |
| No verdict, clean scan | Not Evaluated |
A Fails reads Partially Supports because VPAT 2.5 keeps Does Not Support for when most of the product’s functionality fails the criterion, and a Fails in Review usually rests on one failing instance on a sampled page. A scan alone never makes a row Supports.
ITI’s template keeps Not Evaluated for Level AAA criteria. The VPAT also uses it for a Level A or AA criterion with no current verdict, because a scan alone does not establish conformance, and says so in its Terms and Notes.
Remarks
Section titled “Remarks”Every row gets a remark written for you: what the guided checks found, the reviewer’s note, or how many open findings affect it and how many of those a person confirmed. “Confirmed” only ever means a person did: a finding the scan reports is open, not confirmed. You can edit any remark, and your edits survive when you regenerate the table. On export, each row also says what it rests on: for example “Verdict recorded in Review: Passes, by … on …, from 6 guided checks on 4 pages”, or, with no verdict, “Scan draft. No verdict is recorded in Review.” (4.1.1 Parsing says that W3C’s errata settle it instead.) Where the scan or AI proposed answers that a reviewer accepted, the row says how many, and how many of those checks were opened first: “: 6 accepted from the scan, 0 opened”. Answers given before opening was recorded say only that they were accepted.
Tick the confirmation, then choose Export PDF, Export HTML or Export Markdown. If the header’s conformance claim is Fully conforms, the same rule as the statement’s applies.
Evidence pack
Section titled “Evidence pack”Download on the site’s Evidence pack row gives a zip of the three readiness reports, the statement (once it can be exported), the VPAT (on Pro and Enterprise), a CSV of open issues and a README. The documents are HTML. Screenshots and raw scan results are not in it: export an Evidence bundle (zip) for a scan under Export history (see below).
Scan exports
Section titled “Scan exports”Under Export history on the Reports page, Create Export saves one scan’s results as a CSV of findings or an Evidence bundle (zip). Each export can be downloaded for 7 days.