Frequently asked questions

The EAA (Directive (EU) 2019/882) has applied since 28 June 2025 to consumer-facing services in the EU. In broad strokes:

In or out of scope, we show you exactly where your site stands and what to improve: toward compliance if the law applies to you, toward a site every visitor, customer and prospect can use if it doesn't.

Enforcement is national: each member state has its own market-surveillance authority (ACM in the Netherlands, DGCCRF in France, FOD Economie in Belgium, the Länder authorities in Germany), each with its own practice and penalties. By mid-2026 the first concrete actions are on record. In France, disability-rights associations won a court order (Tribunal judiciaire de Caen, June 2026) requiring Carrefour to make its site fully accessible within six months on penalty of a daily fine. In Sweden, the regulator PTS has opened supervision cases against 28 retailers since 2025: investigations, not yet fines. Norway shows how hard this can bite: its regulator ordered daily penalty payments of NOK 50,000 (about €4,500), and the site was fixed within days, though that runs under Norwegian law, which is separate from the EAA. We won't put a number on your head as a scare tactic: the honest framing is that the deadline passed on 28 June 2025, and the question is whether you can show evidence of what you did.

No, and any automated tool that calls itself an audit is overselling. 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. An audit adds human judgment: keyboard flows, screen-reader testing, meaningful alt text, logical reading order. Every Wexlo report states which criteria were tested automatically and which need manual review, so an auditor can start from our evidence instead of from zero.

Every finding with its rule, WCAG criterion, impact level, and CSS selector; a plain-language explanation and a concrete fix suggestion (markup/ARIA/CSS) per finding; an HTML and PDF version; and a draft accessibility statement for your site. Explanations are AI-drafted and marked as such. The findings come from the rule engine, not from AI.

Plans start at €99/mo for one domain with monthly re-scans, and scale by number of domains and scan frequency. All prices are on the pricing page, excluding VAT. The one-page scan is free, no account needed. Prefer not to subscribe? A one-time in-depth report for one website is €79, credited to your first payment if you subscribe within 30 days.

Overlays inject a JavaScript widget and claim to make a site compliant client-side. 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. We take the opposite approach: findings and fixes in your actual code.

It is real technical evidence and it saves you work, but it is not legal cover. EN 301 549 is harmonised under the directive for public sector websites, and there it gives you a presumption of conformity. Under the European Accessibility Act that link does not exist today: the version in force, v3.2.1, does not mention Directive (EU) 2019/882 once, and the reference to its successor has not yet been published in the Official Journal (as of August 2026). So there are two things worth asking about any report, including ours. Which provision of the directive does it base its coverage on? And does it cover only your pages, or also your customer support, your payment flow and your documents? Annex I asks for more than pages: information about the service and support services in section III, and identification, security and payment in section IV.

Free tools like Lighthouse or a browser extension check one page, in your browser, once. Great for a spot-check. Wexlo is built for evidence you can keep: it crawls up to 100 reachable pages per scan on desktop and mobile, turns every finding into a plain-language explanation and a concrete code fix, delivers an HTML and PDF report plus a draft accessibility statement, and re-scans on a schedule so regressions get caught. The rule engine underneath is the same axe-core. You pay for the pages, the fixes, the evidence, and the repetition, not for a secret algorithm.

The rule engine (axe-core) decides what counts as a finding, not us and not the AI, so results are reproducible. If you think a finding is wrong or doesn't apply, email us. The report always names the exact rule and CSS selector, so it's easy to check. And if a page comes back clean, that's not a wasted scan: a dated report showing what passed is exactly the kind of evidence the accessibility statement asks for.

Yes, manual verification is a separate one-off service (€199, no subscription). A specialist reviews up to 5 key pages of your site by hand against the criteria automated scanning can't judge: live form-error handling, color contrast on images and gradients, whether alt text actually matches the image, and cookie-banner/chat-widget keyboard behavior. It's a representative sample, not full coverage, and the findings are written up as a verification addendum. We usually deliver it within 2 working days, and within 5 at the latest, and confirm the delivery date by email. It's a human-led check, not a certification. Automated scans stay the fast, repeatable baseline; the manual verification adds human judgment on top.

In your own language. You set your default report language in the portal (it starts as the language you signed up in). On the Agency plan you choose the report language(s) per domain, so every client gets their report in the right language. English, Dutch, French, and German are included. The scan itself works on sites in any language, whichever language your report is in. Need reports in more than one language on a paid plan? Add extra report languages as an add-on, from your portal on a subscription, or at checkout on a one-off report.

