Accessibility compliance for D2C stores.

Two regimes, one technical standard

Accessibility compliance sounds like several problems and is mostly one. Europe legislates a standard and enforces it through regulators. The United States has no ecommerce-specific rulebook and enforces through private lawsuits. Both effectively land on the same target: the Web Content Accessibility Guidelines at Level AA. Build to that once and you have addressed the substance of both.

What follows is how the obligations actually apply to a D2C store, not legal advice. If you sell meaningfully into the EU or the US, the specifics for your entity are worth confirming with counsel.

The European Accessibility Act

The EAA became enforceable on 28 June 2025, and it is the one most D2C founders underestimate, for three reasons.

• It follows the customer, not the company. It applies to ecommerce services offered to consumers in the EU. A store in India, the UK or the US that ships to EU consumers is in scope. Being based outside Europe is not an exemption.
• The standard is specific. Compliance runs through the harmonised standard EN 301 549, which adopts WCAG 2.1 Level AA for web content. That is a testable technical bar, not a statement of intent.
• The microenterprise exemption is narrow. It requires fewer than 10 employees and annual turnover or balance sheet total not exceeding 2 million euros. Both conditions, not either. It applies to services rather than products, and it stops applying as soon as you outgrow it, with no transition period. Any brand of the size that hires an agency is generally past it.

Enforcement is by national market surveillance authorities in each member state, and penalties are set nationally. The practical risk for most brands is a complaint from a customer or a competitor triggering an authority's attention, rather than proactive auditing.

The United States

Different mechanism, similar destination. Private ecommerce sites fall under ADA Title III, which has no published web standard and no compliance deadline. What it has instead is litigation: over 5,000 digital accessibility lawsuits were filed across federal and state courts in 2025, and ecommerce accounts for the large majority of filings. Courts have consistently treated online stores as places of public accommodation, and settlements typically require remediating the site's actual source code to WCAG standards.

One point of confusion worth clearing up. You will see references to an ADA Title II deadline in April 2026, since extended to 2027 and 2028. That rule applies to state and local government entities, not to private businesses. If you are a D2C brand, it is not your deadline, and "we have until 2027" is a misreading.

What WCAG 2.1 AA actually requires

The specification is long. The parts that fail on real stores are a short list.

• Contrast. 4.5:1 for normal text against its background, 3:1 for large text and for the visual boundaries of controls. Light grey on white and thin type over hero imagery are the two most common failures, and both usually originate in the brand palette rather than the build.
• Keyboard operability. Every interactive element reachable and usable with a keyboard alone, in a sensible order, with no traps. Drawers, modals and popups are where this breaks: focus must move into the dialog when it opens, stay inside while it is open, and return to the trigger when it closes.
• Visible focus. The keyboard user has to be able to see where they are. Removing focus outlines because they looked untidy is one of the most common single-line causes of failure.
• Text alternatives. Meaningful alt text on product images, empty alt on decorative ones, real labels on form fields rather than placeholder text doing the job.
• Form errors. Errors identified in text, associated with the field, and describing how to fix the problem. Colour alone is not identification.
• Structure. Real heading hierarchy, real buttons and links rather than clickable divs, landmarks that let a screen reader user skip to content.
• Target size and pointer alternatives. WCAG 2.2 adds requirements here, and it is the direction of travel even where 2.1 is the current legal reference. Building to 2.2 costs little more.

Where Shopify stores fail specifically

• The cart drawer and modals. Focus management is wrong in a large share of themes. Open the drawer with a keyboard and you will often find focus still behind it on the page.
• Popups. Newsletter and discount popups that cannot be dismissed with the escape key, or that trap focus with no reachable close button.
• Variant pickers. Colour swatches implemented as unlabelled divs, so a screen reader announces nothing useful and a keyboard cannot reach them.
• Carousels and product media. Auto-advancing galleries with no pause control and no keyboard access.
• Third-party app widgets. Reviews, chat, loyalty and upsell widgets are frequently the least accessible things on the page, and they are code you did not write. This is a procurement question as much as a build one.
• Checkout. Shopify maintains the checkout itself, which helps, but anything you customise into it is yours to get right.

Overlays are not a fix

Accessibility overlay widgets promise compliance from one script tag. They do not deliver it. They cannot repair semantics they cannot infer, they routinely interfere with the assistive technology a user has already configured, and their presence has not prevented lawsuits. Settlements and consent decrees consistently require source-level remediation.

The narrow honest use for an overlay is as a temporary mitigation while real remediation is scheduled. Sold as a substitute for fixing your theme, it is a subscription that buys the appearance of compliance.

A remediation path that works

• Audit with both tools and hands. Automated scanners catch perhaps a third of issues, mostly contrast, alt text and label problems. The rest needs a person navigating the store by keyboard only and listening to it with a screen reader. Do the keyboard pass first, it is fast and it finds the worst failures.
• Fix in the theme source. Semantics, focus management, labels, contrast tokens. Fixing at source means the fix survives content changes and applies everywhere the component appears.
• Prioritise by revenue path. Product page, cart, checkout and search first. A perfectly accessible blog attached to an unusable cart helps nobody, legally or commercially.
• Set a rule for apps. Any new storefront app gets checked for keyboard operability before it goes live. This is the same discipline as an app audit, applied at install time.
• Publish an accessibility statement. State the standard you work to, known gaps, and a contact route for problems. The EAA expects this kind of information, and in the US a documented, ongoing programme is materially better ground to stand on than silence.
• Retest on a schedule. Themes update, apps update, campaigns add markup. Accessibility regresses like performance does, so it belongs in ongoing maintenance rather than in a one-off project.

The commercial case, not just the legal one

Roughly one in six people worldwide lives with a significant disability, and the accessible version of a store is usually the better one for everyone: legible contrast, clear labels, forms that explain their errors, controls large enough to hit on a moving train. The same fixes that satisfy WCAG remove friction for customers who never think about accessibility at all, which is why the work tends to show up in conversion as well as in compliance.

Common mistakes

• Assuming Shopify handles it. Shopify provides an accessible checkout and accessible base themes. Your theme customisations, your apps and your content are yours, and "we use Shopify" has never been a defence.
• Buying an overlay and considering it closed. It does not remediate source, and it has not stopped claims.
• Treating the ADA Title II 2027 date as your deadline. That rule covers public sector entities. Private ecommerce exposure is immediate and litigation-driven.
• Running the scanner and stopping there. Automated tools miss most of what actually blocks a user, including nearly all focus and keyboard failures.
• Fixing once. The next theme update or campaign popup undoes it unless someone is retesting.

FAQ