Shopify Store Accessibility: Which Parts Are Yours

One of three things usually brings a merchant to this question. A customer writes to say they could not finish an order. A business buyer sends a questionnaire with a line asking for your accessibility statement. Or somebody mentions that Europe had a deadline, and you find that it passed over a year ago.

All three arrive with the same assumption underneath: that accessibility is something the platform settles, because Shopify talks about it. Part of that is true, and the part that is true is precisely drawn — Shopify says which surfaces it tests, publishes conformance reports for four of its products on its accessibility page as we read it in August 2026, and states in its own words where its work stops and yours begins.

This page is that line, in both directions. What Shopify covers, what stays with you, what the law in the United States asks when it has published no technical standard, what the European directive asks now that its date is behind us, and what a widget can and cannot settle.

The Quick Verdict

Find your row, then read the section it points at. Nothing below contradicts anything here.

Two Different Things Are Called an Accessible Shopify Store

The confusion is not careless. Shopify does publish an accessibility statement, it does name a standard, and it does test against it.

What that statement describes is Shopify's own content and features. Nothing in it is a measurement of a particular merchant's storefront, because no company can measure a storefront it does not control.

Shopify says the second half plainly, and says it to merchants rather than to developers.

That sentence is worth reading twice, because it settles the shape of the whole topic. Following the published guidance is necessary and it is not sufficient. The same split runs through other compliance questions on this platform — our guide to which parts of PCI compliance are yours takes the same line through card data, and the reasoning there transfers almost word for word.

What Shopify Tests, and What It Publishes

The most useful way to read those reports is not as a grade but as a map of surfaces. Every product with a published report is a surface Shopify runs. Everything else on the list below is somewhere you have a hand in, whether you wrote the code or installed something that did.

Product conformance reports and their scopes read on shopify.com/accessibility and the linked report pages, August 29, 2026. Built for Shopify requirements read on shopify.dev the same day.

The Dawn row is the one that repays a second look. Dawn is the only theme among the four reports listed on Shopify's accessibility page as we read it on August 29, 2026. The Dawn report is dated November 2021, and it marks criteria as only partially supported, noting among other things that some imagery text alternatives duplicate heading text content and that page landmarks may be missing.

Horizon, the theme Shopify now leads with, was not among the four reports on that page when we read it on August 29, 2026. Neither fact is a complaint; both are inputs to how much you can infer about your own theme from what the platform publishes.

Why the Theme Code Is Named as Yours

Read that as an allocation of surfaces rather than as a disclaimer. The admin and the checkout are Shopify's to describe, and it describes them. The theme is yours to change, which is exactly why the platform cannot make a statement about it — the same theme, in two stores, is two different pages after a year of edits.

The practical consequence shows up in what a questionnaire can and cannot be answered with. Shopify's conformance reports answer questions about Shopify's products. A question about whether a customer can buy from your store with a keyboard is answered by opening your store and using a keyboard.

What WCAG Asks, and Why Everything Says AA

The Web Content Accessibility Guidelines are published by the W3C, not by any government, and they are written as testable criteria rather than as advice. The structure matters for reading everything else on this page: the guidelines define three levels of conformance to meet the needs of different groups and different situations.

• Level A — the lowest of the three.
• Level AA — the middle level, and the one every document on this page points at.
• Level AAA — the highest.

Why AA and not AAA is the question worth a sentence. AAA is the highest level, and Shopify's own Admin conformance report states outright that Level AAA is not supported and omits that table from the report. AA is where the documents converge — not because it is a legal floor, but because it is the level the bodies writing about this have each chosen independently.

2.1, 2.2 or None: Which Rule Names Which Version

Getting this straight early saves a lot of second-guessing later, because the number most often quoted as “the legal standard” comes from a rule about state and local governments.

Shopify accessibility page and DOJ rule read August 29, 2026; the European Commission states that both versions of EN 301 549 build heavily on WCAG 2.1.

The United States: a Duty With No Deadline

The American half of this topic has no date in it, and that absence is the whole difficulty. There was never a cutoff to prepare for, which means there is also nothing to have missed — and nothing to point at when somebody asks whether you are compliant.

Who Title III Covers, and Who Answers for a Store

The Department of Justice gives examples of the businesses and nonprofits it has in mind, and the list is worth scanning for the entry that looks like yours:

