Accessibility, and you are the one accountable.
EAA · WCAG 2.1 AA · EN 301 549 · for companies
The law puts the obligation on the organisation that sells, not on the agency that builds. We make that obligation something you can actually run.
Wexlo inventories the accessibility issues on your website in plain terms, hands them to your web agency as ready-to-pick-up tasks, re-tests every finding on the next scan, and keeps the audit trail your organisation can show.
You don't need to be technical. You need to know what's broken, who's fixing it, and whether it's actually done. Wexlo keeps that overview for you.
Audit trail · one finding
your-company.com- 12 Mar · scan #14Found: checkout button contrast too low (WCAG 1.4.3), established
- 14 MarTask handed to your agency: element, fix and effort included
- 21 MarAgency reports the fix done
- 21 Mar · scan #15Wexlo re-tests on the next scan: no longer detected (automated re-test)
- 21 MarSealed in your audit log; every scan renews the automated test results in your statement
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.
Building sites for clients?Agencies run this same workflow across their whole client portfolio: see Wexlo for agencies →
The workflow · a loop, not a one-off
Update after update
Accessibility isn't a project with an end date; every website update can break what was fixed. Wexlo runs the cycle continuously, so your organisation always knows where it stands.
Inventory. Hand off. Check. Keep the record. Then it starts again.
Inventory
Wexlo scans your whole website and lists what's broken in plain terms: what it means for visitors, how serious it is, and where to start. No jargon wall.
Hand off
Every issue is a ready-to-pick-up task for your web agency or developer: page, element, fix guidance and effort, in their language. Prefer to automate? Connect your own tooling.
- your agency
- ticket export to GitHub or CSV
Check
“It's fixed” gets verified, not believed. The next scan re-tests every finding and shows the delta: “no longer detected (automated re-test)” for what the scanner can confirm, “not re-detected: verify manually” for what it cannot. Documented evidence of what changed.
Audit trail
Every finding, hand-off and verification lands in an append-only log with a hash chain, and every scan renews the automated test results in your accessibility statement alongside it. Every report is sealed with a report ID and SHA-256 checksum. You can export that log in one click, as CSV or JSON, with the hash-chain check included.
↻ every site update and every scheduled scan re-enters at step 1
Scans run automatically on the cadence that comes with your plan, monthly, weekly or daily, and you can start an extra scan yourself whenever you want one. The cycle keeps running without your team having to track it by hand.
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
Why this matters
Independent proof, not promises
Many organisations outsource accessibility fixes and then take the invoice as proof. Wexlo separates the roles: your agency (or your AI tooling) does the fixing, and Wexlo re-tests every finding on the next scan, a new automated check, independent of whoever did the fixing.
The result is a record your organisation owns: what was found, when it was handed off, when it was fixed, and the re-test that confirms it. If a customer complains, a regulator asks, or a tender requires evidence of your accessibility work, you have it: dated, per finding, in an append-only log, with every report sealed by a report ID and SHA-256 checksum.
Management
sees progress and risk without reading a single scanner report.
Your agency
gets tasks it can pick up directly, and its work is confirmed by a re-test on the next scan.
Legal & compliance
gets a dated dossier and a statement whose automated test results are renewed at every scan, instead of an audit that reflects a single point in time.
Customers
get a website that actually works, plus a published statement that says what's been done.
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. Today's scanner machine-checks 30 of the 50 WCAG 2.1 AA criteria, in full or in part, counted on criteria, not marketing math.
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.
The lane we're not in
Fix the issue on the website, not the symptom of the problem
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, hands them to the people who can fix them and checks the result on the next scan. That creates a record of actual improvements.
We will never sell or recommend an accessibility overlay.
Pricing · companies
What it costs
Subscriptions start at €99 per month.
One-time report: €79 one-time
All prices exclude VAT · cancel monthly · pay yearly, get 2 months free.
Every paid scan covers up to 100 pages per domain, for one-time reports and subscriptions alike. Larger site? Ask us to scope it
Rather have your agency run all of this for you? Agency pricing is volume-based. see Wexlo for agencies →
Evidence, four levels
One workflow, deeper evidence when you need it
A full manual WCAG audit in the Netherlands typically runs €2,000–4,500 (published NL agency rates, July 2026) and reflects the site at the time of assessment. Wexlo layers the evidence instead, and re-checks are always included, never billed per round.
The full workflow
subscriptions from €99/mo
Everything runs in your customer portal: automated scans on your schedule, plain-language findings your agency can pick up, an automated re-test per finding, a statement whose automated test results are renewed at every scan, and the audit trail. Unlimited on-demand scans included (fair use).
All plans and pricesManual verification
€199 per 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 verificationConformity dossier
€990 per 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 dossierEAA base package
€1,190 per site
One order for an organisation 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 packageBefore you ask
Company questions
We already have a web agency. What does Wexlo add?
Your agency fixes; Wexlo re-tests independently and keeps the record; two different roles. Your agency gets better briefs out of it too, and can even run Wexlo across their whole portfolio.
Does a scan make us compliant?
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 a manual verification or dossier when you need deeper evidence.
Do we need technical people in-house?
No. Findings are written in plain terms for you, and as concrete tasks for whoever fixes them: your agency, a freelancer, or your own tooling via the API or an AI coding agent. You keep the overview; they get the details.
Start your record with one page
Scan one page free. The finding counts and the biggest findings in plain language, plus an example fix, by email. That first measurement is where the record starts.