Accessible retail: storefronts, stores and the rules that now apply

For most of the last two decades, accessibility sat in the same retail budget line as sustainability reports and community sponsorships: worthwhile, visible and easy to defer. That arrangement has ended. Retail accessibility compliance is now a legal exposure in the United States, a market access condition in the European Union and a line item that enterprise and wholesale buyers check before they sign a supply agreement.

This guide explains which rules apply to online storefronts and physical stores, who is covered, what an audit actually inspects, which fixes remove the most friction for the least effort, and how retailers typically budget a remediation programme across a year. It is written as general information for operators, product owners and finance teams, not as legal advice, and every rule cited here is attributed to the body that publishes it.

Why accessibility became a retail compliance topic

Three forces converged. The first is litigation volume in the United States: industry trackers such as UsableNet and the law firm Seyfarth Shaw have for years counted thousands of ADA-related website and app lawsuits annually, and e-commerce and retail consistently rank as the most frequently targeted sector in those reports. Many of these cases settle quickly, which keeps the per-case cost moderate but the aggregate exposure high for any retailer with a sizable digital footprint.

The second force is regulation outside the US. The European Accessibility Act, formally Directive (EU) 2019/882, became applicable across the EU on June 28, 2025, according to the European Commission’s accessibility pages. Unlike the ADA, it names e-commerce services explicitly, which removed the ambiguity that US retailers have lived with for years.

The third force is commercial. The World Health Organization estimates that about 1.3 billion people, roughly one in six worldwide, live with a significant disability, and the US Centers for Disease Control and Prevention reports that up to one in four American adults has some type of disability. Add older shoppers with declining vision or dexterity, and the population that benefits from accessible design is not a niche; it is a meaningful share of every retailer’s customer file.

From goodwill project to purchasing rule

The shift is visible in how the topic is staffed. Five years ago, accessibility was usually owned by a single front-end developer or a brand team. Today it increasingly sits with legal, procurement and the digital product organization together, because the questions now arrive from three directions at once: a demand letter, a regulator’s inquiry and a buyer’s vendor questionnaire.

For retailers already wrestling with the broader pressures described in our overview of the state of retail across department stores, grocers and experiences, accessibility can look like one more cost. The more useful framing is that it is a quality discipline: the same work that reduces legal exposure also tends to reduce checkout abandonment and support contacts.

The conversion argument, stated carefully

Claims that accessibility “doubles conversion” should be treated with skepticism; most published figures come from vendors with a product to sell. What is well supported is narrower. Clear form labels, visible focus states, readable contrast and descriptive error messages reduce friction for every shopper, and those are exactly the elements accessibility audits flag most often.

A practical test: if a checkout cannot be completed using only a keyboard, it is very likely also fragile on mobile screen readers, voice control and some password managers. Fixing the accessibility defect usually fixes several adjacent usability defects at the same time.

The rules that apply online and the ones that apply in store

Retailers operate across two physical realities, the website or app and the store, and the law treats them differently. The table below summarizes the main frameworks a retailer selling into North America, the UK and the EU is likely to meet. It is a simplified orientation, not a complete legal map, and the specific obligations must be verified against the official source for each jurisdiction.

Framework	Where	Covers online?	Covers stores?	Technical benchmark	How it is enforced
ADA Title III	United States	Contested by court and circuit; DOJ guidance says yes	Yes, as places of public accommodation	WCAG 2.x AA in practice (online); 2010 ADA Standards (physical)	Private lawsuits, DOJ actions
State laws (e.g. California Unruh Act)	Individual US states	Yes, as interpreted by state courts	Yes	Usually mirrors ADA	Private lawsuits, statutory damages in some states
European Accessibility Act	EU member states	Yes, e-commerce services named explicitly	Partly: self-service terminals and payment terminals	EN 301 549 harmonized standard (incorporates WCAG 2.1 AA)	National market surveillance authorities
Equality Act 2010	United Kingdom (Great Britain)	Yes, under the duty to make reasonable adjustments	Yes	No statutory technical standard; WCAG commonly referenced	Individual claims; Equality and Human Rights Commission
AODA	Ontario, Canada	Yes, for organizations of covered size	Yes, via customer service and built environment standards	WCAG 2.0 AA (web standard)	Provincial compliance reporting and enforcement

