Skip to content
wexloAccessible by design
Customer portalFree scan
wexloFree scan
Customer portal

How it works

From finding to evidence.
Release after release.

Every step makes clear what has been examined, what your team can fix and what still needs attention.

  1. TestingFind what needs attention
  2. FixGive your developer a task
  3. RetestCheck the result
  4. Keep evidenceRecord the outcome

A change or a release? The cycle starts again.

Testing

Your website, in view.
What needs attention, listed.

A real browser examines your pages on desktop and mobile.

  1. Your websiteDesktop and mobile
    • axe-coreContrast · labels · ARIA
    • Wexlo checksKeyboard · reflow · forms
  3. FindingsSeverity · criterion · element

Free: one public page. Paid: up to 100 pages per scan, more if you order extra pages. AI-written explanation is marked. What a scan does not see

Illustrative exampleSee where the findings sit on the page.

Scan of exampleshop.example · /checkout

What the scan found here

  1. image-altImages must have alternative textWCAG 1.1.1 non-text content · ACriticalEstablished
  2. labelForm elements must have labelsWCAG 4.1.2 name, role, value · ACriticalEstablished
  3. color-contrastElements must meet minimum color contrast ratio thresholdsWCAG 1.4.3 contrast (minimum) · AA2.9 : 1 requires 4.5 : 1SeriousEstablished
  4. link-nameLinks must have discernible textWCAG 2.4.4 link purpose (in context) · ASeriousEstablished

4 findings open.

A drawn page with sample data. Not a real customer site and not a statement of full conformity.

Illustrative exampleSee which websites need attention.

Example of the overview in your customer portal with three websites, open findings and the date of the last usable measurement.

What the scanner tests by machine, and what a person has to do.

31 of the 55 criteria were machine-tested. Machine testing is not a conformity claim.

Illustrative example
  • 2 fully automated
  • 29 partly automated
  • 24 rely on human judgement only
  • 5 of those criteria have findings

The distribution across all criteria, with five sample findings. Not a customer measurement.

Fix

From finding
to fix.

Every finding is recorded in your customer portal, with a status and room for comments. That turns fixing into a workflow instead of a list.

  1. FindingsSeverity · criterion · element
    • Customer portalBacklog · comments · statuses
OptionalFurther in your own toolsAs an issue or as a file
  • GitHub
  • CSV
  • JSON
  1. Understand the problemSeverity, criterion and impact on the visitor.
  2. Find the elementPage, selector and measured value.
  3. Pick it upA suggested fix for your team.

Would your team rather stay in its own environment? That works too.

  • Backlog, comments and statuses in the customer portal.
  • Wexlo turns a site's findings into issues in the GitHub repository you choose. There is one issue per rule. After that, Wexlo keeps both sides in step.
  • Export your findings as CSV or JSON.
Illustrative exampleOpen a finding next to your backlog.

Example of an opened finding next to the list, with a suggested fix and comments.

Retest

See the difference after your change.

A new scan shows what has been resolved, newly found or has returned.

Previous scan2.9 : 1Insufficient contrast
  • Fix in your code
  • New measurement
Retest5.5 : 1Contrast 2.9 : 1 to 5.5 : 1
Meets 1.4.3 for this element

A closed task is not yet a passed retest. Check your changes on the test environment* and again after publication.

*Available for Growth, Business and Agency.

A passed check on one criterion does not mean the whole website complies.

Illustrative exampleCompare the measurements after your change.

Example of a scan comparison with 12 resolved, 8 unchanged and 3 new findings.

Keep evidence

The outcome stays
easy to find.

Share your report and keep the measurements, fixes and retests together.

  • Scope and findings
  • Report ID, date and time
  • Online report and PDF
  • Scan history in your customer portal
As PDF and online
Accessible and tagged, in Dutch, English, French or German. Every report carries a report ID you can verify publicly.
As an audit trail
Every scan, task and retest recorded in order, with date, time and a hash.
Illustrative exampleYour report: the cover and the contents.

wexlo

Action required

Accessibility report

