About Validiscan and the person who runs it
Validiscan is a web accessibility remediation service for EU online shops on Shopify, Shopware, WooCommerce and Magento. It scans a shop 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.
Who runs Validiscan?
Validiscan is run by one person, William Quaade Rasmussen, from Helsinge in Denmark. He reads and answers the email sent to info@validiscan.com, and he is the person who runs the scans of your shop, reviews the fixes and puts the Remediation Evidence Package together.
Details: who you write to, and who does the work
Validiscan is run by one person, William Quaade Rasmussen. He runs it from Helsinge in Denmark, and he is the person who reads and answers email sent to info@validiscan.com.
There is no sales team and no account manager. The person you write to is the person who runs the scans of your shop, reviews the fixes and puts the Remediation Evidence Package together.
Why fix the source code?
Validiscan fixes the shop’s source code because a fix there stays in place and can be read like any other change to the code. Once a change to the theme’s templates, styles or scripts is live, what failed is corrected for every visitor and every program that reads the page.
- The change is yours. It is an ordinary edit to your theme. When the project ends, the fix stays in your code.
- You see it before it goes live. The changes arrive as a pull request, an unpublished copy of your Shopify theme or a patch bundle. Your developer can read a pull request or a patch bundle line by line, and you can preview a theme copy before you publish it.
- Nothing is added on top. No script is added that rewrites your pages for visitors, and no widget appears on your shop.
- The result is checked. A verification scan checks the pages again once the fixes are live, and the Remediation Evidence Package records what was tested, what was changed and what the verification scan confirmed.
Details: what a fix in the theme changes, and where overlays are explained
Validiscan fixes the shop’s source code because a fix there stays in place and can be read like any other change to the code. Validiscan changes the templates, styles and scripts of the shop’s theme, so once a change is live, what failed is corrected for every visitor and for every program that reads the page.
What an accessibility overlay changes, and what it leaves as it wasHow is a project run?
A Validiscan project is run by William Quaade Rasmussen, the person who answers your first email, from the free check to the Remediation Evidence Package. Validiscan’s own software does the scanning, prepares the fixes and builds the package; he decides what is delivered.
- The free check. You send the address of your shop, and William runs the free check and writes back with what it found.
- Permission and access. Before a full scan, you confirm in writing that Validiscan may scan your shop. You also decide whether AI may draft fixes of tier ASSISTED, and how the changes reach your code.
- The baseline scan and the manual checks. William runs the baseline scan and works through a checklist of 35 manual checks, which covers every WCAG 2.2 criterion that no rule tests and some that rules test only in part.
- Every fix reviewed. A fix is delivered only after William has reviewed and approved it, whether it came from a deterministic recipe (AUTO) or was drafted for review (ASSISTED). Findings of tier MANUAL come with guidance, because they need a decision about your content or design.
- Verification and the package. Once the changes are live on your shop, a verification scan checks the pages again. The Remediation Evidence Package then records the result, with the date of every scan.
Details: who decides what is delivered, and each step from your side
William, the person who answers your first email, runs the project from the free check to the Remediation Evidence Package. Validiscan’s own software does the scanning, prepares the fixes and builds the package; William decides what is delivered.
Each step from your side, with what you do and what you receiveCan I see work for other shops?
Not yet. Validiscan has no customer projects to show, and so this site has no testimonials, client logos or case studies. What you can see now is real output of Validiscan’s software, with example data marked “Example data”, and the most direct sample is the free check of your own shop.
What you can see now is real output of Validiscan’s software:
- The text of a pull request for a fictional example shop, as a developer would receive it, marked “Example data”, on how a project runs
- The code before and after each fix recipe, marked “Example data”, on the platform pages
- The sections of the Remediation Evidence Package, under the titles the package prints
Details: what this site does not show yet, and the most direct sample
Not yet. Validiscan has no customer projects to show, and so this site has no testimonials, client logos or case studies.
The most direct sample is the free check of your own shop.
Which company is behind Validiscan?
Validiscan is the brand of a company registered in Denmark: Validiscan ApS, Rishøjvej 9, 3200 Helsinge, Denmark, CVR 46367405. The legal notice has the full provider information.
| Item | Details |
|---|---|
| Name | Validiscan ApS |
| Registered address | Rishøjvej 9, 3200 Helsinge, Denmark |
| info@validiscan.com | |
| Company register | Central Business Register (CVR), Denmark |
| CVR number | 46367405 |
| Responsible person | William Quaade Rasmussen |
Details: the legal notice, and where customer data is kept
Validiscan is the brand of a company registered in Denmark: Validiscan ApS, Rishøjvej 9, 3200 Helsinge, Denmark, CVR 46367405. The legal notice has the full provider information.
Security and data describes where customer data is kept and who can see it.
Does Validiscan’s own website meet the standard it checks?
Validiscan’s website aims to meet WCAG 2.2 AA, the standard Validiscan checks shops against. Automated tests check its pages with axe-core and test keyboard use, reflow, zoom and colour contrast; no person has tested it with a screen reader yet. Its accessibility statement lists each test and what has not been tested yet.
- Aims to meet
- WCAG 2.2 AA
- Tested automatically
- axe-core, keyboard use, reflow, zoom and colour contrast
- Not tested yet
- use with a screen reader, by a person; the accessibility statement lists the rest
Details: the tests, and where each one is listed
Validiscan’s website aims to meet WCAG 2.2 AA, the standard Validiscan checks shops against. Automated tests check its pages with axe-core and test keyboard use, reflow, zoom and colour contrast; no person has tested it with a screen reader yet. The accessibility statement for validiscan.com lists each test and what has not been tested yet.
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 checkOr 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