United States: the ADA and its unsettled online reach

Title III of the ADA prohibits discrimination on the basis of disability in places of public accommodation, which include retail stores. Whether a website or app counts as a place of public accommodation has been litigated for years. Some federal appellate courts have required a connection, or “nexus”, between the website and a physical location, while some district courts have applied the law to online-only businesses; the result is that exposure depends partly on where a retailer is sued.

The US Department of Justice has not issued a final technical regulation for private-sector websites under Title III. Its published web accessibility guidance states the department’s position that the ADA applies to the web offerings of businesses open to the public, and points to existing standards such as WCAG as helpful guidance. In practice, plaintiffs, settlement agreements and courts have converged on WCAG 2.0 or 2.1 at level AA as the working benchmark.

United States: physical stores and the 2010 Standards

For physical premises, the picture is far more concrete. The 2010 ADA Standards for Accessible Design, published by the DOJ, contain measurable requirements. According to those Standards, accessible routes generally need a minimum clear width of 36 inches, sales and service counters need an accessible portion no higher than 36 inches above the floor, and where dressing or fitting rooms are provided, at least 5 percent of them (and no fewer than one of each type) must be accessible.

Existing buildings are also subject to the obligation to remove architectural barriers where that is “readily achievable”, a flexible standard that depends on the size and resources of the business. Retailers planning a refit or a new format should treat the 2010 Standards as the design brief for accessible store design in retail and verify each requirement in the current text on ada.gov or with an accessibility consultant, since exceptions and scoping rules are detailed.

European Union: the EAA’s product and service lists

The EAA covers a defined list of products and services. For retailers, the most relevant are e-commerce services, consumer banking services, e-books and dedicated reading software, and a set of hardware products including computers, smartphones, payment terminals and self-service terminals such as ticketing and check-in machines. According to the European Commission, the directive applies to economic operators placing these products or services on the EU market, which includes businesses established outside the EU that sell to EU consumers.

Retailers selling into Europe can see how this fits alongside the platform and integration choices in our guide to choosing the right e-commerce platform for a store, since many EAA defects originate in themes, checkout plug-ins and third-party widgets rather than in a retailer’s own code.

The UK and Canada

In Great Britain, the Equality Act 2010 places an anticipatory duty on service providers to make reasonable adjustments so that disabled people are not placed at a substantial disadvantage. The Act does not prescribe a technical standard for websites, but WCAG is the reference most commonly cited in guidance and disputes.

In Canada, the Accessibility for Ontarians with Disabilities Act (AODA) has required covered organizations, under its Integrated Accessibility Standards, to make public websites conform to WCAG 2.0 AA, with the timeline set by the Ontario government according to organization size. The federal Accessible Canada Act applies mainly to federally regulated sectors such as banking and transportation, so most retailers meet it indirectly through payment and delivery partners.

Who is covered: sellers, marketplaces and micro-enterprises

Coverage is where retailers most often misjudge their exposure, in both directions. Small merchants sometimes assume they are too small to matter, while large retailers sometimes assume a platform vendor carries the obligation for them. Neither assumption holds up consistently.

The EAA micro-enterprise exemption

The EAA contains an exemption for micro-enterprises providing services. Under the directive, a micro-enterprise is a business employing fewer than 10 persons with an annual turnover or annual balance sheet total not exceeding EUR 2 million. According to the European Commission, micro-enterprises that provide services, such as a small online shop, are exempt from the service accessibility requirements, though micro-enterprises that manufacture or import covered products are not exempt from the product requirements.

The exemption is narrower than it first appears. A merchant that grows past either threshold falls into scope, and member states may encourage micro-enterprises to comply voluntarily. Businesses near the line typically document their headcount and turnover so they can show why the exemption applied at a given time.

Disproportionate burden and fundamental alteration

The EAA allows an economic operator to claim that a requirement would impose a disproportionate burden or would fundamentally alter the nature of the product or service. The directive sets out criteria for that assessment and, according to the Commission, the operator must document it and may need to share it with the market surveillance authority on request. It is a narrow, evidence-based exception, not a general opt-out.