WCAG 2.2 level AA · European Accessibility Act

Action required · 7 findings on 5/31 machine-tested criteria · 24 not machine-tested

Website scanned
exampleshop.example
Scan timestamp
2026-09-15 09:12 CEST
Pages scanned
5 of at least 61 found
Plan
Growth
Report ID
WXL-2026-09-15-7C5496

Verify this reportAnyone can check this report there: the report ID confirms it is genuine, and the file's SHA-256 confirms it is unaltered.wexlo.eu/verify

Issued by Wexlo on 15 September 2026Confidential

Content

  1. Summary
  2. Findings
  3. Criteria matrix: all 55 WCAG 2.2 A/AA criteria
  4. Route to full conformity
  5. Scope of this report
  6. AI use in this report
  7. Enforcement context

Example view with neutral values. The fields, the chapters and their order come from the report generator, so this is the structure you actually get.

A report cover and the table of contents, with sample data. Not a customer measurement.

A hash shows that a file has not been changed without notice. It says nothing about whether the content is correct, and certainly not that a website complies with the law.

A change or a release?

Then the cycle starts again at step 1.

Back to step 1: testing

What the law asks of you, and where Wexlo helps.

The European Accessibility Act asks nine things of you as a provider of a service. For each point you see what you do yourself and which Wexlo tool helps you with it. Legal choices and the notification itself always remain your work.

  1. 1. Determine whether it applies to you

    What you do
    Determine, with a lawyer if needed, whether the law applies to what you offer and to whom.
    Where Wexlo helps

  2. 2. Meeting the requirements

    What you do
    Have your team fix the problems in the source code.
    Where Wexlo helps
    • Scan: Problems that can be tested automatically, with element and measured value.
    • Fixes: A concrete proposal for each finding.
    • Manual verification: A specialist checks it by hand, with a verdict per block.

  3. 3. Substantiate an exception

    What you do
    Substantiate and document any claim of disproportionate burden.
    Where Wexlo helps
    No Wexlo tool

  4. 4. Publish how you comply

    What you do
    Publish an accessibility statement and keep it up to date.
    Where Wexlo helps
    • Draft statement: With the measured status and what still needs manual assessment. You check and publish it.

  5. 5. Continuing to comply after every change

    What you do
    Measure again after every change and fix what comes back.
    Where Wexlo helps
    • Scheduled scans: On a fixed schedule, with a subscription.
    • Release scan: Measuring after a deployment.
    • Retest: Shows what is resolved, new or has returned.

  6. 6. Being able to demonstrate your process

    What you do
    Work to a fixed method and agree who picks up what.
    Where Wexlo helps
    • Scheduled scans: On a fixed schedule, with a subscription.
    • Way of working in the customer portal: Test, fix, retest, keep evidence.
    • Audit trail: What was found when, who it was handed to and when it was measured again.

  7. 7. Reporting if you do not comply

    What you do
    Notify the market surveillance authority of every country where you sell, within that country's deadline. You make the notification yourself.
    Where Wexlo helps

  8. 8. Producing evidence on request

    What you do
    Produce what you have done, on request.
    Where Wexlo helps
    • Audit trail: Scans, tasks and retests in order, with date, time and a hash.
    • Report ID: Reports with a verifiable report ID.
    • Conformity dossier: An evidence dossier, not an audit and not a certificate.

  9. 9. Knowing who can enforce

    What you do
    Know where a complaint about your service ends up and what the consequences can be.
    Where Wexlo helps
    No Wexlo tool

The grouping into nine is ours, not the directive's: the obligations are real and are set out in the European Accessibility Act, but how you bundle them is a choice. This is how we read them.

Think a finding is wrong?

The rule engine (axe-core) determines what counts as a finding, not us and not the AI. That makes an outcome reproducible: the same page gives the same finding, even if you have it checked elsewhere.

If you think a finding is incorrect, email the report ID and the criterion to hello@wexlo.eu. We'll take a look and explain what the rule checks. We don't adjust findings because they're inconvenient.

See it on your own website.

One page, free and without an account.

Scan one page free