Ecommerce Website Accessibility in 2026

By Site Brace Research · Published June 9, 2026

These are big, well-resourced national retailers, drawn from the NRF Top 100 - the kind of stores with design teams and a budget for this. The most heavily defended of them blocked our scanner and are not even in the count. Three out of four of the ones we could read still ship a measurable accessibility barrier on the first page a shopper sees.

Key findings

• 76% of the largest retailers' home pages had at least one automated WCAG 2.1 AA violation (25 of 33). Because automated tools cover only 30 to 40 percent of WCAG criteria, that figure is a floor, not a ceiling.
• Low color contrast and missing image alt text tied as the most common failure, each on 8 of 33 sites (24%). For a store built on product photography, an image with no alt text is a product a screen-reader shopper cannot perceive.
• Links with no accessible name followed, on 6 of 33 sites (18%) - usually the icon-only cart, search, and account controls a shopper needs to actually buy something.
• Ecommerce is the most-targeted sector for ADA Title III website lawsuits. By UsableNet's count, online stores drew roughly 70 percent of the more than 5,000 digital accessibility suits filed in 2025; among the top 500 ecommerce retailers, 35.8 percent were hit with at least one.
• This sample is large retailers minus the most defended. A typical small Shopify or WooCommerce store, with less budget for this work, is unlikely to do better. We did not scan small stores for this report, so treat that as a reasoned expectation, not a measurement.

How accessible are ecommerce home pages?

Of the 33 retailer home pages we scanned cleanly, 25 had at least one automated WCAG 2.1 AA violation - 76%. The median site had one violation; the average was 1.6.

Read that number the right way. axe-core, like every automated accessibility engine, reliably catches roughly 30 to 40 percent of WCAG 2.1 AA success criteria. The rest - whether focus order makes sense, whether alt text actually describes the product, whether a custom add-to-cart widget works with a screen reader - need a person. So 76% is the share failing the part of WCAG a machine can check on one page. The share failing the full standard, across a whole store with its product pages, cart, and checkout, is higher. We test the automated slice on purpose and say so wherever we report it.

For wider context, WebAIM's 2026 analysis of the top one million home pages found detectable WCAG failures on about 96% of them, with low-contrast text the single most common error, on 84% of pages. That study uses a different engine and a broader rule set, so its percentages are not directly comparable to ours. Our sample of large retailers comes in below the web at large, which fits: better-resourced sites do somewhat better. But 76% is still most of them, and the item at the top of both lists is the same. Low contrast is the most common accessibility defect on the web, and online stores are no exception.

The most common failures on ecommerce home pages

These are the axe-core rules that failed on the most retailer sites. Each count is the number of distinct sites where the rule failed at least once, out of 33. With a sample this size, read the top of the list as the reliable signal and the long tail as directional.

Below those, a few sites had buttons with no accessible name or a missing page title. None of these are exotic. They are the routine, fixable defects that accumulate when accessibility is not part of the build.

For a store the stakes are direct, because each of these failures sits on the path to a purchase. A product image with no alt text is, to a screen-reader shopper, a blank space where the thing they came to buy should be. An icon-only cart or search link with no name gives no clue what it does. A quick-add widget a screen reader cannot operate stops the sale outright. For the store, each of those defects is also a place where a sale can quietly fail.

What the law and the lawsuits say

Ecommerce is unusual in how much accessibility litigation it draws. This section describes what the law says and what the filing data shows. It is not legal advice, and whether any particular store is covered or liable is a question for an attorney.

The ADA reaches online stores, but without a rulebook written for them. Title III of the Americans with Disabilities Act covers "places of public accommodation," and the Justice Department's position is that this includes the goods and services a business offers through its website. The landmark case is Robles v. Domino's Pizza: in 2019 the Ninth Circuit held that the ADA applied to Domino's website and app because they connect to its physical restaurants, and the Supreme Court declined to hear the appeal, leaving that ruling in place. What does not exist is a federal regulation naming a specific technical standard for private websites. The DOJ shelved its Title III web rulemaking in 2017 and, in its 2022 guidance, said businesses "can currently choose how they will ensure" their sites are accessible, pointing to WCAG as helpful guidance rather than a codified rule. In practice, WCAG 2.1 Level AA is the standard plaintiffs cite and settlements adopt - the same standard a Site Brace audit measures a site's conformance against.

