White-label accessibility reports you can put your name on
Clients do not buy "25 checks". They buy a document that tells them what is wrong with their website, what it costs them, and what they would be paying you to fix first. This page is about producing that document — and about the two sentences that keep you legally honest.
What clients actually want to know
- Is my site broken, and how badly? (a count they can understand, not a score)
- Which parts matter to my customers? (checkout, booking, contact, the pages that earn money)
- What is the evidence, so I can believe you? (the offending markup, a screenshot, a contrast ratio)
- What do I do first, and what does it cost? (a short, ordered work list)
- How do I know it stays fixed? (that is the retainer)
A report that answers those five questions sells the next engagement by itself. A report that opens with "WCAG 2.2 level AA conformance status: partially conformant" and nothing else does not.
Why white-label matters
If the document carries another company's logo, the client learns that somebody else found the problem. If it carries yours, they learn you found it, which is the whole reason they pay you instead of running a free checker. So the tool that produces it must let you set the name on the report, and must not stamp its own advertising all over the page — or worse, try to upsell your client directly.
AccessAudit Station prints the report with whatever name you put in its settings, and no branding of ours. It runs on your own server, so the report, the client list and the findings are yours, not a subscription's.
The two sentences that protect you
Put these in every report, and mean them:
- "Automated checks find the mechanical problems: missing alt text, unlabelled form fields, broken heading order, empty links and buttons, tables without headers, frames without titles. They cannot see colour contrast, judge whether alt text is useful, or know how the page behaves in a screen reader." This is not weakness; it is what makes the rest of the document credible.
- "This is a work list from an automated scan on a given date, not a certification and not legal advice." Nobody can certify a website by script, and the vendors who claim otherwise have found themselves in court rather than out of it.
Making it a monthly line item
An audit is a snapshot; sites change weekly. Scan the pages that convert, weekly or monthly, and email the client only when something new appears — "three new problems on /checkout after Thursday's update" is an email they will read, and it is also the justification for the fee. Then send the refreshed report with the previous one attached. Clients renew the thing that keeps producing evidence.
Pricing the bundle, honestly
Sell the first audit as a fixed fee priced on templates rather than pages, sell remediation separately because page builders are unruly, and sell monitoring as a small recurring amount per site. Monitoring should not be priced per page or per scan: a client with 200 pages is not ten times a client with 20, and pricing that way punishes them for having a big site.
What to do when a client says "our host already gives us an accessibility widget"
Overlays sit on top of the page and leave the underlying markup alone. Ask the host for a written statement of what the widget fixes, and test one page with a screen reader before the next invoice. You will usually win that conversation on evidence rather than argument, and you will not have to sell against a competitor — the page itself will do it.
See the report and the screens Pricing What belongs in a report