Accessibility,from scan to proven fix.
For agencies · EAA · WCAG 2.1 AA · EN 301 549
Wexlo helps web agencies test client sites, turn findings into developer tasks, and prove what got fixed.
Free scanners show you what's wrong. They don't run your delivery: monitoring every client site, prioritising, client-ready reporting, and re-testing after every release.
Delta · scan #15 vs #14
client-example.com · 21 Mar- WX-0142Checkout button contrast 2.9:1 (WCAG 1.4.3)no longer detected (automated re-test)
- WX-0158Menu button without accessible name (WCAG 4.1.2)no longer detected (automated re-test)
- WX-0161Focus order in checkout (WCAG 2.4.3)not re-detected: verify manually
- WX-0177Form field without label on /campaign (WCAG 3.3.2)new
9 no longer detected3 verify manually2 new41 unchanged
Illustrative example, not from a customer site.
Accessible by design. WCAG 2.1 AA is the bar we build to. This site passes the same automated checks we sell. See our accessibility statement.
Not an agency,but responsible for your own organisation's website? see Wexlo for companies →
The workflow
Accessibility doesn’t stop after an audit
Accessibility isn’t a report you deliver once. Every release, new page, plugin or code change can undo an earlier fix. That’s why Wexlo runs the whole cycle for every client site, so your agency delivers a service and not a snapshot.
Test
Scan client websites in a real browser, on desktop and mobile. Wexlo combines axe-core with its own checks, handles cookie banners and dynamic content, and gives every finding a certainty label.
Fix
Every finding becomes a concrete development task, with the WCAG criterion, the selector, a fix suggestion and an estimate of the time it takes.
Verify
On the next scan Wexlo re-tests every earlier finding. If the issue is no longer found, the report records that as “no longer detected (automated re-test)”. If only a person can judge whether it is really fixed, that stays visible as “not re-detected: verify manually”.
9 no longer detected3 verify manually2 newProve
An accessible PDF and online report per client: what was tested, what changed since the last scan, and what still needs human review. That builds a record of the work as you go. Every sealed report carries a report ID and a SHA-256 checksum, so your client can check that the report was not altered.
Test. Fix. Verify. Prove. Then the next release starts it again.
↺ back to Test on the next release
Scans run on the schedule you set per client: weekly, monthly or on demand; release-triggered scans are on our roadmap. The cycle keeps running without your team having to track it by hand.
The market in four numbers
What the regulator found on 100 large Dutch sites
Two separate groups, and the heavier one is the larger. Read the other way around, the numbers say something the regulator did not.
61 of 100: placing an order with assistive technology proved impossible.
33 of 100: had serious problems; ordering is possible, but takes considerably more effort.
6 of 100: the remaining sites.
- 95.9%
- of a million home pages tested in 2026 had detectable WCAG failures, up from 94.8% a year earlier. It is the first rise in six years.
- WebAIM Million, 2026
- €2,000+
- is what a full manual WCAG audit of a small business site typically costs in the Netherlands, and it reflects the site at the time of assessment.
- published NL agency rates, July 2026
Anatomy of a finding
A finding your developer can start on today
Finding
WX-0142
Criterion
1.4.3
Contrast, minimum
The checkout button label measures 2.9:1 against its background, below the 4.5:1 required for normal text.
button.checkout-cta > spanDarken the gray. Same design language, passing contrast:
S: under an hour, one CSS change
Illustrative example, not from a customer site.
AI suggestions never fail a criterion and never move a score; they wait for human confirmation.
Copy a finding as task text, or export it to GitHub or CSV in one click.
Built for multi-client work
Every client site, on its own schedule
Accessibility work fragments fast when every client has a different website, developer, language and release cycle. And clients rarely want to pay for the hours you spend interpreting scanner output. Wexlo keeps the cycle running per client:
- dated scan history per client domain
- report ID and SHA-256 checksum on every sealed report
- run all client domains, from a handful to hundreds
- plan scans per client: weekly, monthly or on demand
- reports in each client's language (EN/NL/FR/DE, per domain)
- developer tasks with certainty and effort labels
- delta on the next scan: what's no longer detected, what's new
- alerts on new critical issues
- hosted accessibility statement per domain, renewed at every scan
- co-branded reports for your clients
- monthly recurring monitoring your clients understand paying for
Your client domains
- client-example.comtoday
3 fail · 2 review · 41 pass
- shop-example.eutoday
0 fail · 4 review · 42 pass
- booking-example.nl2 days ago
7 fail · 3 review · 36 pass
- portal-example.be5 days ago
1 fail · 1 review · 44 pass
Illustrative example, not from a customer site.
For client organisations the same record is their compliance file: see Wexlo for companies →
The honest part
Automated scanning is the starting point, not the entire audit
| Coverage | Criteria |
|---|---|
| 3 criteria, fully automated | 3 |
| 27 criteria, partially automated | 27 |
| 20 criteria, need human review | 20 |
No automated tool can test the full accessibility experience or certify legal compliance on its own. Automated scanning finds roughly 30 to 50% of real accessibility issues. Independent testing by the UK Government Digital Service put the best single tool at 41%; Deque, which makes the scanner we use, reports 57% on its own data. We stay with the lower estimate. Our scanner machine-checks 30 of the 50 WCAG 2.1 AA criteria, in full or in part, counted on criteria. Wexlo shows the coverage per criterion, so you know exactly what was tested automatically, what was tested partially, and where human judgment is still needed. See the coverage per criterion
Every report clearly separates: automatically tested criteria · partially tested criteria · checks that need human review.
No false compliance claim. No black box. Need the human layer too? Add a manual verification by a specialist or a conformity dossier per client site.
The lane we're not in
Fix the website, not the layer on top
Overlay widgets
Inject a JavaScript layer, typically marketed as making your site compliant. The underlying code stays broken.
In April 2025 the FTC's final order against overlay vendor accessiBe (Docket No. C-4817, a $1M non-admission settlement) barred it from claiming its automated products can make websites WCAG-compliant without evidence.
Wexlo
Identifies issues in the website itself, shows developers what to change and re-tests the finding on the next scan. That creates a record of actual improvements.
We will never sell or recommend an accessibility overlay.
Evidence, four levels
Evidence that grows with the situation
Not every client site needs the same depth of evidence. You start with automated monitoring and add manual verification or a conformity dossier when a client asks for it. Re-checks are always included, never billed per round.
Evidence depth 1 of 4
The full workflow
included in the Agency plan
Everything runs in your customer portal, per client domain: automated scans on your schedule, developer-ready findings with certainty labels, an automated re-test per finding, reports and statements. Unlimited on-demand scans included (fair use).
Evidence depth 2 of 4
Manual verification
€199 per client site
A specialist tests what software cannot judge: keyboard flows, real form errors, content quality. Sample-based, explicit verdict per block, in a shareable addendum. Quickscans elsewhere start around €495 (published NL agency rates, July 2026).
Manual verificationEvidence depth 3 of 4
Conformity dossier
€990 per client site
Every one of the 50 criteria documented with the strongest available evidence, WCAG-EM-structured, including what was not tested. Our documented assessment, not an independent audit or certificate.
Conformity dossierEvidence depth 4 of 4
EAA base package
€1,190 per client site
One order for a client site that has to show its EAA homework: an in-depth automated report, a specialist's manual verification of up to five key pages, and the conformity dossier. An evidence package, not an independent audit or certificate.
EAA base packageThe agency offer
What your agency gets, in detail
Everything in the company plans, per client domain, plus the layer agencies actually need: winning the work, delivering it at portfolio scale, and standing behind it afterwards. That turns accessibility work into a recurring service for your clients, instead of a one-off project per site.
Turn accessibility into new business
- sales enablement kit on request: deck, one-pagers and example reports
- referral and resell routes (partner programme)
- prospect scan teaser, co-branded with your agency
Run the workflow across every client
- multi-client workspace, from a handful to hundreds of domains
- scans per client: weekly, monthly or on demand
- developer tasks with certainty and effort labels
- report language per client domain (EN/NL/FR/DE)
- ticket export to GitHub or CSV
- co-branded PDF and online reports
Stand behind the work
- automated re-test of every finding, delta per scan
- scan history and sealed reports per client domain, with report ID and SHA-256 checksum
- hosted accessibility statement per domain, renewed at every scan
- alerts on new critical issues
- manual verification, conformity dossier and EAA base package per client site
- exportable audit trail of your workspace
Agency
Pricing scales with your portfolio: request a quote.
One plan, sized to your portfolio: from 20 domains, weekly scans plus unlimited on-demand scans (fair use), everything above included.
Discuss your agency portfolioAll prices exclude VAT. Plans for a single organisation (Starter, Growth, Business, one-off report) live on the pricing page; this page is about running accessibility for clients. Pricing
Every paid scan covers up to 100 pages per domain, for one-time reports and subscriptions alike. Larger site? Ask us to scope it
Partner programme · founding cohort
Refer, resell or co-brand without selling an overlay
The best-known accessibility partner programmes ask agencies to resell a widget. Wexlo's founding partner programme is the alternative: co-brand the honest workflow (test, fix, verify, prove) for your clients, with transparent terms. Applications for the founding cohort are open; the programme terms follow our legal review. Full white-label is on our roadmap. We will never ask you to sell an overlay.
Before you ask
Agency questions
How do you deal with false positives?
Every finding carries a certainty label. AI-suggested findings can never fail a criterion or move a score, and “likely” findings are clearly separated, so your developers decide where judgment is needed instead of chasing noise. Built so false alarms don't bury your team.
Can we tell our client they are compliant after a scan?
No, and be wary of anyone who says yes. Automated scanning finds roughly 30 to 50% of real accessibility issues. That range is not a guess, but it does depend on how you count. Independent testing by the UK Government Digital Service (2017) planted 143 failures in a single page and ran ten tools against it: the best single tool found 41%, and 29% was caught by no tool at all. Deque, which makes the axe-core we use, reports 57%, but counts individual instances rather than kinds of problem. That gap is explainable: contrast failures repeat dozens of times on one page, a keyboard trap happens once. In our own scan of 133 agency homepages, contrast appeared 693 times across 80 sites. So we stay with the lower estimate, and the report states per criterion what the machine tested and what a person still has to check. That lets you plan the human part honestly with your client.
Can our reports carry our agency's brand?
Yes, on the Agency plan. Turn co-branding on in your portal, upload your logo and pick an accent colour, and every report carries your mark. You can opt individual client sites back out. The Wexlo mark stays alongside yours: full white-label is still on our roadmap, and until then that visible independence is part of what your client is buying.
Why pay for Wexlo when free WCAG scanners exist?
Because finding is only the first step. A free tool checks one page, in your browser, once. Wexlo runs the work after that: prioritising per client, findings as development tasks, re-testing on the next scan, and recording the evidence in reports your client can keep. The rule engine underneath is that same axe-core.
Start the record on one client site
Scan one page of a client site free. The finding counts and the biggest findings in plain language, plus an example fix, by email. That first measurement is where your client's record starts.