A11y Delivery Report Copilot

Turn an accessibility scan into a report your client will pay for.

Scan a page, get the exact element and the measured value behind every finding, turn them into a fix list your developer can work through — then export the client-ready report. Runs in your browser. $39 once, not $39/month.

Buy for $39 — one-time See a sample report (PDF)

3 devices · 12 months of updates and support · 14-day refund · no subscription

The report takes longer than the audit

You already know how to find the problems. Formatting them into something a client reads — scope, severity, evidence, what to fix first — is the unpaid afternoon.

“Clients don't read DevTools.”

A screenshot of a scanner panel is not a deliverable. A numbered, prioritised list with the element, the reason and the fix is.

“Which one do I fix first?”

Severity, WCAG criterion and a plain-language reason, so the developer starts at the top instead of arguing about the list.

“Prove the fixes landed.”

Re-scan the page and show exactly what was fixed, what is still failing and what is new.

How it works

Five steps, one loop, no account.

1

Scan the page you have open

One click. 19 automated WCAG 2.2 checks, severity-sorted, each bound to a real DOM element. Nothing is uploaded.

The extension popup showing a scan summary with severity counters and a list of findings.
Scan summary — severity counters, filters and the finding list.
2

Locate the exact element

Click a finding and the element is outlined in the page, with its selector and HTML. No guessing which of the twelve buttons is the broken one.

A web page with the offending image outlined in blue and labelled with the rule name.
The finding is highlighted in the live page, not in a separate panel.
3

Turn findings into a work queue

Status and owner per finding — open, in progress, fixed, verified, or accepted risk. The status travels into the export.

The task board tab with a status selector per finding, one of them set to Verified.
Task board — every change is stored locally and appears in the report.
4

Re-scan after the fixes ship

Fixed, still failing, newly introduced. That diff is the evidence for your second invoice.

The popup showing a re-scan comparison card with counts of fixed, remaining and new findings.
Re-scan comparison, carried into the exported report.
5

Deliver the report

Markdown, JSON, CSV, or a print-ready A4 PDF with running header and footer. Your client name and your name on the cover, evidence on every line.

A printable A4 report page with a summary table, severity bar and numbered findings.
Printable report — A4, page-breaks handled, no PDF library involved.

What's in the box

  • 19 automated checks across 14 WCAG 2.2 AA success criteria: text alternatives, form labels, accessible names, heading order, measured contrast, target size, landmarks, table headers, frames, viewport zoom, duplicate ids, tab order, hidden focusables, vague link text, empty headings.
  • Element-level evidence — CSS selector, HTML snippet and the measured value (for example 2.94:1 (needs 4.5:1)).
  • Fix snippets you can paste, written in plain language.
  • Task board — status and owner per finding.
  • Re-scan comparison — fixed / remaining / new.
  • Exports — Markdown, JSON, CSV and print-to-PDF.
  • Local by design — the page you scan never leaves your browser.
It is not a compliance certificate. Automated testing reliably reaches roughly a third of WCAG success criteria. This tool covers 19 checks across 14 of them — the part a machine can decide. Keyboard journeys, screen-reader reading order, motion and content semantics still need a human. Every export says so.

It does not modify your site. No overlay, no runtime patching, no “compliance badge”.

Pricing

One price, no renewal, no card on file with us.

$39 USD · one-time

Devicesup to 3
Updates12 months
Support12 months, email
Refund14 days, no questions
After 12 monthsthe version you own keeps working
Buy for $39 — one-time

Payments and tax handled by Paddle. Full pricing and FAQ.