US law has its own analogues, including “undue burden” and “readily achievable” standards for barrier removal. In both systems, the key point is that the burden argument depends on the resources of the whole business, not of a single store or website team.

Marketplaces, platforms and third-party sellers

When a retailer sells through a marketplace, the marketplace operator generally controls the storefront interface, while the seller controls listing content such as product images, titles and descriptions. Responsibility can therefore be split: the platform may be accountable for the checkout and navigation, while the seller remains accountable for alt text, image clarity and descriptive copy it supplies.

Retailers running their own sites on hosted platforms face a similar split with theme developers, app vendors and payment providers. Contracts increasingly include accessibility warranties and conformance obligations for exactly this reason, which is why the procurement section below matters even for mid-sized merchants.

Business profile	Typical EAA position (EU sales)	Typical US position	Main practical risk
Micro online shop (under 10 staff, under EUR 2m)	Service requirements exempt, per the Commission	No size exemption from ADA lawsuits	US demand letters despite small size
Mid-sized D2C brand on a hosted platform	In scope for e-commerce service	In scope; nexus to stores raises exposure	Theme and app defects it does not directly control
Multi-channel chain with stores and apps	In scope, plus terminals in EU stores	In scope online and in store	Inconsistency between channels and regions
Marketplace seller only	Depends on division of control with the platform	Platform usually the primary defendant	Inaccessible listing content and images
Manufacturer or importer of covered hardware	Product requirements apply regardless of size	Varies by product and sector rules	CE marking and documentation gaps

What an accessibility audit actually inspects

An audit is not a single scan. A credible retail audit combines automated testing, manual expert review, assistive technology testing and, ideally, sessions with disabled users. Automated tools are fast and cheap, but accessibility specialists commonly estimate that they detect only a minority of WCAG issues, because many criteria require human judgment.

The automated layer

Automated scanners crawl pages and flag machine-detectable failures. WebAIM’s annual “Million” analysis of the top one million home pages has, in recent editions, found detectable WCAG failures on roughly 95 percent of them. The most common categories in that research are consistent year to year: low-contrast text, missing alternative text for images, missing form input labels, empty links, empty buttons and a missing document language.

Retail sites tend to fail these checks at scale because catalogs generate thousands of near-identical templates. A missing label on one filter component repeats across every category page, which is why automated findings on large stores often run into the tens of thousands while the underlying root causes number in the dozens.

The manual layer

Manual testing covers what scanners cannot judge: whether alt text is meaningful, whether the reading order makes sense, whether focus moves logically through a mega-menu, and whether a custom size selector or product configurator can be operated without a mouse. Auditors typically walk the critical retail journeys in sequence, and our ecommerce accessibility audit guide sets out the order to test them in.

1. Home page and global navigation, including mega-menus and search.
2. Category or listing pages, including filters, sorting and pagination.
3. Product detail pages, including image galleries, variant selectors and reviews.
4. Cart, including quantity changes, promo codes and shipping estimates.
5. Checkout, including address forms, error handling, payment fields and confirmation.
6. Account creation, login, order tracking and returns flows.

The assistive technology layer

Auditors test with screen readers such as JAWS, NVDA and VoiceOver, with screen magnification, with voice control, and with keyboard only navigation. Mobile apps receive the same treatment using platform screen readers on iOS and Android. This layer catches the defects that generate the most frustration: payment iframes that trap focus, modals that cannot be closed, and live cart updates that are never announced.

The physical store layer

Store audits measure routes, counters, door hardware, fitting rooms, parking and signage against the applicable building rules, which in the US means the 2010 ADA Standards. They also check operational practice: whether merchandising displays have narrowed aisles below the required width, whether accessible checkout lanes are actually staffed and open, and whether self-service kiosks provide a non-visual mode. Many in-store failures are not design failures at all but operational drift, the same pattern we describe for windows and fixtures in our piece on the signage, window display and permit rules main street forgets.

WCAG 2.2 and what changed

