Accessibility compliance

Fix the accessibility-compliance gaps before a regulator, not a customer, finds them.

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.

Designer testing storefront accessibility with keyboard and screen-reader flows

SIGNS THE RISK IS REAL, NOT THEORETICAL

The accessibility risk is real, not theoretical — four reasons why.

01

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.

02

Keyboard navigation and screen readers fail on real checkout forms

The parts of the site that make money are usually the parts assistive technology struggles with most.

03

There's no audit trail to show conformance if someone complains

Good intentions aren't evidence — a regulator or procurement review asks for a record.

04

Design and engineering don't know which WCAG criteria actually apply

Without a shared list, every team guesses differently, and nothing gets consistently fixed.

OUR APPROACH

An automated scan, a manual audit or full remediation — these catch different things.

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.

Engineer comparing automated scan results against manual audit findings

Automated scan

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.

Manual audit

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.

Full remediation

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

An audit, real fixes, and a record you can actually show.

Team reviewing interface mockups across tablet, phone and monitor
01

A prioritised, evidence-based audit

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.
02

Fixes in the actual codebase, not a report

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.
03

A conformance record you can actually hand someone

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

Audit → Prioritise → Remediate → Verify.

01

Audit

In

Representative storefront and checkout journeys.

We do

We test with screen readers, keyboard-only navigation and automated scanners.

Out

A full list of violations, not a sample.

02

Prioritise

In

The audit findings.

We do

We rank violations by legal exposure, user impact and engineering effort.

Out

A fix order that spends budget where risk actually is.

03

Remediate

In

The prioritised list and codebase access.

We do

We fix markup, focus order, forms, contrast and dynamic content directly.

Out

Corrected journeys, not just a report of what's wrong.

04

Verify

In

The fixed journeys.

We do

We retest with the same methods used in the audit and document the evidence.

Out

A conformance statement you can hand to a regulator or buyer.

FREQUENTLY ASKED

Questions before the EAA deadline, not after a complaint.

Does the EAA apply if our company is outside the EU?

Yes — if you sell to consumers in the EU, the product and service obligations generally apply regardless of where the business is registered.

Is an automated scan enough to prove conformance?

No. Automated tools catch a fraction of WCAG criteria; manual testing with assistive technology is required for checkout and dynamic flows.

Do we need to rebuild the storefront?

Usually not. Most conformance gaps are fixable in markup, focus management and component behaviour without a rebuild.

What happens if we are not ready by the deadline?

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.

Let's start your accessibility audit.

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 →

7+years on the market
42+projects delivered
20+specialists on the team
8+countries served