I find the front-end defects that stop blind and keyboard-only customers from buying — and I fix them in your theme code. Not a widget. Not a PDF. A patch your developer can merge.
WCAG 4.1.2 This is the link to the shopping cart. It contains an icon and no text, and it has no accessible name.
Screen reader announces
link
Impact That is the entire announcement. A blind customer hears "link" and has no way to know the cart is there. Every item they added is unreachable.
I tested 192 certified online stores. Here is what came back.
Every one a member of a national e-commerce trustmark — real, established businesses that already submit to compliance checks. If anywhere was going to be clean, it was here.
178
reachable for automated testing
149
published no accessibility statement at all
0
running an accessibility overlay widget
3×
every page tested three times; only repeatable findings kept
No store is named, in the study or anywhere else. Findings go to the owner, not to a marketing page. Automated testing catches roughly a third of WCAG failures, so treat these numbers as a floor rather than a verdict. Read the full study and methodology.
Two legal systems, one technical standard
I work with stores selling into the European Union and stores selling in the United States. The obligation arrives very differently in each — but underneath, both point at the same success criteria, which means the same code work satisfies both.
European Union
European Accessibility Act
Applies to e-commerce serving EU consumers since 28 June 2025. Enforcement sits with national market surveillance authorities rather than with private claimants, which makes it slower and quieter than the US route.
Technical reference
The harmonised standard is EN 301 549 v3.2.1, which points at WCAG 2.1 AA. Version 4.1.1, raising that to WCAG 2.2 AA, is expected in the Official Journal around October 2026.
Documentation
A published accessibility statement is required. It is also the cheapest item on any remediation list, and the first thing an outside observer can check without reading a line of code.
Who is exempt
Micro-enterprises — broadly under ten staff and under €2M turnover — fall outside the scope.
United States
ADA Title III
There is no federal web regulation for private businesses. Enforcement happens through private litigation instead, and the volume is substantial: roughly four hundred federal filings a month, with e-commerce and retail the most targeted sector.
Technical reference
Courts and settlements commonly reference WCAG 2.1 AA — the same criteria the European standard points at.
What surprises people
In the first quarter of 2026, roughly a quarter of all filings were against sites that already had an accessibility overlay widget installed. Having a widget is not correlated with being safe.
Who is exposed
There is no size exemption. Small stores receive demand letters at the same rate as large ones.
I am not a lawyer and nothing here is legal advice. Whether either framework applies to your business, and what it requires of you, is a question for your counsel. What I can tell you is what the technical standards say, and what your code does or does not do.
Four ways to work with me
Start with the free one. If the findings are not worth acting on, you have lost nothing.
Step one
First findings
I run your storefront, a product page and your cart in a real browser, three times each. You get the three to five defects that hurt customers most — what breaks, where, and for whom.
FreeTwo working days, no obligation
Try me
One defect, fixed
Pick the finding that worries you most. I fix it properly in your theme, hand you the patch, and re-test to show the difference. Small enough that you can decide on it in a minute, real enough that you see exactly how I work.
€90 / $99Fixed price, three working days
The work
Full fix pack
Every critical defect in your theme: labels, focus handling, contrast, ARIA that is wrong rather than missing. Full findings list with exact selectors, delivered as a patch your developer reviews and merges. Retested after.
€490 / $590Fixed price, agreed before I start
After
Monthly re-check
Themes get updated, apps get installed, agencies push changes. I re-run the scan every month and tell you what regressed, before a customer finds it.
€120 / $149Per month, cancel whenever, no term
Invoicing. In euro or US dollars, whichever suits your accounting — you choose when we agree the work, and the number does not move afterwards. Payment by bank transfer, due in 14 days; PayPal on request for smaller engagements. The invoice comes after delivery, not before.
How this actually goes
No contract to sign before you know what is wrong. No payment until the work is agreed and done.
01
You send a URL
One line of email is enough. I do not need access to anything — the scan runs against your public storefront, the same way a customer sees it.
02
You get the first findings, free
Within two working days: the three to five defects that hurt customers most, each with what it breaks and for whom. Yours to keep, hire me or not. The full list with exact selectors comes with the work itself.
03
Start small if you want
You do not have to commit to everything. Pick one defect, I fix that one for €90, and you see how I work before deciding anything else. No obligation after that.
04
Fixed price, agreed in writing
For the full job I tell you what I will fix, what I will not, and what it costs — before I start. The number does not move afterwards.
05
Patch, retest, invoice
You get the changes as a patch your developer reviews and merges, plus a re-scan showing the difference. The invoice comes after delivery, payable in 14 days by bank transfer in euro.
What I will not tell you
This market has a credibility problem. Being precise about the limits is the only way to be worth believing.
✕That you are "compliant." Nobody can certify that from a scan. Automated testing finds roughly a third of WCAG failures; the rest needs a human with a screen reader and time.
✕That a widget fixes this. Overlay tools sit on top of broken markup. In 2025 the FTC fined the largest vendor one million dollars over what it claimed those widgets do, and a quarter of US filings last quarter were against sites that had one installed.
✕That I am a lawyer. I write front-end code. Whether your obligations under the European Accessibility Act are met is a question for your legal advisor, not for me.
✕That I found everything. Every report I send separates what a machine proved, what still needs checking by hand, and what I did not look at.
The scanner is open source
The tool I use is public. It drives a real browser, runs axe-core against WCAG 2.1 AA, separates what is binding today from what becomes binding when the standard updates, and discards any finding that does not reproduce across three runs. Read it before you trust a number in it.