• Restaurants
• Hotels
• Retail stores
• Movie theaters
• Private schools
• Doctors' offices
• Hospitals
• Day care centers
• Gyms
• Organizations offering courses or examinations
• Privately operated transit

Alongside that list the department states the general requirement plainly: businesses must provide people with disabilities an equal opportunity to access the goods or services that they offer.

Reading that definition against a Shopify store gives the answer to the question merchants usually ask first, and it is worth being explicit that it is a reading rather than a quotation. What Title III describes is the business open to the public, and in a Shopify store that is the merchant — the platform is the supplier of the software, and the merchant is the business selling to the shopper.

Why There Is No Official Checklist

This is not an oversight anybody is about to correct. The DOJ formally withdrew its earlier attempt at rulemaking here: as of December 26, 2017, four previously announced advance notices were withdrawn, including the one on accessibility of web information and services of public accommodations, and the notice records that no rulemaking document on Title III web accessibility had been published since the 2010 notice.

None of the DOJ pages we read on August 29, 2026 describes a current rule — final or proposed — that sets a technical standard, meaning a named WCAG version and level, for private businesses under Title III. What the department did say, in the preamble to the rule it published for public bodies, is that the obligations of Title III entities are untouched by it.

One more absence is worth stating rather than working around, because it is the number readers most often arrive looking for. No ada.gov or justice.gov page we read on August 29, 2026 publishes a count of web-accessibility lawsuits. That is why this article quotes no such figure: the counts in circulation come from private law firms compiling their own datasets, and we have no official baseline to check them against.

The 2024 Rule Everyone Quotes Is Not About Your Store

Almost every article that tells a merchant “the legal standard is WCAG 2.1 AA” is quoting this rule. It is a real rule with real dates, and it binds public entities. The DOJ's own summary puts it in those terms: state and local governments must make sure their web content and mobile apps meet WCAG 2.1 Level AA within three or four years of publication, depending on their population.

Those dates then moved. An interim final rule effective April 20, 2026 extended the compliance date for entities with a population of 50,000 or more to April 26, 2027, and for smaller entities and special district governments to April 26, 2028. The same document states that it only pertains to the department's regulations implementing title II, and that the regulations implementing title III are not addressed in that rulemaking.

If There Is No Standard, What Do You Aim At?

The flexibility is genuine, and it cuts both ways. It means no auditor can hold you to a criterion number as if it were law, and it also means “we followed a checklist” is not by itself an answer. What the department points at as helpful guidance is exactly the standard the rest of this page keeps naming — the existing technical standards, WCAG and Section 508 among them.

For a Shopify merchant that lands somewhere convenient. The level Shopify tests its own surfaces at, the level the European standard builds toward, and the level American regulators wrote into the one rule they did publish are the same level. Aiming at AA is not a legal position; it is the only target with any agreement behind it.

The European Union: the Deadline Passed on 28 June 2025

The directive is Directive (EU) 2019/882, and its Article 2(2) reads, without prejudice to Article 32, that it applies to the listed services provided to consumers after 28 June 2025. The word consumers is the directive's own, and it stays that way here rather than being softened into customers or buyers: it is doing work in the sentence, and what it excludes is a question for a lawyer rather than for this page.

E-commerce services are item (f) on the Article 2(2) list, alongside electronic communications, access to audiovisual media, certain passenger transport elements, consumer banking, and e-books and dedicated software. Recital 43 reads the scope broadly, saying the e-commerce obligations should apply to the online sale of any product or service.

The Dates, and Which Ones Are Not About You

The reason to lay these out rather than to name one date is that only the 2025 entry starts anything for an online store. The others bind Member States, cover emergency communications, cover physical terminals, or turn on products a service provider was already using — and reading the 2027 line as yours would be an expensive misunderstanding of what Article 4(8) covers.

Does It Reach a Store With No EU Address?

Article 3(4) is the whole of it: a service provider means any natural or legal person who provides a service on the Union market or makes offers to provide such a service to consumers in the Union. A store that ships to Germany and prices in euros is making offers to provide a service to consumers in the Union whatever address is on its invoices.

Being precise about the status of that sentence matters, because a good deal of what is written about the directive overstates it. The full text of the directive we read on August 29, 2026 contains neither the phrase “established outside” nor the phrase “irrespective of where established”. The reach follows from how the definition is written, not from a clause addressed to non-EU service providers, and anyone telling you the directive says so in as many words is describing a sentence that is not there.