The filings concentrate on retail. By UsableNet's 2025 count, more than 5,000 digital accessibility lawsuits were filed across federal and state courts in 2025, and ecommerce was the most-targeted sector by far, at roughly 70 percent of them. Among the top 500 online retailers, more than a third - 35.8 percent - drew at least one suit that year. Counting federal court alone, the law firm Seyfarth Shaw recorded 3,117 website-accessibility suits in 2025, up 27 percent from the year before. The two totals differ because they measure different things - UsableNet includes the heavy state-court docket, New York most of all, while Seyfarth counts federal filings - but both point the same way: the volume is large, it rose in 2025, and online stores absorb most of it. The cases cluster in New York, Florida, and California, the last under a state civil-rights law that carries statutory damages per violation.

Overlays are a liability here, not a fix. A store told it has a lawsuit problem is often sold an accessibility "overlay" widget that promises compliance in one line of JavaScript. It does not work, and it has become its own legal exposure. In 2025 the Federal Trade Commission fined the overlay vendor accessiBe 1 million dollars over its claim that the product could automatically make any website conform to WCAG, a representation the FTC found false. Plaintiffs increasingly name sites that run these widgets. The honest path is the unglamorous one: find the real barriers and fix them in the code. That is what we explain in detail, and it is why a Site Brace report tells you what is actually wrong instead of selling you a number.

The honest read is this. The legal pressure on ecommerce is real and concentrated, but a scan result is not a verdict. We report conformance, a measurable property of a page. Whether a store meets its legal obligation is a determination only an attorney can make.

What this means for smaller stores

The 33 sites here are among the largest retailers in the country. A store running an off-the-shelf Shopify or WooCommerce theme has fewer resources for accessibility than a national chain, not more. We did not scan small stores for this report, so this is a reasoned expectation rather than a finding: if the biggest retailers fail the automated slice 76% of the time, a smaller store is unlikely to come out ahead, and the litigation data shows plaintiffs do not pursue only the giants. If you run an online store of any size, you can run a free automated check on your own home page in about a minute, see what a full manual and automated audit covers, or read how we approach Shopify stores in particular.

What this data is not

• Not a whole-store audit. We scan one page, the home page. Product detail pages, search results, the cart, checkout, and account flows are not tested, and those are where the barriers that block a sale - and the ones plaintiffs cite most - tend to live. The real picture per store is very likely worse.
• Not the full WCAG standard. Automated testing covers 30 to 40 percent of success criteria. We report the automated slice and say so.
• Not a legal verdict. Conformance is a measurable property of a page against WCAG. Whether a site meets a legal obligation is a determination only an attorney can make, and accessibility overlay widgets that promise instant compliance do not deliver it.
• Not a random or complete sample. This is 33 of the largest US retailers that returned a clean scan, out of 50 drawn from the NRF Top 100 list; the most heavily bot-defended sites blocked automated access and are excluded. The sample is small and skews toward big, well-resourced retailers. We label the size, lean on the top of the list rather than the thin tail, and never count a site we could not scan as inaccessible.

How we measured this

We took the largest US retailers from the National Retail Federation's Top 100 list and scanned each home page once with axe-core against WCAG 2.1 Level AA. The retailers were drawn on 2026-05-31 and scanned over the following day, as part of our broader State of Web Accessibility 2026 study. 33 of the 50 we drew returned a clean automated scan and are analyzed here; the rest blocked automated access or returned an error and are excluded. We never count a site we could not scan as inaccessible.

This is the same axe-core engine and the same home-page method as the flagship study, so the ecommerce figures here line up with the ecommerce row reported there. For the full standard we hold our data to, and the sources behind each industry sample, see how Site Brace Research compiles accessibility data.

Citing this report

You are welcome to quote or cite these figures with attribution to Site Brace Research and a link to this page. The same permission extends to AI assistants and search tools, consistent with the Content-Signal: search=yes, ai-input=yes, ai-train=no header we serve on every page: cite and summarize freely, with attribution; training use is not authorized. Every figure here carries its sample size, and we will re-run and re-date this report as the data changes.