The European Accessibility Act applies even when the business isn't EU-based
If you sell to EU consumers, the obligation generally follows the sale, not your company's address.
Accessibility compliance
For storefronts that need to meet EN 301 549 / WCAG 2.1 AA before enforcement, a complaint, or a lost procurement deal forces the issue.
SIGNS THE RISK IS REAL, NOT THEORETICAL
If you sell to EU consumers, the obligation generally follows the sale, not your company's address.
The parts of the site that make money are usually the parts assistive technology struggles with most.
Good intentions aren't evidence — a regulator or procurement review asks for a record.
Without a shared list, every team guesses differently, and nothing gets consistently fixed.
OUR APPROACH
Each level of testing finds a different slice of the problem. Knowing which one you actually need keeps the budget pointed at real risk instead of a checkbox.
Catches a meaningful fraction of WCAG violations fast and cheaply — contrast, missing labels, structural issues.
Can't catch what it can't test: real keyboard flow, screen-reader behaviour, or dynamic checkout states.A person navigates checkout and cart with a keyboard and a screen reader, the way a real user would.
Needed before any conformance claim — automated tools alone can't support one.Fixes get made directly in the codebase, then retested against the same journeys.
This is where the actual legal exposure gets closed, not just documented.WHAT WE CAN OWN
Representative journeys — search, product, cart, checkout — get tested with screen readers, keyboard-only navigation and automated scanners, then ranked by legal exposure and user impact.
We rank the risk; deciding how much budget to spend fixing lower-priority items stays a business call.Markup, focus order, forms, contrast and dynamic content get corrected in the highest-risk journeys first, then retested to confirm the fix actually holds.
A full redesign is rarely needed — most gaps are fixable without rebuilding the storefront.A documented statement and evidence package exist for regulators, customers or a procurement review — not just an internal note that work happened.
Member-state enforcement and penalties vary; we document conformance, we don't represent the legal outcome.HOW WE WORK
Representative storefront and checkout journeys.
We test with screen readers, keyboard-only navigation and automated scanners.
A full list of violations, not a sample.
The audit findings.
We rank violations by legal exposure, user impact and engineering effort.
A fix order that spends budget where risk actually is.
The prioritised list and codebase access.
We fix markup, focus order, forms, contrast and dynamic content directly.
Corrected journeys, not just a report of what's wrong.
The fixed journeys.
We retest with the same methods used in the audit and document the evidence.
A conformance statement you can hand to a regulator or buyer.
FREQUENTLY ASKED
Yes — if you sell to consumers in the EU, the product and service obligations generally apply regardless of where the business is registered.
No. Automated tools catch a fraction of WCAG criteria; manual testing with assistive technology is required for checkout and dynamic flows.
Usually not. Most conformance gaps are fixable in markup, focus management and component behaviour without a rebuild.
Enforcement and penalties vary by member state; the practical risk is complaints, procurement exclusion and remediation under time pressure — starting the audit now avoids that.
Tell us which journeys matter most to your revenue — we'll tell you where the real legal exposure is hiding.
Start an accessibility audit →Finding this is actually a sign the whole platform needs replacing, not just fixing? See ecommerce replatforming →