Skip to main content

Sample report

Not a mockup. A real report.

This is a real report our audit pipeline generated, from a scan of a public demo storefront (demoblaze.com), with the real screenshots and findings it produced.

Download the sample report (PDF)

What's in the report

Every Quietramp report has the same structure: an executive summary, a severity breakdown, and one finding card per issue — each with a screenshot, the specific WCAG criterion it maps to, and a fix instruction. Findings are grouped critical → serious → moderate → minor, in that order, so the highest-priority issues are first.

CriticalFinding 01WCAG 1.1.1 Non-text Content
Screenshot of the demoblaze.com header, highlighting a small logo image with no alt text next to the site navigation.

Logo image in the header has no alt attribute,aria-label, or title — a screen-reader user gets no information about it.

CriticalFinding 02WCAG 1.1.1 Non-text Content
Screenshot of a product card on demoblaze.com, highlighting an unlabeled image icon.

Same issue, second instance: an image inside a product heading with no accessible name.

Full-page screenshot of the demoblaze.com storefront homepage as scanned.
Full-page screenshot captured at scan time, included in every report for context.

Each finding in the actual PDF includes the fix instruction a developer would act on directly (in this case: add a descriptive altattribute, or alt="" plus a text label if the image is decorative) — download the sample above to see the full report format.

Beyond the automated scan

This particular public demo site happened to trigger only automated findings. A real Quietramp audit also includes the manual review layer — keyboard navigation, screen-reader landmarks, false-positive triage — even when the automated scan comes back clean, because those checks are things a scanner cannot do at all. See the service description for what that covers.