The Exemption That Removes the Duty Outright

This is the single most consequential paragraph of the European half, and it is also the one most often reported as a discount when it is actually a removal. Read the three bands together.

Articles 3(23), 3(24), 4(5) and 14(1) of Directive (EU) 2019/882, read August 29, 2026.

Two boundaries ride with that table. The exemption in Article 4(5) is for microenterprises providing services — an e-commerce service is one, and microenterprises dealing in products do not get the same treatment. And the directive works through national law: Member States were required to adopt and publish implementing measures by 28 June 2022, so a seller sitting near the line reads the implementing law of the Member State concerned, which is where questions like how the turnover or the balance sheet total is counted are settled.

What the Directive Asks of an Online Store

Read as a group, those seven are less alarming than a first pass suggests: four of them are about information reaching people, one is about the products used to provide the service, and two are about the parts of a purchase that involve identifying and paying. The one that surprises merchants is Section IV(g)(i), which asks for accessibility information about the products being sold where the responsible operator provides it — that is a catalogue question, not a code question.

The wording about how information must reach people is not unique to this directive, and if you have already worked through AI disclosure duties you have met it before. The EU AI Act uses the same construction for its Article 50 notices, and our guide to how that disclosure has to appear walks through what “conform to applicable accessibility requirements” asks of the surface a shopper actually sees.

Article 2(4) then carves five things back out of scope, and one of them is directly relevant to a store that runs embedded widgets.

Article 2(4) of Directive (EU) 2019/882, read August 29, 2026.

The third-party line is the one to keep. Content that is neither funded by, developed by, nor under the control of the economic operator concerned sits outside — which makes it worth knowing exactly which embedded widgets on your storefront your business pays for and configures, and which simply arrived with somebody else's script. That inventory is step eight of the pass further down this page.

What the Directive Says About Penalties

This matters because the round numbers circulating in blog posts — figures in the hundreds of thousands — are presented as if the directive contained them. It does not. Article 30 does what framework directives normally do: it sets the quality of the penalty and leaves the amount to each Member State.

That is the same mechanism that decides the microenterprise threshold a section earlier. Article 31(1) required Member States to adopt and publish the laws, regulations and administrative provisions needed to comply by 28 June 2022, and Article 30 hands those same States the penalty rules to write. There is therefore no single European figure to quote at a merchant, and the document that carries one is the implementing law of whichever Member State is asking.

Do Accessibility Widgets Make a Shopify Store Compliant?

This is the most-searched question on the topic, and it deserves an answer built on documents rather than opinion.

Widgets in this class advertise themselves clearly enough. The listing for accessiBe's accessWidget stated, as read on August 29, 2026, that AI scans your store daily and applies accessibility adjustments without altering your design or layout, and that it supports ADA, EAA, AODA and WCAG alignment. Two other listings in the same category made comparable claims about ADA and WCAG the same day.

What the FTC Order Against accessiBe Says

The FTC states the claim it acted on directly: accessiBe claimed the plug-in accessWidget can make any website compliant with the Web Content Accessibility Guidelines. The order prohibits accessiBe from making misleading claims and requires the company to pay $1 million.

Three boundaries belong with that figure, and dropping any of them turns a precise fact into a slogan. The order is about accessiBe and the claims accessiBe made, not about overlays as a technology. The claim it describes was that the product could make any website compliant. And the bar it sets is conditional: the order prevents representing that its automated products can make any website WCAG-compliant or ensure continued compliance over time, unless it has the evidence to support such claims.

What Official Guidance Says About Checkers and Overlays

That is a more useful position than either enthusiasm or dismissal, and it applies to every automated check on this page, including the Lighthouse score Shopify itself sets for submitted themes. A number is a starting point for looking, not a substitute for having looked.

One correction is worth making here, because it circulates widely in the other direction. No page on w3.org or w3.org/WAI we read on August 29, 2026 carries an official W3C or WAI position statement about accessibility overlays. The document sometimes cited as one is a Community Group draft report, which by the W3C's own process is neither a Recommendation nor a statement of the organisation. Citing it as the W3C's verdict overstates it in exactly the way the widget listings overstate theirs.

Where Does Your Accessibility Work Actually Start?

