KresciaPARTNERS
White-label · for web agencies
One letter costs your client $5,000–$25,000. Before a single line is fixed.
Then the remediation lands on top — $5,000 to $25,000 in the first year at published rates. We do it for a flat $2,400, in the theme, in eight working days, and the report goes out under your name. Demand letters: NK Legal, 2026 · Remediation rates: a11yproof, 2026
The right-hand column stays empty until the fix is in the theme and the scan has run again. That second number is the job.
- No widget. Overlays don’t change the HTML underneath.
- No compliance promise. That claim cost one vendor $1M at the FTC.
- No legal advice. We’re technicians. Lawyers are lawyers.
Pricing, published
Three steps. The first one costs nothing.
Published rates for this work run $350–550 per page, or $5,000–25,000 for a first year. Ours is a flat number, and it is what the work costs you — not what you charge. The margin is yours, and so is the client relationship. Range: a11yproof pricing guide, 2026
01 · start here
Free scan
$0
One page, back within a day
- Automated scan of any page you name
- Issue counts by category
- Three examples quoted from the actual code
- What a screen-reader user hits first
- No compliance verdict, no call
02 · the work
Remediation
$2,400
Five main templates · 8 working days · $5,400 for 10–20
- Tooled audit plus a manual keyboard and screen-reader pass
- Fixes written into the theme files
- Image alternatives written by hand, not generated blindly
- Measured before/after report
- White-label: your name on the report
03 · afterwards
Monitoring
$149/month
Per site · cancel any time
- Monthly re-scan
- Alert when a theme update breaks something again
- Two hours of fixes included each month
- Dated history of every measurement
The public numbers, without the scare tactics
Three figures your clients can verify themselves. We quote them because they’re sourced — not to predict what will happen to anyone in particular.
of the top million home pages fail automated WCAG checks, at an average of 56.1 errors per page.
WebAIM Million, 2026federal web accessibility lawsuits filed in the US in 2025 — up 27% year on year, with over 5,500 expected in 2026.
UsableNet lawsuit trackerthe FTC order against an overlay vendor that advertised automatic compliance. It’s the reason we never use that word.
FTC, January 2025The email you didn’t want
A client forwards you a letter from a law firm you’ve never heard of. It names your site, lists things like “images lacking alternative text,” and names a figure. Demand letters in this area typically land between $5,000 and $25,000.
They ask you what it means. You built that site three years ago, on a theme you didn’t write, and the honest answer is that you don’t know yet.
It isn’t always a letter. Often it’s quieter: a procurement form asks whether the site meets WCAG 2.2 AA, and nobody on the team can answer it. Either way the question is the same: what is actually wrong, and what does it take to fix it? That question has a measurable answer, and the measurement is free.
What you actually receive
One file, written to be forwarded
Everything on this page ends in the same object. Your client reads the first page without knowing what WCAG stands for. Your developer works from the rest without asking us anything. Your logo is on it; ours isn’t.
The counts, before and after
By category and by template, each with the date and the rule-set version it was measured with. One table, no score, no verdict.
Every issue, with its file and its selector
The line as it shipped, the line as we hand it back. Your developer reviews the set in one pass instead of hunting for it.
What we did not fix, and why
Out of scope, needs a design decision, or needs someone with the password. The list exists so nobody discovers it in three months.
| Category | Before | After |
|---|---|---|
| Images with no alternative | 37 / 56 | — |
| Buttons with no accessible name | 14 / 38 | — |
| Links with no accessible name | 17 / 74 | — |
| Everything else the engine flags | listed in full | — |
How white-label actually works
- Who talks to your client
- You do. We never contact them, and we don’t appear in the thread.
- Whose name is on the report
- Yours. We send you the file; what you forward is up to you.
- What we need from you
- Theme access or a staging copy, and the list of templates in scope.
- What you bill
- Whatever you decide. Our number is your cost, not your price.
- If you’d rather introduce us
- Also fine. Some agencies prefer it. We follow your lead, not ours.
If the site already runs an overlay
The widget didn’t fix it. That’s not a criticism.
Overlays do help some users, and installing one was a reasonable decision at the time. But a script that runs in the browser doesn’t change the HTML that ships — and the HTML is where the issues live. Every scan we run is done with the widget active, so the numbers already account for it.
In January 2025 the FTC ordered one overlay vendor to pay $1M over its automatic-compliance advertising. We took the opposite lesson: say what was measured, fix it in the code, measure again.
Adds a layer at runtime
A toolbar, contrast switches, and guesses at missing labels — applied after the page has loaded, in the visitor’s browser.
Change the source
The template still ships buttons with no accessible name and images with no alt text. Turn the script off and every issue is back.
Edit the theme
The fix lives in the repository, survives the next deploy, and shows up in a re-scan. That’s the part you can hand to a client.
How a job runs
Four steps, all of them in writing
Audit
Automated engine across the templates in scope, then a manual keyboard and screen-reader pass on the paths that matter — cart, forms, navigation.
Fix
Changes written into the theme: alt text, accessible names, labels, landmarks, focus order, contrast, heading structure.
Re-measure
The same scan, run again, side by side with the first one. Plus the list of what changed, file by file.
Watch
Optional. A monthly re-scan catches the regression the next theme update introduces — because it will.
Working with us
Built to sit behind your agency
We don’t sell to your clients, we don’t appear in the thread unless you put us there, and we don’t take the account. You quote, you bill, you keep the relationship. We hand you a finished job and a report that carries your logo.
Everything runs in writing, in English, across time zones — the work is usually in your inbox before your day starts.
What we turn down
- Enterprise procurement. Formal compliance dossiers, insurance schedules and vendor onboarding — not our size, and you’d feel it.
- Complex applications. A bespoke checkout or a JavaScript-heavy app is a project, not a fixed-price job. We’ll say so on day one.
- Anything that needs a promise. If the only way to win the work is to guarantee an outcome we can’t measure, we pass.
The first step, in full
What happens after you send a URL
We confirm we got it
One line, from a person. If the site is outside what we take on, we say so here and that is the end of it.
The scan comes back
Counts by category on the page you named, three issues quoted from your actual code, and what a screen-reader user hits first.
Unless you write back
No sequence, no follow-up, no reminder. If it was useful, you know where we are. If it wasn’t, you never hear from us again.
What we don’t do with it
- We don’t add you to a list
- Your address is used to answer you. That is its whole purpose.
- We don’t name the site
- Not in a case study, not in an example, not to another agency.
- We don’t scan behind a login
- Only pages a browser can already reach without credentials.
- We don’t contact your client
- Ever, at any stage, for any reason. You own that relationship.
Prefer to read the small print? It’s all on the privacy page, in plain English.
Questions we get
Straight answers
Do you guarantee compliance?
No. Nobody honestly can — compliance is a legal assessment, not a technical output. We measure the issues, fix them in the code, and measure again. You get both numbers and the list of what changed.
Is this an overlay or a widget?
No. We edit the theme files. An overlay sits on top of the page and leaves the underlying HTML unchanged, which is where the issues live.
Can we put our own name on the report?
Yes — white-label is the default. Your logo on the report, your name to the client, and we stay invisible unless you introduce us.
How long does it take?
Eight working days for five templates, from the moment we have theme access. Larger sets are quoted before we start, never after.
What do you need from us to start?
A staging environment or theme access, and the list of templates in scope. No calls required — everything runs in writing.
What won’t you take on?
Enterprise procurement work, custom single-page applications, legal advice, and anything where we would have to promise an outcome we cannot measure.