Monthly on Starter, weekly on Growth, daily on Business, plus on-demand scans from your portal. Re-scans catch regressions and verify fixes.

Everything, every time. A re-scan runs the same full audit as your first scan: it re-crawls your site (up to 100 pages), re-tests every page against all automated checks, and produces a fresh report plus an updated draft statement. It doesn't just look at new pages. An issue that was fixed and later reappears shows up again. You can compare reports side by side in your portal.

No. We scan publicly reachable pages the way a browser does. No script on your site, no access to your repository, no agency handover.

Run the free one-page scan. No account needed. If it's useful, pick a plan and register your domains in the portal; your first full report (up to 100 reachable pages, on desktop and mobile) runs right after. No installation, no sales call, nothing to set up on your side. You go from a URL to evidence, not into a project.

Your scans over time, per domain: every finding with its rule, criterion and selector, the delta against the previous scan, and the log of when something was found, handed off and re-tested. The draft accessibility statement lives there too, and its automated test results update when a new scan runs. The customer portal belongs to the subscriptions: that is where your scan history per domain lives. Order the one-time report and you get the files by email.

The EAA expects you to publish information about your service's accessibility. We generate a draft statement based on your scan results, hosted at a stable link you can point to directly, or embed on your own site as an HTML fragment, alongside HTML/PDF/Markdown downloads. It's a solid, honest starting point. It becomes "enough" once you complete it with what automated testing can't see (manual checks, organizational measures) and keep it current. We're explicit about that: the draft says what was and wasn't tested.

Yes. Subscriptions run monthly and you can cancel from the portal with one click; access runs until the end of the period you already paid for. No annual lock-in, no cancellation call.

You can pay monthly or yearly. The yearly plan gives you 2 months free (you pay for 10 months, we scan for 12). A monthly plan runs month to month; a yearly plan runs for a year and then renews automatically for another year at the same price, so it never jumps at renewal. You can cancel either one anytime from the portal, and the cancellation takes effect at the end of the period you already paid for. Section 7 of the terms has the full detail, including how this works if consumer law applies to you.

A one-time report shows where you stood on the day of the scan, useful as a baseline or as evidence at a specific moment. Accessibility doesn't stay fixed, though: every release, new page or content change can introduce new issues. A subscription re-scans your site on a schedule (monthly, weekly or daily depending on your plan), verifies that fixes stayed fixed, keeps your draft accessibility statement in sync with the latest scan, and builds up scan history in your portal. And if you start with the one-time report, we credit its fee against your first subscription payment if you subscribe within 30 days.

Yes. You can upgrade anytime. You pay the new plan's price straight away and the time you already paid for is credited as extra days, so nothing is lost. That works on yearly plans too: your remaining value converts into extra days on the new plan, and you can switch to monthly billing at that moment if you prefer. A downgrade starts at the end of your current billing period (on a yearly plan: the current year). Each domain slot can be pointed at a different domain once a calendar month; if you just mistyped, you have 24 hours to correct that same entry (a fix, not a second change). On an Agency plan you can add or remove domains anytime above your plan's minimum. Each added domain is billed in full for the month it's active, even for a single day, with no pro-rata. For now, email us and we'll arrange any of these. Self-service is coming to the portal.

Not yet. The scanner visits your site the way a public visitor's browser does, so pages behind a login, paywall, or intranet stay out of scope. Every report lists exactly which pages were scanned.

The free scanner accepts any public URL, but we never bypass a site's bot protection to get in. That's a hard line, not a technical limit we're working around. If a site blocks our scanner, we say so plainly instead of trying harder to get past it. For your own site, you can allowlist our scanner (identity and steps on our scanner-info page) so re-scans go through cleanly.

Not by default: we don't run fingerprint-spoofing or proxy tricks to get past that kind of protection. For a verified domain you own, email us: we can look at a paid, request-only unblocking option for that specific case. Start with allowlisting our scanner first; for most sites that's all it takes.

We don't solve CAPTCHAs in v1. If your verified domain requires one for automated visitors, email us and we'll see what's possible.

Because we don't need one: this site sets no tracking or marketing cookies at all. Our visitor statistics are cookieless and aggregate. No identifier follows you around. The only cookie Wexlo ever sets is the strictly necessary session cookie that keeps you signed in to the customer portal, and EU rules don't require a banner for that. Fewer pop-ups is also an accessibility choice: a consent banner is one more obstacle between you and the content.