Validiscan
Menu

Language

Accessibility failures, fixed in your shop’s own code

Validiscan scans EU online shops on Shopify, Shopware, WooCommerce and Magento against WCAG 2.2 AA and EN 301 549, delivers the fixes as changes to the shop’s own source code, and documents the result in a dated Remediation Evidence Package.

Request a free check How a project runs
  • No overlay, ever. No script that rewrites your pages for visitors.
  • Nothing reaches your live shop until you or your agency publish it.
  • A dated Remediation Evidence Package. Evidence of the work, not a certificate.

One finding, from open to verified

Example data

An example finding from the customer portal: Buttons must have discernible text

The shop’s search button shows only an icon, so a screen reader has no name to read out. The change adds that name in the theme file. The button looks the same.

Finding
F-43D4A5F5 · button-name · WCAG 4.1.2 (A)
Impact
Critical
Fix tier
ASSISTED
Pages
31
  1. Open ,
  2. Fix proposed ,
  3. Fix delivered ,
  4. Fixed ,
  5. Verified ,

Verified on 24 Sept 2026: a verification scan of the same pages no longer found the failure, and the Remediation Evidence Package with that scan was issued.

sections/header.liquid Changes to sections/header.liquid: 1 added, 0 removed

Changes to sections/header.liquid: 1 added, 0 removed
Line after Change Code
42 {%- render 'icon', icon: 'search', size: 20 -%}
43 Added <span class="visually-hidden">{{ 'general.search.search' | t }}</span>
44 </button>

  • 102

    automated checks

    run in a scan: the rules of axe-core and Validiscan’s own checks

  • 35

    manual checks

    done by a person, for what no automated check can prove

  • 4

    platforms

    Shopify, Shopware, WooCommerce and Magento

  • 5

    languages

    English, German, Danish, French and Spanish, on this site and in the customer portal

Fix tiers, as they appear on every finding. AUTO: a ready-made fix that a recipe applies to your theme. ASSISTED: a fix drafted for your code (with AI only if you agree) and reviewed by a person before delivery. MANUAL: a decision only you can make, such as the words of a caption; listed with guidance, not changed.

Three things leave a project.

Fixes in your own code, a dated record of the work, and a weekly check that reports a fix that fails again.

  1. Fixes in your code

    A pull request or a patch bundle that your developer or agency reviews before anything goes live; on Shopify also an unpublished copy of your theme that you preview and publish yourself.

    validiscan/a11y-20260924-9f8e7d6c

    3 changes, one per fix 0 on your live shop

    Example data

  2. The Remediation Evidence Package

    A dated record of what was tested, what was changed and what the verification scan confirmed, with a draft accessibility statement. Evidence, not a certificate.

    PDFDOCXJSON

    One zip, SHA-256 checksums, every scan dated

  3. Regression protection

    Optional. A weekly re-scan compares your shop with the verified baseline. When a fix fails again, you get an email that says what and where.

    1. Week 1: no regression
    2. Week 2: no regression
    3. Week 3: no regression
    4. Week 4: one regression, email sent
    5. Week 5: no regression
    6. Week 6: scheduled

    Week 4 found a regression: one email, one entry on the timeline.

    Example data

Why not an overlay app?

An overlay is a script that runs on top of your pages in the visitor’s browser. A source fix changes your own templates, styles and code.

Accessibility overlay

Where does the change live?
In the provider’s script, which loads with every page
Can your developer or agency review it?
Not as a change to your code
What stays when the contract ends?
Nothing: the script is removed and your pages are as they were

Source fix, as Validiscan delivers it

Where does the change live?
In your theme’s own files
Can your developer or agency review it?
Yes, line by line, as a pull request or a diff
What stays when the contract ends?
The change, because it is part of your own code

What overlays change and what they leave as it was

Five steps. You decide what goes live.

Every step from your side

  1. Baseline scan

    Your shop against WCAG 2.2 AA, at desktop and phone size, plus the manual checks.

    Your part Confirm in writing that your shop may be scanned.

  2. Changes to your code

    What code can fix is fixed, reviewed, and delivered as a pull request, a theme copy or a patch bundle.

    Your part Review and publish it, or let your agency do it.

  3. Verification scan

    Once the changes are live, the affected pages are scanned again.

    Your part Tell Validiscan when the changes are live.

  4. Remediation Evidence Package

    The record of the result: PDF, DOCX and JSON in a zip, with the date of every scan.

    Your part File it, and have the draft accessibility statement reviewed.

  5. Regression protection

    Optional. A weekly re-scan against the verified baseline, with an email when something regresses.

    Your part Decide whether you want it.

How long a project takes depends mostly on steps 2 and 3: they wait for you or your agency to review the change and put it live.

Four platforms. Fixes land where your theme lives.

How fixes reach each platform

20 ready-made fixes on each platform, for failures such as a missing page language or a page that blocks zoom on phones, plus fixes written for your code.

What a scan finds, and what a person checks.

55

WCAG 2.2 success criteria at levels A and AA

Automated checks test some of them; a person checks the rest. So a first scan shows what can be proven from your code today, not the whole picture.

The scan finds

  • Images without a text alternative
  • Buttons without a name
  • Form fields without a label
  • A missing page language
  • A broken heading structure

A person checks

  • Whether the whole purchase path works with a keyboard
  • Whether an error message makes sense when it is read aloud
  • Whether a video’s captions are right
  • Whether the pages still work at 400 percent zoom

The method and the standards

Questions buyers ask

The short answers. Every page of this site says what the service does not do as plainly as what it does.

Will this help my shop meet the European Accessibility Act?

Yes, that is what it is for. EN 301 549, the European standard written for the EAA, uses WCAG 2.2 for websites, and WCAG 2.2 AA is exactly what we test and fix against. You also get a dated Remediation Evidence Package of every fix to show when someone asks. The final legal assessment stays with your lawyer.

Does anything change on my live shop?

Not without you. Changes arrive as a pull request, an unpublished theme copy or a patch bundle. Your developer or agency merges, or you publish, when you are satisfied.

What does a project not cover?

Findings that need your own content decisions (tier MANUAL, for example captions for your videos), third-party embeds such as payment or chat widgets, and PDFs. Platforms other than the four, and headless storefronts, are handled on request.

Is AI used on my shop’s code?

Only for fixes of tier ASSISTED, and only if you agree. AI drafting is off by default and switched on per shop. Every drafted change is reviewed by a person before it is delivered.

Start with a free check of your shop.

Send your shop’s address. Validiscan scans it and replies with every failure the scan can prove, with the page and the code.

Request a free check

Or write to info@validiscan.com.

What the free check covers, and what it leaves out
You send
your shop’s address
Pages scanned
up to 15
You get
every failure the scan can prove, with the page and the code
On your shop
public pages only; no login, nothing bought, no forms sent
What it is not
a full audit

Write to Validiscan

For a free check, give the address of your shop and its platform.

Validiscan uses what you send to answer you. Privacy notice