ADA Website Compliance for Online Stores

Why ADA Applies to Websites

The ADA was signed into law in 1990, long before the commercial internet existed. Title III of the ADA requires that "places of public accommodation" be accessible to people with disabilities. The original law listed physical locations like hotels, restaurants, and retail stores. The legal question of whether websites qualify as places of public accommodation has been settled through a decade of court decisions, with the majority of federal circuits ruling that websites are covered, particularly when connected to a physical business or when the website itself is the primary means of accessing the business's goods and services.

The Department of Justice confirmed in 2022 that web accessibility is covered under Title III and that businesses must ensure their websites are accessible to people with disabilities. While the DOJ has not yet issued specific technical standards for websites, courts consistently reference the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the benchmark for compliance. The WCAG is published by the World Wide Web Consortium (W3C) and provides detailed, testable criteria for making web content accessible.

For ecommerce businesses, the legal exposure is straightforward. Your website is the primary way customers access your products and services. If a person with a visual impairment cannot navigate your product pages, complete a purchase, or access customer service through your website because it is not compatible with screen readers, that person is being denied equal access to your business. This denial of access is what ADA lawsuits are built on.

Who Files ADA Website Lawsuits

The majority of ADA website lawsuits are filed by a small number of law firms that specialize in serial ADA litigation. These firms employ or represent plaintiffs with disabilities who test websites for accessibility failures, then file lawsuits or demand letters seeking settlements. The typical settlement for a small business ranges from $5,000 to $25,000, plus the cost of remediation and attorney's fees. Larger businesses face demands of $50,000 to $150,000 or more.

Critics call this "drive-by" litigation because the same plaintiffs file dozens or hundreds of lawsuits against different businesses. However, courts have consistently allowed these cases to proceed because the underlying accessibility failures are real, regardless of the plaintiff's motivation. The fact that a plaintiff tests many websites does not diminish their standing as a person with a disability who was denied access to your business.

The most targeted industries are retail and ecommerce (over 70% of ADA website lawsuits), food and beverage, hospitality, and entertainment. Within ecommerce, businesses with high-traffic websites and clearly non-compliant elements (missing alt text on product images, inaccessible checkout forms, missing form labels) are the easiest targets because the accessibility failures are obvious and easily documented.

WCAG 2.1 Level AA: The Standard

WCAG 2.1 Level AA is organized around four principles: perceivable, operable, understandable, and robust (POUR). Each principle contains specific guidelines with testable success criteria. For ecommerce websites, the most critical requirements fall into these categories.

Perceivable

All content must be presentable to users in ways they can perceive, including users who are blind, deaf, or have low vision. This means every product image must have descriptive alt text that conveys the information the image provides (not just "product image" but "Blue cotton crew neck t-shirt, front view"). All video content needs captions. All audio content needs transcripts. Text must have sufficient color contrast against its background, with a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text. Users must be able to resize text up to 200% without loss of content or functionality.

Operable

All website functionality must be operable through a keyboard alone, without requiring a mouse. This includes navigation menus, product filters, add-to-cart buttons, checkout forms, and account management pages. Users who rely on keyboards or assistive technology cannot use mouse-dependent features like hover menus, drag-and-drop interactions, or click-only controls. Focus indicators must be visible so keyboard users can see which element is currently active. Pages must not contain content that flashes more than three times per second, which can trigger seizures in users with photosensitive epilepsy.

Understandable

The interface must be understandable and predictable. Form fields must have visible labels that describe what information is expected (not just placeholder text that disappears when the user starts typing). Error messages must identify the field with the error and describe how to fix it. Navigation must be consistent across pages. The page language must be specified in the HTML lang attribute so screen readers pronounce content correctly.

Robust

Content must be robust enough to be interpreted by a wide variety of assistive technologies, including screen readers, voice recognition software, and switch devices. This primarily means using valid, semantic HTML. Buttons should use the button element, not styled divs with click handlers. Links should use anchor elements. Form fields should be associated with their labels using the for attribute. Custom interactive components should use ARIA (Accessible Rich Internet Applications) roles and properties to communicate their purpose and state to assistive technology.

Common Accessibility Failures in Online Stores

Missing alt text on product images. This is the single most common failure and the easiest to fix. Screen reader users rely on alt text to understand what a product looks like, since they cannot see the image. Every product image, variant image, and lifestyle image needs descriptive alt text. Your ecommerce platform likely has an alt text field for every image, but many store owners leave it blank or fill it with the product name only.

