UX / Accessibility
Ecommerce Website Accessibility: A Practical Guide
// a store people can't use is a store they can't buy from
By Fracto Solutions
October 24, 2026
The short answer
Ecommerce accessibility means your store works for people using screen readers, keyboards, zoom, or captions. Target WCAG 2.2 Level AA, fix the handful of failures behind most errors (low contrast, missing alt text, unlabeled form fields), and test the checkout path by keyboard. It widens who can buy and lowers legal risk. It is practical work, not a compliance badge.
95.9%
56.1
~70%
Why does accessibility matter for an online store?
Because a shopper who cannot perceive, navigate, or complete your checkout cannot buy, no matter how good your products are. Accessibility widens the audience who can actually use your store, and most of it overlaps with plain good usability.
Disability is common enough to be part of your market rather than an edge case. The World Health Organization estimates that 1.3 billion people, about 16% of the world’s population, experience significant disability, and the CDC puts more than 1 in 4 US adults as having some type of disability. Handle both carefully, because neither measures “people whose disability affects how they use a website”. The CDC’s web-relevant categories are narrower and they overlap, so they cannot be summed: cognition 13.9%, mobility 12.2%, hearing 6.2%, vision 5.5%. What you can say without stretching anything is that a real share of your traffic arrives with a screen reader, a keyboard, zoom, or captions, and leaves if the store does not work that way.
The scale of the problem is measured, and it is not improving. WebAIM’s February 2026 analysis of a million home pages found 95.9% had detected WCAG 2 Level A/AA failures, averaging 56.1 errors per page. Both numbers moved the wrong way from the year before (94.8% and 51), so the web is not quietly fixing this on its own. WebAIM is equally clear about the limits of the method: automated tools cannot find every conformance failure, and in its own words, “absence of detected errors does not indicate that a page is accessible or conformant”. A clean scan is a starting point, not a verdict.
What standard should I aim for?
The Web Content Accessibility Guidelines (WCAG), the W3C standard built on four principles: content should be perceivable, operable, understandable, and robust. It has three conformance levels, A, AA, and AAA. AA is the level the regulations that do name one have adopted, and the level ecommerce teams generally target.
WCAG 2.2 has been the current W3C Recommendation since 5 October 2023, revised 12 December 2024. WCAG 3.0 exists only as a working draft the W3C says should not be cited as anything but work in progress. You do not need to memorize any of it: target AA and clear the common failures.
One detail worth keeping straight, because it is where most write-ups slip: the laws lag the standard. The US Department of Justice’s Title II rule adopts WCAG 2.1 Level AA, and EN 301 549, the European harmonized standard, maps to Level A and AA as well. Shopify’s own accessibility statement names 2.2 as its guiding principle while testing its Dawn theme to 2.1 A/AA. So “target AA” is the stable part of the instruction, and the version number depends on which authority you are answering to.
What are the most common accessibility failures?
A handful of issues cause most of the problem. WebAIM’s 2026 report found six categories account for 96% of all errors it detected, led by low-contrast text, missing image alt text, and unlabeled form inputs, exactly the things that block screen-reader and low-vision shoppers.
The encouraging part is how concentrated the failures are: fix these six and you clear most of what a scan will find.
Failure
Home pages affected
What it blocks
Low-contrast text
83.9%
Readability for low-vision shoppers
Missing image alt text
53.1%
Screen readers describing products
Missing form input labels
51.0%
Completing checkout and forms
Empty links
46.3%
Knowing where a link goes
Empty buttons
30.6%
Operating key actions, add to cart
Missing document language
13.5%
Screen readers pronouncing the page correctly
WebAIM Million, February 2026 data. These six categories account for 96% of all errors detected. “Detected” is doing real work in that sentence: it is what one automated engine found, not the full set of accessibility problems on those pages.
One barrier belongs on the list even though automated scans will not flag it. In WebAIM’s Screen Reader User Survey #10, respondents ranked CAPTCHA the most problematic item they encounter, by a notable margin. On a store it usually sits on login and checkout, the two pages you can least afford to break.
Is my store legally required to be accessible?
Often, yes, but it depends on where you sell, and this is general information rather than legal advice. In the EU, ecommerce is named explicitly in the European Accessibility Act. In the US there is no technical standard for private businesses, and the risk comes from litigation rather than regulation.
The EU. The European Accessibility Act, Directive (EU) 2019/882, has applied since 28 June 2025, and ecommerce services are explicitly listed in its scope. Its technical requirements run through EN 301 549, which maps to WCAG Level A and AA. There is a real exemption that a lot of small merchants sit inside: a service provider that is a microenterprise, meaning fewer than 10 people employed and annual turnover or balance sheet total not above EUR 2 million, is not bound by it. Check your own numbers against the Directive rather than assuming either way.
The US. The DOJ rule people cite, published 24 April 2024 and adopting WCAG 2.1 Level AA, is a Title II rule: it covers state and local government, not private businesses. Its compliance dates were also pushed back a year by an interim final rule on 20 April 2026, to 26 April 2027 and 26 April 2028. Your store is Title III, and for Title III the DOJ has deliberately not set a technical standard. Its guidance says businesses “have flexibility in how they comply with the ADA’s general requirements of nondiscrimination and effective communication. But they must comply with the ADA’s requirements.” Courts also still disagree on whether an online-only business with no physical premises falls under Title III at all.
What actually creates risk. Private litigation, and it is concentrated on stores. UsableNet counted more than 5,000 digital accessibility lawsuits filed in 2025 across federal and state courts, with nearly 70% of them against ecommerce. Read that as a vendor’s count, cast wider than federal-only trackers such as Seyfarth. Even discounted, ecommerce is the biggest single target.
What conformance buys you, and what it does not. Targeting WCAG 2.2 AA is the most defensible position available and the standard settlements point at. It is not a safe harbor. Conformance is self-declared, nobody certifies it, it is scoped to pages rather than whole flows, and WCAG itself notes that “even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability”. State statutes such as California’s Unruh Act also allow damages the ADA does not. Conformance reduces exposure; it does not remove it. The Shopify-specific version of this question is in is my Shopify store ADA compliant.
How do I make my store more accessible?
Start with the high-frequency failures: fix color contrast, add meaningful alt text to product images, label every form field, and make the whole store keyboard-operable. Then test with real assistive tech. Most of the gain comes from a short, concrete list.
You do not need a rebuild to make progress. Run an automated checker for contrast, alt-text, and labeling issues, fix them, then do a manual pass: navigate the store with only a keyboard, and try checkout with a screen reader. The fast, high-impact subset is in accessibility quick wins.
Be careful with one-click accessibility overlays, and this is no longer a matter of opinion. On 3 January 2025 the FTC ordered accessiBe to pay USD 1 million, alleging that its accessWidget “did not make all user websites WCAG-compliant and these claims were therefore false, misleading, or unsubstantiated”, and barring the company from repeating those claims without evidence. The DOJ’s own guidance warns that a clean automated report “does not necessarily mean everything is accessible”. The Overlay Fact Sheet, signed by more than a thousand accessibility practitioners, states that no overlay product on the market can make a site fully compliant with any existing standard or eliminate legal risk. And UsableNet’s 2025 data shows filings against sites that already had a widget installed continuing at the same rate all year. Fixing the underlying code is what counts.
Does accessibility help conversion and SEO?
Most accessibility fixes are plain usability fixes, so they pull in the same direction as conversion. Be careful with the numbers, though: no published study isolates a conversion lift from accessibility remediation on ecommerce, and the figures that circulate do not survive checking.
We would rather say this plainly than repeat the usual claims. The famous Tesco “GBP 13 million” figure is a misreading: the W3C case study says a wider audience was spending GBP 13 million a year on that site, which is total spend, not revenue created by accessibility. The Legal & General numbers come from a full site redesign in 2005, so accessibility cannot be separated from the rebuild. The W3C’s own business case page concedes that direct ROI “is too difficult to measure” and declines to publish a conversion figure.
What stands up is mechanical rather than statistical. A customer who cannot read your price, cannot tell which field wants the postcode, or cannot reach the pay button with a keyboard does not convert, and that needs no study. The nearest supporting data is the UK Click-Away Pound survey, which found 69% of participants with access needs will simply leave a problematic website; it is a self-selecting 2019 survey with no disclosed sample size, so treat it as directional. Our position is that these fixes are worth doing on usability grounds, and that the conversion effect on your store is something you measure rather than forecast from someone else’s number.
On SEO, one correction to a claim you will see everywhere: accessibility is not a Google ranking factor, and Google has said so directly. What is true is narrower and still useful. Google’s documentation says it uses alt text along with computer vision and page content to understand images, and recommends writing it to W3C guidelines, so alt text genuinely helps in Google Images. Descriptive link text helps Google understand what a page covers. Neither of those is a ranking boost for fixing contrast. The broader structural work still belongs alongside ecommerce SEO, and it is the same find-the-friction discipline behind our growth-strategy pillar.
How do I keep my store accessible over time?
Accessibility is not a one-time project; it drifts as you add products, apps, and theme changes. Bake a few checks into the normal workflow, alt text when you upload images, contrast and labels when you design, a keyboard pass before you ship, and you keep the gains instead of re-earning them.
Most stores that fix accessibility once slide back, because every new product image without alt text, every app that injects an inaccessible widget, and every theme tweak is a chance to reintroduce the same failures. Three of WebAIM’s top six error types, low contrast, missing alt text, and empty links and buttons, are overwhelmingly things a merchant adds rather than things a theme ships with. The durable fix is process, not a single audit: make alt text part of adding a product, check contrast and labels when you build a section, and run a quick automated scan plus a keyboard test before major releases.
Treat the checkout path as the one you never let regress, since an inaccessible checkout blocks the sale outright for everyone affected.
We treat accessibility as usability and risk reduction, fixed at the source.
We audit your store against the common WCAG failures, fix contrast, alt text, labels, and keyboard operability in the code rather than papering over them with an overlay, and test with real assistive tech, so your store works for more people and carries less legal risk.
It’s the same measurement-first discipline behind our conversion optimization and web development work, where we rebuild the buying path and measure the result .
// we would rather show up in your reporting than in your inbox
Frequently asked questions
What accessibility standard should an ecommerce store target?
WCAG 2.2 Level AA. WCAG is the W3C standard that accessibility laws point to, and AA is the level the regulations that name one have adopted. Note the version drift: the US DOJ Title II rule adopts WCAG 2.1 AA, and the European harmonized standard EN 301 549 maps to Level A and AA.
What are the most common accessibility problems?
Low-contrast text (83.9% of home pages), missing image alt text (53.1%), missing form input labels (51.0%), empty links (46.3%), empty buttons (30.6%), and missing document language (13.5%). WebAIM’s February 2026 report found these six categories account for 96% of all errors it detected, so a focused fix list goes a long way.
Is my online store legally required to be accessible?
It depends on where you sell, and this is general information rather than legal advice. In the EU, the European Accessibility Act has applied since 28 June 2025 and names ecommerce explicitly, with an exemption for microenterprises under 10 staff and EUR 2 million. In the US there is no technical standard for private businesses; the risk comes from litigation, and nearly 70% of 2025 digital accessibility lawsuits targeted ecommerce.
Do accessibility overlay widgets make my store compliant?
No. In January 2025 the FTC ordered accessiBe to pay USD 1 million over claims that its widget made websites WCAG-compliant, and lawsuits against sites that already had a widget installed continued through 2025. Fixing the underlying problems, contrast, alt text, labels, keyboard support, is what actually works.
Does accessibility help conversion?
It usually helps, but no published study isolates the effect on ecommerce, and the widely quoted ROI figures do not survive checking. The honest argument is mechanical: a shopper who cannot read the price or reach the pay button cannot buy. Measure the effect on your own store rather than forecasting it from someone else’s number.
Sources
Accessibility failure rates: WebAIM Million 2026, an automated accessibility analysis of the home pages of the top one million websites, conducted February 2026. 95.9% of home pages had detected WCAG 2 Level A/AA failures (94.8% in 2025, 95.9% in 2024); average 56.1 detected errors per page (51 in 2025). Most common failures: low-contrast text 83.9%, missing image alt text 53.1%, missing form input labels 51.0%, empty links 46.3%, empty buttons 30.6%, missing document language 13.5%; these six categories account for 96% of all errors detected. WebAIM states that not all conformance failures can be automatically detected and that absence of detected errors does not indicate a page is accessible. https://webaim.org/projects/million/
Screen reader user priorities: WebAIM Screen Reader User Survey #10, December 2023 to January 2024, 1,539 respondents. CAPTCHA was ranked the most problematic item encountered, by a notable margin, ahead of unexpected interactive behavior and unclear links or buttons. This survey does not measure purchase abandonment, and we do not cite it for that. https://webaim.org/projects/screenreadersurvey10/
The standard: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation 5 October 2023, revised 12 December 2024. Four principles (perceivable, operable, understandable, robust), three conformance levels (A, AA, AAA). WCAG 3.0 remains a working draft. https://www.w3.org/TR/WCAG22/
Disability prevalence: World Health Organization, Disability fact sheet, updated 7 March 2023: an estimated 1.3 billion people, 16% of the world population, experience significant disability. US Centers for Disease Control and Prevention, Disability Impacts All of Us: more than 1 in 4 US adults have some type of disability (cognition 13.9%, mobility 12.2%, hearing 6.2%, vision 5.5%). Neither figure measures disability that affects web use specifically, and the CDC categories overlap and cannot be summed. https://www.who.int/news-room/fact-sheets/detail/disability-and-health
EU law: European Accessibility Act, Directive (EU) 2019/882, applicable from 28 June 2025. Ecommerce services are explicitly in scope; technical requirements flow through EN 301 549, which maps to WCAG Level A and AA. Microenterprise service providers, fewer than 10 employees and turnover or balance sheet total not above EUR 2 million, are exempt. https://eur-lex.europa.eu/eli/dir/2019/882/oj/eng
US law: DOJ Title II web rule published 24 April 2024, adopting WCAG 2.1 Level AA, covering state and local government and not private businesses; compliance dates extended one year by interim final rule published 20 April 2026, to 26 April 2027 and 26 April 2028. For Title III private businesses the DOJ has not adopted a technical standard and states that businesses have flexibility in how they comply. https://www.ada.gov/resources/web-guidance/
Litigation volume: UsableNet 2025 year-end digital accessibility lawsuit report: more than 5,000 federal and state filings in 2025, with nearly 70% against ecommerce, and filings against sites already running an accessibility widget continuing at a steady rate through the year. UsableNet sells accessibility services, counts state as well as federal filings, and its window closes mid-December, so the figure is a vendor count on a wide net. Seyfarth, counting federal ADA Title III filings only, reports a smaller website-specific subset. https://blog.usablenet.com/ada-web-lawsuit-trends-2026
Overlays: Federal Trade Commission order against accessiBe Inc. and accessiBe Ltd., 3 January 2025, USD 1 million. The FTC alleged accessWidget “did not make all user websites WCAG-compliant and these claims were therefore false, misleading, or unsubstantiated”, and the order bars representing that its automated products can make a website WCAG-compliant without supporting evidence. See also the Overlay Fact Sheet, signed by more than a thousand practitioners, which states that no overlay product can make a site fully compliant with any existing standard or eliminate legal risk. https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-order-requires-online-marketer-pay-1-million-deceptive-claims-its-ai-product-could-make-websites
Abandonment: Click-Away Pound 2019, a UK survey of online shoppers with access needs: 69% say they will simply leave a problematic website, down from 71% in 2016. The report states that participants were entirely self-selecting and does not disclose a sample size, and the GBP 17.1 billion headline is an extrapolation rather than measured lost revenue. We cite the direction, not the magnitude. https://clickawaypound.com/downloads/cap19final0502.pdf
SEO: Google has stated that accessibility is not a direct ranking factor (John Mueller, Search Central office-hours, March 2022). Google’s own image documentation says it uses alt text together with computer vision and page content to understand images and recommends writing alt text to W3C guidelines. https://developers.google.com/search/docs/appearance/google-images
Conversion claims we did not use: the widely quoted Tesco “GBP 13 million” figure describes total spend by that site’s audience, not revenue created by accessibility, and refers to a separate accessible site which the W3C now flags as not current best practice. The Legal & General figures come from a 2005 full-site redesign in which accessibility cannot be isolated. The W3C’s own business case page concedes that direct ROI is too difficult to measure. We found no published study isolating a conversion lift from accessibility remediation on ecommerce. https://www.w3.org/WAI/business-case/
General information, not legal advice. Accessibility law varies by country and situation, and WCAG conformance is self-declared rather than certified. Confirm your obligations with a qualified professional.