Example deliverable
Example: Partial-Compliance-Analysis Report
This sample report shows the structure of a Partial-Compliance-Analysis, the format ADA Site Monitor delivers after testing a website against WCAG 2.1 Level AA. The entity below is fictional: out of respect and privacy we never publish a client's name, so no real report ever appears on this site. The full interactive example is being prepared and will replace this outline.
Sources
What does the sample report open with?
A one-page summary an administrator can read in two minutes: the properties tested, the scan date, the count of verified findings by severity, and the three fixes that matter most. Every number on the page is tied to a dated scan, never an estimate.
In detail
| Section | What it contains | Written for |
|---|---|---|
| Executive summary | Scope, scan date, finding counts by severity, top priorities | The administrator who owns the obligation |
| Property inventory | Every site, portal and document library in scope | Both readers |
| Verified findings | Each defect tied to its URL and WCAG success criterion, with plain-language remediation guidance | The IT staff or vendor doing the fixing |
| Priority order | Findings ranked by user impact and exposure | Whoever plans the work |
| Found / Verified record | The dated history: when each issue was found, and when a later scan verified the fix | The file |
What does a single finding look like?
Like this, for a fictional "City of Example" permit page:
Finding 14 · WCAG 1.4.3 Contrast (Minimum) · Level AA
Page: https://example.gov/permits/ · Found 06-03-2026 · Status: Verified fixed 07-02-2026
The gray help text under the "Parcel number" field measures 2.9:1 against its background; the standard requires 4.5:1 for text this size. Residents with low vision cannot reliably read the instruction that explains the required format. Fix: darken the help text color so it measures at least 4.5:1. Verified on the July scan.
Every finding carries the same anatomy: the checkpoint, the exact page, the date found, the plain-English explanation, the fix guidance, and the verification date once a later scan confirms the repair.
Why is the example fictional?
Quiet Client is a standing rule here: we never publish a client's name, their findings or their screenshots, in a sample report or anywhere else. A real report describes a real organization's weaknesses, and that belongs to them alone. The fictional example shows you the format; the free Website SnapShot shows you real findings from your own page, which is better evidence anyway. The rule itself is described on the Quiet Client page.