Inaccessible checkout forms. Form fields without properly associated labels, missing error messages, and forms that cannot be completed using only a keyboard are common in custom checkout implementations and some third-party checkout plugins. The checkout is the most critical page on your site for accessibility because it is where the transaction occurs. A user who can browse your products but cannot complete checkout is being denied the ability to purchase.

Poor color contrast. Light gray text on white backgrounds, low-contrast buttons, and product descriptions in colors that do not meet the 4.5:1 contrast ratio affect users with low vision and color blindness. This affects a significant portion of users, as roughly 8% of men and 0.5% of women have some form of color vision deficiency.

Missing skip navigation links. Screen reader and keyboard users must tab through every navigation element on every page to reach the main content unless you provide a "skip to main content" link at the top of the page. For a store with a complex header, mega menu, and promotional banner, navigating past these elements on every page load is extremely tedious without a skip link.

Inaccessible dropdown menus and filters. Product category filters, sort-by menus, and size/color selectors that work only with mouse clicks are useless to keyboard and screen reader users. These elements need keyboard operability (arrow keys to navigate, Enter to select) and ARIA attributes to communicate their state and options.

How to Test Your Store's Accessibility

Start with automated testing tools that scan your website and identify WCAG violations. Free tools include WAVE (wave.webaim.org), which provides a visual overlay of accessibility issues on any page, axe DevTools (a browser extension by Deque), which runs a comprehensive audit from Chrome's developer tools, and Google Lighthouse, which includes an accessibility audit as part of its performance analysis. These tools catch roughly 30% to 40% of accessibility issues, primarily technical issues like missing alt text, contrast failures, and missing form labels.

Automated tools cannot catch all issues. Manual testing is required for keyboard navigation (can you complete a purchase using only Tab, Enter, Space, and arrow keys?), screen reader compatibility (does the checkout make sense when read aloud by VoiceOver, NVDA, or JAWS?), and logical reading order (does the content flow in a meaningful sequence when CSS is disabled?). Recruit users who actually rely on assistive technology for the most thorough testing.

Professional accessibility audits from firms like Deque, Level Access, or TPGi cost $5,000 to $25,000 depending on the size and complexity of your site. For small stores, this may be overkill. A combination of automated testing with WAVE and axe, plus manual keyboard testing of your core user flows (browsing, adding to cart, checkout, account management), catches the majority of high-risk issues for a fraction of the cost.

Overlay Widgets: Why They Are Not the Answer

Accessibility overlay widgets from companies like accessiBe, UserWay, and AudioEye promise one-click WCAG compliance by adding a JavaScript widget to your site. These tools add adjustable text sizes, contrast toggles, and other features through an overlay menu. While these tools can help with some accessibility issues, the disability community, accessibility professionals, and the National Federation of the Blind have consistently criticized overlay widgets as inadequate substitutes for actual accessible code.

Overlays do not fix underlying code issues. A form without proper labels is still inaccessible to screen readers regardless of what overlay widget is present. Overlays can also conflict with users' existing assistive technology settings, creating a worse experience rather than a better one. Several companies that relied on overlay widgets as their sole accessibility solution have been successfully sued, with courts rejecting the argument that the overlay made the site compliant. The overlay can supplement genuine accessibility work, but it cannot replace it.

Building Accessibility Into Your Store

The cheapest and most effective approach is to build accessibility in from the start rather than retrofitting it later. If you are choosing a Shopify theme or WooCommerce template, check whether the theme developer specifically addresses accessibility. Themes from reputable developers like Out of the Sandbox (Turbo), Archetype (Impulse), and the default Shopify Dawn theme have good accessibility foundations. Third-party themes from less established developers may have significant accessibility gaps.

When adding apps, plugins, or custom code to your store, test the accessibility impact of each addition. A product review app that injects content without proper heading structure, a popup that traps keyboard focus, or a product quickview modal that cannot be closed with the Escape key all introduce accessibility barriers. Evaluate accessibility as part of your decision-making process for any new tool or feature.

Document your accessibility efforts with an accessibility statement page on your website. This statement should describe your commitment to accessibility, the standard you are working toward (WCAG 2.1 Level AA), the steps you have taken, known limitations, and how users can report accessibility issues. An accessibility statement demonstrates good faith, which is relevant in litigation because it shows you are actively working toward compliance rather than ignoring the issue.