How to Make Your Shopify Store EAA & WCAG Compliant

Your storefront probably converts perfectly well for most of the people who land on it. That is exactly why the gap is easy to miss. The shoppers it quietly locks out — someone navigating by keyboard, someone using a screen reader, someone who cannot read low-contrast grey-on-white — are now the same people who can file a complaint. As of 28 June 2025, that is no longer a customer-experience footnote. It is a legal line.

This note explains what Shopify EAA compliance actually requires, where Shopify themes tend to fail it, and how to make your Shopify store accessible for real rather than for show. No fear-selling, no jargon you have to decode twice.

The deadline that already passed

The European Accessibility Act (EAA) came into force across the EU on 28 June 2025. It applies to e-commerce regardless of what you sell and regardless of where your company is registered — if you accept orders from consumers in the EU, you are in scope. The operative technical benchmark is WCAG 2.1 Level AA, carried through the harmonised European standard EN 301 549.

New services placed on the market after that date had to comply immediately. Services already trading before it have until 28 June 2030 to bring everything in line, but that runway shrinks the moment you make a material change to the store. Penalties vary by member state, but reporting on the Act points to fines that can reach around €100,000 per violation, with additional penalties for publishing inaccurate accessibility information.

If you are a UK business, the EAA still reaches you the second you sell into the EU. At home, the Equality Act 2010 already expects you to make "reasonable adjustments" for disabled users, and WCAG 2.2 Level AA has become the recognised yardstick for what reasonable looks like. The UK has not transposed the EAA into domestic law, but if you trade both sides of the Channel, one consistent standard across the whole store is simply less to maintain.

Why Shopify stores draw the complaints

It is worth being honest about the risk picture, because it is not abstract. Reporting across the accessibility industry describes thousands of digital accessibility lawsuits filed in the United States each year — roughly 4,605 ADA website cases in 2024 by one widely-cited count — and a large share land on e-commerce. Shopify is one of the most-targeted platforms, behind only custom-coded sites, and the businesses sued are overwhelmingly smaller ones, not household names. A demand letter does not check your turnover first.

The reason Shopify shows up so often is not that Shopify is careless. It is that a polished theme can hide non-compliant markup beautifully. The site looks finished, so nobody checks the parts a sighted mouse-user never touches. That is the trap: visual completeness and Shopify WCAG 2.2 compliance are not the same thing.

Where Shopify themes quietly fail WCAG

Most failures on a Shopify store cluster into a handful of repeat offenders. If you only ever check these, you will catch the majority of what matters.

• Missing or useless alt text. Product images carry the buying decision, yet many are uploaded with no alternative text — or with a filename like "IMG_4471". Missing alt text is reported as the single most common issue behind accessibility complaints. A screen-reader user hears silence where your hero shot should be.
• Colour contrast. The most frequent WCAG failure of all. Normal-size text needs a contrast ratio of at least 4.5:1 against its background. Pale grey captions, washed-out "sale" badges and low-contrast button text all fall short — and they are the easiest thing to introduce while chasing a clean, minimal look.
• Keyboard operability. Every interactive element must be reachable and usable with the Tab key, and operable with Enter or Space. Mega-menus, image carousels, quick-view modals and custom drop-downs are the usual culprits — they work with a mouse and trap or ignore a keyboard.
• Unlabelled forms. Every input needs a programmatically associated label, and error messages must be specific. A checkout field that only shows its meaning through grey placeholder text disappears the moment a shopper starts typing.
• WCAG 2.2 additions. The 2.2 update, the current standard, adds requirements worth knowing: interactive targets should be at least 24×24 CSS pixels, focus indicators need a 3:1 contrast ratio, and the focused element must not be hidden behind a sticky header or footer.

None of these are exotic. They are the small details a theme ships with and a busy merchant never revisits.

The honest truth about accessibility apps and overlays

This is the part most guides skip, so we will not. When merchants search "Shopify accessibility app vs code", they are usually hoping a one-click widget solves it. It does not, and relying on one can make things worse.

Overlay widgets work on the rendered page — the version the browser paints — not on your source code. A screen reader still meets the same broken HTML underneath; the overlay only paints over it. This is why a large body of disability advocates, reportedly more than 700 accessibility experts, signed a public letter against overlay use, and why a meaningful slice of accessibility lawsuits in 2025 targeted sites that already had a widget installed.

It went further than reputation. In early 2025 the US Federal Trade Commission acted against a leading overlay vendor, accessiBe, over claims that its AI widget could make any site compliant when it could not, alongside allegations of paid reviews dressed up as independent ones. The April 2025 final order imposed around $1 million in penalties and a 20-year ban on the company guaranteeing compliance it cannot prove. The lesson is not "all tools are bad" — it is that a layer on top of the page is not the same as a fix in the page.

That does not mean code is the only honest answer for everything. Automated scanners — the genuinely useful kind — are still valuable for continuous monitoring. Just know their ceiling: across the industry, automated testing is understood to catch only around 30–40% of WCAG issues. The remaining 60–70%, including whether your alt text is actually accurate and whether reading order makes sense, needs a human. A real Shopify accessibility audit pairs automated scanning with manual keyboard-and-screen-reader testing. Anything sold as "fully compliant, automatically" is selling the 30%.

How to actually make your Shopify store accessible

The durable fix lives in the theme, because that is where the markup lives. Here is the order we work in, roughly highest-impact first.

1. Audit against reality, not a badge

Run an automated scan for the easy wins, then test by hand: unplug the mouse and navigate the whole purchase journey with the keyboard alone. Then run a screen reader (VoiceOver on Mac, NVDA on Windows — both free) across a product page and checkout. You will find the real problems in minutes, and they will not be the ones the scanner flagged.

2. Fix contrast and alt text first

These are the highest-frequency complaints and among the cheapest to resolve. Adjust theme colour tokens so text clears 4.5:1, and write meaningful alt text describing what each product image shows — colour, material, what the model is wearing — not a filename. For decorative imagery, mark it as such so screen readers skip it cleanly.

3. Make the theme keyboard-complete

This is where Liquid and theme JavaScript earn their keep: visible focus states, logical tab order, menus and modals that open, trap focus correctly and close on Escape. An accessible Shopify theme handles this in its components rather than leaving it to a plugin to paper over later.

4. Repair the forms and checkout

Associate every label, give error messages real text, and make sure validation is announced, not just shown in red. The checkout is the most expensive place to lose a shopper who was ready to pay.

5. Document and monitor

The EAA expects you to be able to describe your accessibility position. An accessibility statement, plus ongoing automated monitoring so a future theme update does not silently undo your work, keeps you defensible. One careless app install or a "quick" template tweak can reopen a hole you closed.

What this is really protecting

It is tempting to treat all of this as box-ticking to avoid a letter. The more useful framing: every barrier you remove is a sale you were quietly turning away. Larger, better-keyboarded buttons help everyone on a phone. Clear contrast helps anyone shopping in bright sunlight. Labelled forms reduce checkout abandonment across the board. Accessible stores tend to convert better not because of a moral premium, but because friction is friction for everyone — and you were paying for it on every visit.

And the plain version, because you deserve it: if your store is small, mostly text and images, on a current well-built theme, you may be a weekend of focused work away from compliant — most of it contrast and alt text you can do yourself. You may not need anyone. If you are running heavy customisation, a bespoke checkout, or an older theme that has been patched by five different hands, that is where the work gets real, and where getting it wrong in code costs more than getting it right once.