The W3C published WCAG 2.2 as a Recommendation in October 2023. It added criteria that matter directly to retail, including a minimum target size for pointer inputs (24 by 24 CSS pixels at level AA, with listed exceptions), a rule against making users re-enter information they have already provided in the same process, a requirement that keyboard focus is not entirely hidden by sticky headers or banners, and accessible authentication that avoids cognitive function tests such as transcribing puzzles. Many current audits test against WCAG 2.2 AA even where the legal benchmark is still 2.1, to future-proof the work.

The fixes that remove the most friction per hour spent

Remediation is a prioritization exercise. A retailer with 40,000 automated findings does not have 40,000 problems; it has a few dozen defective components and templates. The most efficient programmes fix shared components first, then the critical purchase path, then long-tail content.

High-yield fixes in the design system

• Color contrast tokens: adjusting a handful of brand colors in the design system can resolve thousands of contrast findings at once, provided text meets the WCAG ratio of at least 4.5:1 for normal text.
• Form components: giving every input a programmatic label, linking error messages to their fields and announcing errors to screen readers fixes the checkout, account and newsletter forms simultaneously.
• Focus styles: a visible, high-contrast focus indicator applied globally helps keyboard users and is often a one-line style change.
• Buttons and links: icon-only controls such as cart, wishlist and close buttons need accessible names; this is usually a template fix.
• Modals and drawers: cart drawers, cookie banners and promotional pop-ups need focus management and a keyboard way to close them.

High-yield fixes in the purchase path

The checkout deserves disproportionate attention because a defect there blocks revenue and is the scenario most often described in complaints. Common retail checkout issues include payment fields embedded in third-party iframes without labels, address autocomplete widgets that cannot be operated with a keyboard, CAPTCHA challenges without an accessible alternative, and session time-outs that clear the cart without warning.

Variant selectors are the second hotspot. Color swatches that convey meaning only through color, size buttons with no text equivalent, and “out of stock” states shown only by a strike-through line all fail common WCAG criteria. Each can usually be fixed in the product template once and inherited by every product.

High-yield fixes in content and catalog data

Alt text at catalog scale is a data problem, not a copywriting problem. Retailers that treat image descriptions as a structured product attribute, governed in the PIM alongside dimensions and materials, find it far easier to keep them complete; the same governance logic applies to all catalog data, as explained in our guide to product data, attributes and the digital shelf. Decorative images should be marked as such so screen readers skip them, while images that carry information, such as size charts, need either a text alternative or an equivalent HTML table.

A caution on overlays

Many retailers have been offered “one line of code” overlay widgets that promise automatic compliance. Disability advocacy groups and many accessibility practitioners have criticized these tools, and in 2025 the US Federal Trade Commission finalized an order against overlay vendor accessiBe; according to the FTC, the company had misrepresented that its AI-powered tool could make any website compliant with WCAG, and it agreed to pay USD 1 million. Overlays may add some user-facing settings, but they do not replace fixing the underlying code, and an overlay alone is generally not regarded as evidence of conformance.

Fix	Typical effort	Scope of impact	Priority
Contrast-compliant color tokens	Low (days)	Sitewide	First wave
Labeled, error-linked form components	Low to medium	Checkout, account, newsletter	First wave
Global visible focus indicator	Low	Sitewide	First wave
Accessible names for icon buttons	Low	Header, cart, product cards	First wave
Modal and drawer focus management	Medium	Cart, promotions, consent banners	Second wave
Variant selector rebuild	Medium	All product pages	Second wave
Payment iframe and CAPTCHA review with vendors	Medium to high (vendor-dependent)	Checkout	Second wave
Catalog alt text as governed attribute	High (ongoing)	All product imagery	Third wave, continuous

Accessibility statements and how to write an honest one

An accessibility statement is a public page explaining how accessible a website or app is, which standard it targets, where known gaps remain and how users can get help or report problems. For e-commerce services in the EU, the EAA requires providers to make information available on how the service meets the accessibility requirements, according to the European Commission, and many national implementing laws expect this in the general terms and conditions or an equivalent public document.

What a credible statement contains

• The standard targeted: for example, WCAG 2.2 level AA, or EN 301 549 for EU-facing services.
• Conformance status: fully, partially or not conformant, stated plainly.
• Known limitations: specific areas that do not yet meet the standard, with any workarounds.
• Assessment method: internal review, external audit or both, and the date of the last assessment.
• Feedback and contact routes: at least two channels, such as email and phone, with an expected response time.
• Enforcement information: in the EU, the national authority a user can contact if dissatisfied.

