Skip to content

How Wexlo works

A scan is one measurement, at one moment. Accessibility does not stop there: every release can undo what was fixed. So Wexlo runs a cycle that keeps going (establish, hand off, re-test, record), and the customer portal is where those four come together. The scan is one of them. No installation, no widget, no access to your codebase needed.

01The cycle
  1. You give us a URL

    The free scan covers one page. On a paid plan you register your domains and we crawl up to 100 reachable pages per scan, on desktop and mobile viewports.

  2. The rule engine scans

    A real browser loads each page and runs axe-core against WCAG 2.1 A and AA, the technical basis of EN 301 549, the European standard for accessible ICT and in practice the route to meeting the European Accessibility Act. The rule engine alone decides what counts as a finding.

  3. Every finding becomes a fix

    Per finding you get the rule, the WCAG criterion, the impact level, the CSS selector, a plain-language explanation, and a concrete fix suggestion: actual markup, ARIA, or CSS. Summaries and explanations are AI-drafted and marked as such; findings are not. That package is what you hand to your own developer or your web agency; we do not fix for you, we re-test what you had fixed.

  4. You get evidence, on a schedule

    Reports come as HTML and PDF, in your own language, with a draft accessibility statement hosted at a stable, linkable page; or embed it directly on your own site as a ready-to-use HTML fragment. On the Agency plan you pick the language(s) per domain, with all four (EN/NL/FR/DE) included. Scheduled re-scans (monthly, weekly, or daily by plan) catch regressions and verify that fixes stayed fixed. Your customer portal holds the whole series side by side: every scan, the delta against the previous one, and the statement that keeps pace.

That is the cycle as Wexlo runs it. Who runs it inside your organisation (who fixes, who signs off, who keeps the record) is on For companies.

02The portal

Where the work lives

The scan is one step; the portal is where the rest happens

Between two scans this is where the work happens: what is new, what your agency resolved, and what still needs checking by hand. And when a customer, an auditor or a regulator asks where you stand, the answer is already there. You are not reconstructing it from tickets, emails and loose scans.

Customer portal · one domain

your-company.com
  1. 12 Mar · scan #149 resolved3 to verify by hand2 new
  2. 5 Mar · scan #136 resolved5 to verify by hand
  3. 26 Feb · scan #124 resolved7 to verify by hand1 new
  4. 19 Feb · scan #110 resolved11 to verify by hand
Log
when each finding was found, handed off and re-tested
Statement
automated test results updated on 12 Mar
Illustrative example, not from a customer site.
03The clock

One site, one clock per country

Article 13(4) of the EAA asks the same thing in every member state: report your own non-conformity immediately, describe it, and describe what you are doing about it. What differs is how each country wrote that down: the deadline, the authority, and whether a route to report yourself exists at all. The Netherlands is the only country that turns it into a repair-or-report rule, where fixing it inside the deadline means you do not have to report.

Which countries do you sell in?

Optional. Select nothing and you see every market.

One site, one clock per country
MarketDeadlineRoute to report yourself
Netherlands1 week (critical and serious)1 month (moderate and minor)yes
Sweden14 daysfrom regulator guidance, not from the law itselfyes
Belgiumimmediately, with no number in the lawan addressee, but no prescribed form
Germanyimmediately, with no number in the lawgeneral contact form only
Franceimmediately, with no number in the lawyes
Rest of the EU5 working days(Lithuania)not establishedsource not yet verified

What this means for you

Your shortest deadline is 1 week, and it applies in the Netherlands. You have to meet all of them, because there is no single desk that handles the other countries for you. In practice you work towards the shortest.

04A finding

What a finding looks like

Finding

WX-0142

Criterion

WCAG 1.4.3

contrast, minimum

FailCritical
What fails

The checkout button label measures 2.9:1 against its background, below the 4.5:1 required for normal text.

Element
button.checkout-cta > span
Fix

Darken the gray. Same design language, passing contrast:

#9298A3 · 2.9:1#5B6B77 · 5.5:1Pass
Effort

S: under an hour, one CSS change

Illustrative example, not from a customer site.

05What we cover

What this does and doesn't cover

Coverage of the 50 WCAG 2.1 AA success criteria: 2 fully automated, 28 partially automated, 20 need human review
CoverageCriteria
2 criteria, fully automated2
28 criteria, partially automated28
20 criteria, need human review20

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 tests 30 of the 50 WCAG 2.1 AA criteria automatically, in full or in part. Every report states which criteria were tested automatically and which require manual review, so you know exactly where a human needs to look. No automated scanner can certify legal compliance. And the Act asks for more than a website. Grouped the way we read it, it puts nine obligations on you: a measurement feeds two of them, and the other seven are decisions and records that no tool makes for you.

See all 50 criteria in plain language

The W3C, the body behind the WCAG guidelines, says so itself: "no tool alone can determine if a site meets accessibility standards. Knowledgeable human evaluation is required to determine if a site is accessible." That is why the matrix above separates, per criterion, what the machine tests from what a human needs to review. That human review is not part of the scan. It is a separate, paid step: the manual verification.

Source: W3C Web Accessibility Initiative, Test & Evaluate (updated 1 August 2023)

06If it is disputed

Think a finding is wrong?

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.

hello@wexlo.eu

07Start

See it on your own site

Start with one page for free and see what comes out, or read what a plan covers and what it costs.