An accessibility failure is a locked front door, and since June 2025, EU law says the door must be open. The European Accessibility Act covers e-commerce among its services, and the gap between where most storefronts sit today and where the law puts the floor is not a detail. It is the operating problem this article is about.
The line moved from principle to law.
The European Accessibility Act is an EU directive that aims to improve the functioning of the internal market for accessible products and services. E-commerce is among the services it covers. That framing matters: this is not a voluntary standard or a reputational nudge.
New accessibility obligations for online shop operators apply starting from June 2025. The scope is broad. The only formal exceptions are micro-enterprises with fewer than ten employees and no more than two million euros in annual turnover. If your shop sits above that threshold, the floor applies.
A floor set in law is not a feature request that can slip to next quarter. It is the new definition of a storefront that is open. The conversation about accessibility has shifted registers, from aspiration to obligation, and the operator's job is to treat it accordingly.
Check the micro-enterprise threshold against your own headcount and turnover before assuming the exemption applies; the threshold is narrow, and growing past it does not grandfather you in.
The baseline is failing that floor at documented scale.
In WebAIM's 2026 analysis of the top one million home pages, 95.9% had detected WCAG 2 failures. The average page carried 56.1 errors. Those are not outlier shops with neglected codebases. Those are the pages most people visit most often.
The average storefront is not slightly below the legal line. It is structurally below it. Errors of this density do not appear because teams made a few bad decisions. They appear because accessibility was never a gate in the build, never a property of the design tokens, never a field in the publishing routine. It was always the thing addressed after launch, under pressure, by a consultant with a checklist.
“Being average is now the risky position.”
A craft problem, not a legal one.
An accessibility failure is almost always a conversion failure wearing its legal name. The text a screen reader cannot parse is the same text a guest cannot skim on a phone in sunlight. The button a keyboard cannot reach is the button a hurried thumb misses. The form a label does not describe is the form that gets abandoned at the last step.
The overlap between accessibility and plain craft is nearly total. Low contrast is a design decision that excludes users in bright light, not just users with visual impairments. Missing labels on form fields are a usability regression for everyone filling out a checkout form quickly. Focus states that disappear are a navigation failure for anyone who has put down the mouse.
This is why the fix belongs to the build, not to a lawyer. Legal review tells you whether you are exposed. Craft built into the loop is what actually closes the gap.
The operating-loop move.
A one-off audit bought under enforcement pressure tells you where you are once. It does not hold the floor. A redesign triggered by a complaint costs an order of magnitude more than a floor maintained week by week inside the build. The operating-loop move is to stop treating accessibility as a project and start treating it as a property of the system.
Automated checks wired into the build mean a regression fails before it ships, not after a customer reports it. Contrast ratios and focus states that live in the design tokens mean every new page inherits a passing baseline rather than starting from zero. Alt text as a required field in the publishing routine means the question is never "did anyone remember?" but "did the system accept it?". A quarterly walkthrough of the money paths with a keyboard and a screen reader catches what automation misses.
Each of those is a small, repeatable operation. Together they hold a floor that a single audit cannot. The cost is a little every week. The alternative cost is a redesign.
A field checklist for the operating loop.
- Wire automated checks into the build. Accessibility regressions should fail the build before they reach production. Axe-core and similar tools integrate into most CI pipelines without significant overhead.
- Put contrast and focus states in the design tokens. If passing contrast ratios and visible focus indicators are properties of the token set, every new component starts compliant rather than needing a retrofit.
- Make alt text a required publishing field. Not a recommendation in a style guide: a field the CMS will not accept empty. The discipline lives in the tool, not in the team's memory.
- Walk the money paths each quarter. Find, book, order, pay, with a keyboard only and then with a screen reader. Fix what blocks you, in order of the revenue that path touches.
- Treat the first failure as a calibration, not a verdict. If automated checks surface 40 errors on the first run, prioritise by path impact rather than count. The goal is a floor that holds, not a perfect score on day one.
A hospitality operator we audited last quarter had passing contrast in the design system but had overridden it in three promotional banner components. Wiring the build check caught the override on the next deploy before it reached guests.
Common questions.
Does this law apply to a small shop with only a few staff?
The law carves out micro-enterprises with fewer than ten employees and up to two million euros in turnover, so the smallest shops may sit outside the formal duty. The operator's read is narrower: the floor still applies commercially. The guests, platforms, and corporate clients above you inherit it, and craft that excludes users leaks revenue at any size. Verify your own position against the threshold rather than assuming the exception applies.
Will an accessibility overlay widget satisfy the requirement?
An overlay repaints the door. It does not unlock it. The failures that matter live in the page itself: structure, labels, contrast, focus states. A bolt-on layer cannot rewrite the underlying markup. Fix the craft in the build, where it is cheapest and where the fix actually holds.
Where should an operator start without commissioning a full audit?
Walk the money paths first: find, book, order, pay, with a keyboard and a screen reader, and fix what blocks you in order of the revenue that path touches. Then wire automated checks into the build so the floor holds. An audit tells you where you are once. The loop keeps you above the line every week.
Does accessibility work overlap with general site quality, or is it a separate track?
The overlap is nearly total. Contrast, label clarity, focus visibility, and navigable structure are properties of good craft on any screen, for any user. Running accessibility as a separate track inflates the cost and misrepresents the problem. It belongs inside the build and design process, not alongside it.
If your storefront needs an accessibility audit or a build loop that holds the floor without a recurring engagement, start a conversation or read how we structure this kind of work in our hospitality systems practice.