Why honesty beats boilerplate

A statement claiming full conformance on a site with obvious defects creates two problems. It undermines trust with disabled shoppers who immediately encounter the gaps, and it can become an exhibit in a dispute, since it documents what the business knew and claimed. A partial conformance statement with a dated remediation plan is generally a stronger position than an unsupported claim of perfection.

Statements also need owners and review dates. A statement written for a site launch and never revised quickly drifts out of date as themes, apps and checkout providers change. Many retailers tie the review to their release calendar or to the annual audit.

Procurement and wholesale buyers asking for evidence

The quietest driver of accessibility work is business-to-business purchasing. Large retailers, government buyers and corporate procurement teams increasingly ask suppliers for documented accessibility conformance, both for software they license and, in some categories, for products and digital content they resell.

VPATs and accessibility conformance reports

In the US, the common format is the Voluntary Product Accessibility Template (VPAT), maintained by the Information Technology Industry Council. A completed VPAT is known as an Accessibility Conformance Report (ACR) and documents, criterion by criterion, how a product meets standards such as WCAG, Section 508 of the Rehabilitation Act (which governs federal agency procurement) and EN 301 549. Retail technology vendors, from POS providers to e-commerce platforms, are routinely asked for ACRs during selection.

What buyers check in practice

Procurement teams rarely have accessibility specialists on staff, so they look for signals: a recent ACR prepared by a credible third party, an accessibility statement, a named owner, a remediation roadmap and contract language committing to maintain conformance through updates. Suppliers that can produce these quickly shorten sales cycles; suppliers that cannot may be screened out before price is discussed.

Flowing obligations down the supply chain

Retailers are now writing the same demands into their own vendor contracts. Typical clauses require WCAG 2.1 or 2.2 AA conformance for delivered components, a duty to remediate defects within a defined period, cooperation in audits and, in some cases, indemnities for claims arising from vendor-caused defects. This matters because, as noted above, a large share of storefront defects originate in third-party code the retailer does not write.

Budgeting a remediation programme over four quarters

Costs vary widely by catalog size, platform, number of markets and the state of the existing code, so any single figure would be misleading. What can be described reliably is the shape of a typical programme and where the money goes. The plan below assumes a mid-sized multi-channel retailer starting from a site that has never been formally audited.

Quarter 1: baseline and governance

The first quarter is about measurement and ownership. Typical activities are a full external audit of key templates and journeys, a scan of the whole catalog to size the long tail, an inventory of third-party scripts and vendors, appointment of an accountable owner, and an honest interim accessibility statement. Spending is concentrated on audit fees and internal time.

Quarter 2: shared components and checkout

The second quarter delivers the first-wave fixes from the table above: color tokens, form components, focus styles, icon button names and the checkout path. This is usually the quarter with the highest engineering cost, but also the one that removes the most risk, because it addresses the journeys most likely to be tested by a plaintiff, a regulator or a buyer.

Quarter 3: product pages, apps and stores

The third quarter extends the work to variant selectors, galleries, reviews and the mobile apps, and begins physical store work where audits found barriers. Store remediation tends to split into cheap operational fixes, such as clearing aisles and staffing accessible lanes, and capital items, such as counter or fitting room alterations, which are often scheduled into planned refits rather than done as standalone projects.

Quarter 4: verification, documentation and maintenance

The final quarter is verification: a re-audit, user testing with disabled shoppers, an updated statement and, for retailers that sell technology or services to other businesses, a refreshed ACR. Crucially, it also builds maintenance into normal operations, with accessibility checks in the design system, automated tests in the deployment pipeline, training for content teams and accessibility criteria in vendor contracts.

