- Examples
- 5
- Checked
- 2026-11-05
Example Accessibility Conformance Reports
Five filled-in ACRs for invented products, one for each common situation: a WCAG 2.2 web app, an EU store against EN 301 549, a US course portal under Section 508, a city permit portal on the INT edition and a documentation site limited to WCAG 2.1. Every product name is fictional; read them for the shape of the remarks, not as a description of anything real.
Every product, company and finding on these pages is invented. They show how a filled report reads, not how any real product performs.
B2B invoicing web app
The two Does Not Support rows come from WCAG 2.2 additions (dragging and accessible authentication). A report that claimed 2.2 without those rows, or answered them Supports from an automated scan, would be caught by the first buyer who tried to reorder an invoice line without a mouse.
Brindlecroft Home online store (fictional product)
EU (EN 301 549)
Online store
Clause 9 of EN 301 549 is answered through the WCAG tables, so most of the work is the WCAG 2.1 rows; the EN 301 549 clauses that matter for a store are 10 (the PDFs) and 12 (support). The Notes say which version of EN 301 549 the report covers, because V4.1.1 now exists and a European buyer may ask about it.
Quillstone Course Portal 9.1 (fictional product)
Revised Section 508
University course portal
A course portal is also an authoring tool, so section 504 applies and the PDF export becomes a Section 508 finding. The report does not claim the 501.1 exception for web applications, because that exception depends on full WCAG 2.0 A and AA conformance, which the portal does not yet have.
Ostervale Permits 3.6 (fictional product)
International (INT)
City permit portal
In the INT edition one set of WCAG rows answers three standards, and the rows marked 2.2 only do not apply to Section 508 or EN 301 549 V3.2.1. The failures here are all in one place, the help videos, which shows how a single content gap can account for every Does Not Support in an otherwise solid report.
Documentation website
A report may leave out the WCAG 2.2 rows if it says it covers 2.0 and 2.1 only, as the template allows. It then has to say so plainly, because a buyer asking about WCAG 2.2 will see the gap at once. Not Applicable is used only where the remark can say why.