Validiscan
WCAG 2.2 AA · EN 301 549 · EAA 2019/882

European Accessibility Act · in force since June 2025

Accessibility failures, fixed in your source code.

We find what is broken on your shop, write the fix into your code, and keep a dated record of what changed and when. No overlay. No widget. No script that hides the problem from you instead of solving it.

Corrected WCAG 4.1.2 Name, Role, Value · Level A

Cart button had no name a screen reader could read

Announced as “button”, with nothing to say what it does. A blind customer could not find the way to their basket.

Verified fixed Pull request #128 Re-checked on every deploy
94%

of the world’s busiest home pages fail the accessibility standard that EU law is built on. The average page carries more than fifty separate failures.

Source · WebAIM Million, annual survey of one million home pages

The difference that matters

A widget sits on top. We change what is underneath.

Overlay tools inject a script that adds a toolbar to your page. The code underneath is exactly as it was before — which is why the same failures keep turning up in audits, complaints and procurement questionnaires.

Overlay widget

  • Adds a script and a toolbar on top of the page
  • Your source code is left unchanged
  • Stops working the day you remove it
  • Little to show an authority beyond an invoice

Validiscan

  • Fixes land in your repository or your theme
  • You own the changes, and review them before they merge
  • The fix stays fixed if you cancel tomorrow
  • A dated record of every finding and every correction

In April 2025 the US Federal Trade Commission required a leading overlay vendor to pay $1 million and barred it from claiming its automated product could make a website conform to WCAG. In the first half of that year, more than a fifth of US accessibility lawsuits were filed against sites that already had a widget installed.

How it works

Find it, fix it, prove it.

01

Find

Your shop is checked against WCAG 2.2 AA, the standard behind the European Accessibility Act. You get the exact failures, with the line of code and the criterion each one breaks.

02

Fix

We write the corrections and send them as pull requests, or as theme patches if you have no developers. Nothing reaches your live site until you approve it.

03

Prove

Every scan and every fix is recorded with a date. When a customer complains, an authority asks, or a buyer sends a questionnaire, the answer is already written.

Straight answer

What automated testing can and cannot do.

Automated checks reliably catch a share of the problems — missing labels, unnamed buttons, images without alternative text, broken heading structure. Every failure we report is provable from your code, so nothing on your report is a guess or a maybe.

They do not catch everything. Whether a page can be used entirely by keyboard, whether an error message makes sense read aloud, whether a video explains what is on screen — those need a person. Any tool claiming it makes your site compliant on its own is overstating what it does.

So the number in your first report is a floor, not a total. It is the part we can prove today, and the part we can start fixing this week.

Send a shop address. Get back what we find.

No charge, no account, no call required. Reply with the URL and you get the failures we can prove, with the code and the criterion for each one. If it is useful, we can talk about fixing them.

[email protected]