The table at the top answers by profile — who you are. This answers by combination: where your customers are, how big you are, what your storefront is built on, what has already been done to it, and who is asking. Those five cross in ways a single row cannot express, and they change what you do first rather than whether you are covered.

Five questions, and none of the routes is a failing grade. Nothing here is legal advice, and no result tells you that you are compliant — each one names the documents that describe your situation and the first move that follows from them.

What to Check in Your Own Store, and in What Order

Everything in this section is a pass over what you already have. It is not a guide to editing a theme, and none of it asks you to open a file — the value is knowing which questions to ask, in an order where the answers build on each other.

The Bar Shopify Applies to Theme Store Themes

This is the closest thing to an official checklist that exists anywhere in this topic, and its scope is exact: it applies to themes submitted to the Shopify Theme Store. That makes it a floor for a stock theme and a shopping list for a custom one — and it says nothing at all about code an app injects into your pages after install.

Requirements read on Shopify's Theme Store requirements on August 29, 2026. They govern themes submitted to the Theme Store; a Lighthouse score is an automated check, and the ADA guidance above applies to reading it.

Shopify writes the same caution twice — once to merchants about their online store, quoted at the top of this page, and once to whoever builds the theme.

Where Your Checks Stop

This boundary is worth stating because it changes what a thorough pass looks like. Working through the checkout as if it were yours produces findings you cannot act on and cannot report; the surface has its own published report, and that report is what a buyer's questionnaire should be pointed at.

The admin sits on the same side for a different reason. It is where you and your staff work, not where your customers shop, and Shopify's report for it names the areas it covers. Neither surface is excluded from your interest — they are simply described somewhere other than in a pass you run yourself.

Your Pass, in Order

Two notes on order and weight. Steps one and two apply to everybody and take an afternoon between them, and skipping them makes every later step ambiguous. Step three earns its position ahead of step five because the keyboard pass needs no tools and finds the problems that stop a purchase outright, while contrast findings are real but rarely blocking.

Step nine is the only one that costs money, which is also where the choice between doing it in the theme editor and handing it to a developer is actually made.

Do You Need an Accessibility Statement?

The demand for this is real — merchants search for it directly — and the honest framing is that it is a surface for information rather than a certificate. Annex I Section III(b) asks for information about the functioning of the service, and Section IV(g)(i) asks for accessibility information about the products and services being sold where the responsible operator provides it. Both of those are things a statement can carry.

Shopify's own statement is the most convenient template to study, because you can read it in a minute and it is written by a company with the same problem you have. What it contains is worth listing:

• The standard it works to — WCAG 2.2 as a guiding principle, with continual testing at Level AA.
• What is covered and what is not — conformance reports per product, each naming its own scope and the standard it was tested against.
• Work in progress rather than a finished claim — the page describes continuously working to remove access barriers, including for e-commerce services covered under the European Accessibility Act.
• Where the boundary sits — the sentence about merchants controlling their theme codes.
• A route for a person who is stuck — a contact path, which is the part a shopper actually uses.

A statement written that way is useful in both directions. It answers the buyer's questionnaire, and it gives a customer who cannot complete something a way to tell you — which, as the quiz above treats it, is the single most valuable input you can get about your own storefront.

Who Does the Work, and Where the Budget Question Goes

Sort your findings before you price anything, because the two halves have completely different costs. Colour choices, heading hierarchy in the content you write, alternative text on images and the wording on buttons are all things a merchant changes in the theme editor and the admin. Nothing about them requires a developer, and nothing about them requires a plan change.

The other half is code. Focus order that matches the DOM, valid HTML, inputs bound to their labels, and the behaviour of a custom section somebody built two years ago are all theme-code work, which Shopify names as the merchant's responsibility and which most merchants hire out.

What that hour costs, and how a freelance rate compares with an agency one, is the subject of our breakdown of freelancer and agency rates. This page carries no price for accessibility work itself: the sources behind it are standards documents and conformance reports rather than rate cards.

If you are not sure which kind of help you are shopping for at all, the Shopify development guide routes between the specialist types in about a minute, which is faster than working it out from a quote.

The Bottom Line

Almost every confusing sentence written about accessibility on Shopify comes from one substitution: a statement about the platform standing in for a statement about a storefront. Separate the two and the topic becomes unusually tractable — a published list of checks, one European exemption that either describes you or does not, and an American duty with no deadline and no official pass mark.

Frequently Asked Questions