Quarter	Main deliverables	Main cost drivers	Evidence produced
Q1	Audit, catalog scan, vendor inventory, owner, interim statement	External audit fees, internal analysis time	Audit report, issue backlog, interim statement
Q2	Design system fixes, checkout remediation	Front-end engineering, vendor coordination	Release notes, retest results for checkout
Q3	Product pages, apps, store operational and capital fixes	Engineering, store works, fixtures	App test reports, store audit follow-up
Q4	Re-audit, user testing, updated statement, ACR, pipeline checks	Re-audit fees, user research, tooling	Updated statement, ACR, test coverage records

Where budgets usually go wrong

The most common budgeting error is treating accessibility as a one-off project. Retail sites change weekly; new campaigns, apps and marketplace integrations reintroduce defects unless checks are part of the release process. The second error is ignoring vendors: if the payment provider, review widget or chat tool is inaccessible, internal fixes cannot make the journey conformant. The third is underestimating content, since thousands of product images and promotional banners need ongoing governance rather than a single clean-up.

For multi-channel operators, accessibility planning also belongs in the broader store and format strategy outlined in our analysis of where department stores, grocers and experiential retail are heading. Refits, new formats and self-service technology are the moments when accessible design costs least to include and most to retrofit later.

Important note on legal information

This article is general information and education about how accessibility rules and practices work in retail. It is not legal advice and does not describe the obligations of any particular business. Accessibility laws, standards, deadlines and enforcement practices differ by country, state and sector, and they change over time; the figures and rules cited here are attributed to their official sources and should be verified there before any decision is made. Readers with questions about their own situation should consult a qualified attorney or a certified accessibility professional familiar with the relevant jurisdiction.

FAQ on retail accessibility

What is retail accessibility compliance?

It is the practice of making online stores, apps and physical stores usable by people with disabilities in line with applicable laws and standards. In practice, that usually means designing and testing digital channels against WCAG at level AA and physical premises against the relevant building rules, such as the 2010 ADA Standards in the US, and documenting the results.

Does the ADA apply to online stores?

The US Department of Justice states in its web guidance that the ADA applies to the web offerings of businesses open to the public. Courts have not been uniform, with some requiring a connection to a physical location, so exposure can depend on the jurisdiction. In practice, many retailers treat their websites and apps as covered and use WCAG AA as the working benchmark.

When did the European Accessibility Act start to apply?

According to the European Commission, the EAA became applicable on June 28, 2025. The directive includes transitional provisions, including for services using products that were lawfully in use before that date and for certain self-service terminals, so the exact timeline for a specific product or service should be checked against the directive and the relevant national law.

Are small online shops exempt from the EAA?

The directive exempts micro-enterprises providing services, defined as businesses with fewer than 10 employees and an annual turnover or balance sheet total not exceeding EUR 2 million, from the service requirements. The exemption does not cover micro-enterprises that manufacture or import covered products, and businesses that cross either threshold fall into scope.

Which WCAG version should a retail site target?

Most legal benchmarks and settlements still reference WCAG 2.0 or 2.1 at level AA, and the EU harmonized standard EN 301 549 incorporates WCAG 2.1 AA. Many retailers test against WCAG 2.2 AA, published by the W3C in October 2023, because it is backward compatible and adds criteria relevant to checkout, target sizes and authentication.

Can an accessibility overlay make a store compliant?

Overlays are widely criticized by accessibility practitioners and disability advocates, and they do not fix underlying code. In 2025 the FTC finalized an order against overlay vendor accessiBe over claims, according to the agency, that its tool could make any website WCAG compliant. Code-level remediation remains the generally accepted route to conformance.

What does an accessibility audit cost a retailer?

Costs depend on the number of templates, journeys, apps and markets in scope, and on whether user testing and physical store audits are included. Rather than relying on a single figure, retailers usually request quotes scoped by template and journey, and budget separately for remediation, re-testing and ongoing maintenance.

What should an accessibility statement include?

A credible statement names the standard targeted, gives an honest conformance status, lists known limitations, explains how and when the site was assessed, and provides at least two contact routes for feedback. EU-facing statements commonly also name the national authority users can contact.

Do physical stores need to change if the website is accessible?

Yes, they are assessed separately. In the US, physical stores must meet the 2010 ADA Standards for new construction and alterations, and existing stores must remove barriers where readily achievable. Common store issues include narrowed aisles, inaccessible counters and fitting rooms, and self-service kiosks without a non-visual mode.