Ecommerce Accessibility 2026: WCAG 2.2 AA, ADA Compliance, and Legal Exposure for DTC

The lawsuit letter that usually arrives on a Monday

In 2025, US courts saw more than 4,300 ADA Title III website accessibility lawsuits filed against ecommerce companies, a 19 percent increase over 2024. The overwhelming majority were filed by a small set of plaintiff law firms, against DTC brands that had no idea their storefront was out of compliance until the letter arrived. The average brand learned about WCAG and overlay widgets on the same day they hired a defense attorney.

Accessibility is not an edge case. Roughly 15 percent of US adults have a disability that affects how they use the web. Older shoppers, users on poor connections, users on small screens, and users with temporary impairments all benefit from the same design and engineering choices that make a site WCAG conformant. Accessibility is one of the rare disciplines where legal protection, ethical practice, and conversion lift point in the same direction. At Pixeltree, we treat it as an operational hygiene item, not a special project, and the brands we work with spend less on defense and more on building.

TL;DR ▸ WCAG 2.2 AA is the de facto US legal standard and the EU required standard under the European Accessibility Act of June 2025. ▸ Overlay widgets do not create compliance and have been named in lawsuits. They are not a remediation strategy. ▸ Automated testing catches 30 to 40 percent of issues. Manual testing with keyboard and screen readers catches the rest. ▸ Checkout, PDP, and cart are the highest-risk pages. They are where sales fail and where lawsuits succeed. ▸ A 90-day remediation reliably lifts conversion 4 to 12 percent while substantially reducing litigation exposure.

Table of contents

• Why accessibility matters: legal and conversion
• ADA lawsuit trends in 2025 and 2026
• WCAG 2.2 AA requirements for ecommerce
• The overlay widget myth
• Automated testing versus manual testing
• PDP and checkout accessibility specifics
• Color contrast, font size, and visual design
• Keyboard navigation and focus management
• Screen reader compatibility
• The 90-day remediation roadmap
• What to ship this quarter

Why accessibility matters: legal and conversion

There are two honest reasons a DTC brand should care about accessibility in 2026. The legal exposure is real, and the conversion impact is material. Either alone would justify the investment. Together they make it a non-negotiable.

On the legal side, the ADA Title III litigation landscape has matured into a predictable pattern. A small set of plaintiff law firms monitor ecommerce sites with automated scanning tools, identify brands with clear WCAG failures, and send demand letters or file suits. The brands targeted are not random. They skew toward growing DTC companies with traffic volume, a recognizable brand name, and no visible accessibility statement. Most settlements are in the 10k to 75k range in direct payment, plus plaintiff attorney fees under the ADA's fee-shifting provision, plus internal legal and remediation costs. A single case usually costs more than a year of proactive accessibility work.

On the conversion side, the math is cleaner than most operators expect. Roughly 15 percent of US adults report a disability that affects web use. A larger population has temporary or situational impairments on any given day. Accessibility improvements tend to help all of them, plus aging users, plus users on slow connections, plus users navigating with one hand on a subway. Typical DTC brands see 4 to 12 percent conversion lift after a substantive WCAG 2.2 AA remediation, with larger lifts on mobile and on considered-purchase categories.

For the full compliance framework, see our compliance audits service and the ADA WCAG audit methodology.

ADA lawsuit trends in 2025 and 2026

The lawsuit pattern against ecommerce brands has evolved meaningfully in the last three years. Five trends define the current landscape.

First, filing volume is up and still rising. More than 4,300 ADA web accessibility cases were filed against ecommerce defendants in 2025, with a compound annual growth rate of roughly 18 percent over the prior three years.

Second, repeat litigation is common. A brand sued once has a materially higher chance of being sued again, often by a different plaintiff in a different jurisdiction. One lawsuit is a warning. Two is a pattern that invites more.

Third, overlay widget defenses have weakened. Multiple federal cases have explicitly held that installing an overlay widget does not constitute compliance, and in some cases the widget itself was cited as evidence that the brand knew of the problem and chose a non-remediation path.

Fourth, state-level exposure is growing. New York, California, Florida, and Illinois have emerged as high-volume jurisdictions, and California's Unruh Act creates additional statutory damages per violation.

Fifth, the European Accessibility Act, effective June 2025, has extended exposure for any US DTC brand shipping to or marketing in the EU. The legal framework is different but the WCAG 2.2 AA standard is essentially the same.

The practical implication: the cost of non-compliance is rising while the cost of proactive remediation is stable. The value of acting before the letter arrives has never been higher.

WCAG 2.2 AA requirements for ecommerce

WCAG 2.2 AA is structured around four principles: Perceivable, Operable, Understandable, Robust, collectively known as POUR. Each principle has specific success criteria at A, AA, and AAA levels. AA is the de facto legal standard.

The most commonly violated criteria on DTC ecommerce sites, in our audit experience:

• 1.1.1 Non-text content: Images without descriptive alt text, including product images, hero banners, and decorative icons. This is the single most common failure on DTC sites.
• 1.3.1 Info and relationships: Form fields without proper labels, headings used for visual styling rather than structure, tables without header associations.
• 1.4.3 Contrast minimum: Text with insufficient contrast against its background, commonly found on sale badges, muted secondary text, and brand-colored buttons.
• 2.1.1 Keyboard: Interactive elements that cannot be operated with a keyboard alone, including variant pickers, cart drawers, and image galleries.
• 2.4.3 Focus order: Tab order that does not match visual order, often caused by CSS positioning that reorders elements visually without updating DOM order.
• 2.4.7 Focus visible: Focus indicators hidden or removed via CSS outline: none with no replacement.
• 3.3.2 Labels or instructions: Form fields with placeholder text as the only label, which disappears on focus and fails screen readers.
• 4.1.2 Name, role, value: Custom components built without proper ARIA attributes, including drawers, modals, and custom dropdowns.
• 2.4.11 Focus not obscured (WCAG 2.2 addition): Sticky headers or banners that cover the focused element during keyboard navigation.
• 2.5.8 Target size minimum (WCAG 2.2 addition): Interactive targets smaller than 24x24 pixels, common in icon-only buttons and close controls.

The table below summarizes the highest-frequency failures and the most effective remediations on Shopify and similar DTC stacks.

The overlay widget myth

Accessibility overlay widgets are JavaScript tools that inject a button on the site offering adjustments like font size, contrast, and text-to-speech. They are marketed as a one-line solution to accessibility compliance. They are not.

The evidence is clear and growing. Multiple federal cases have held that overlay widgets do not remediate underlying WCAG failures. Screen reader users consistently report that overlays interfere with their own assistive technology, making sites less usable rather than more. A coalition of accessibility advocates and professionals issued an open letter in 2021 recommending against overlay use, and the consensus has only strengthened since.

The practical failure modes of overlays:

1. They do not fix semantic HTML problems. If your headings are wrong or your buttons are divs, an overlay cannot help.
2. They do not fix keyboard navigation. If your cart drawer does not trap focus, an overlay cannot fix it.
3. They do not fix alt text. If your product images have no descriptions, no overlay can generate meaningful ones.
4. They interfere with screen readers. Some overlays inject aria attributes and focus changes that conflict with the user's own assistive technology.
5. They create legal exposure. The presence of an overlay indicates the brand knew accessibility was an issue and chose not to remediate the actual site.

The right path is substantive remediation of the underlying code. It is more work up front, but it is the only approach that actually makes the site usable and the only approach that stands up in court.

Automated testing versus manual testing

Accessibility testing is two disciplines, and neither alone is sufficient.

Automated testing uses tools like axe-core, WAVE, Lighthouse, and Pa11y to scan HTML for detectable violations. Automated tools catch roughly 30 to 40 percent of WCAG issues: missing alt text, color contrast failures, missing form labels, and structural problems. Integrate an automated scanner into your CI pipeline and run it on every deploy.

Manual testing catches the remaining 60 to 70 percent. It includes:

• Keyboard-only navigation through every page and interactive element
• Screen reader testing with NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android
• Zoom testing at 200 percent and 400 percent
• Cognitive walkthroughs for task completion
• Focus management review across modals, drawers, and dynamic content

The mature accessibility program runs automated tests continuously in CI and manual audits quarterly or after major releases. A single initial audit is not enough. Regression is inevitable without ongoing monitoring.

PDP and checkout accessibility specifics

The highest-value pages on a DTC ecommerce site are also the highest-risk for accessibility failures. Focus remediation effort on the pages where sales fail and where lawsuits succeed.

Product detail pages have four common failure patterns. First, variant pickers built as custom dropdowns without proper ARIA. Second, image galleries with thumbnails that cannot be navigated with keyboard. Third, review widgets from third-party apps that are built without accessibility in mind. Fourth, Add to Cart buttons that send focus to a cart drawer without proper announcement.

The fixes are mostly mechanical. Use native select elements or properly-built custom controls with role, aria-expanded, and keyboard handlers. Ensure every image in the gallery has descriptive alt text and every thumbnail is reachable by keyboard. Audit third-party review apps and replace ones that cannot be made accessible. When Add to Cart opens a drawer, move focus into the drawer, trap focus there, and return focus on close.

Checkout is the highest-risk page for both conversion and legal exposure. Common failures include:

• Shipping and payment fields without persistent labels
• Error messages that appear visually but are not announced to screen readers
• Radio groups and checkboxes without proper fieldset and legend structure
• Country and state selectors that do not handle keyboard input correctly
• Credit card fields in iframes that disrupt the accessibility tree

Shopify's native checkout has improved substantially in recent years, but brands using Shopify Plus with checkout customizations, or brands on custom checkouts, need explicit testing. See CRO service and Shopify development for implementation support.

Color contrast, font size, and visual design

Visual design choices drive a large share of accessibility failures, and they are usually the easiest to fix.

The contrast requirements at WCAG 2.2 AA:

• Body text: 4.5:1 contrast ratio against background
• Large text (18pt or 14pt bold): 3:1 contrast ratio
• UI components and graphical objects: 3:1 contrast ratio (WCAG 2.1 addition)

The most common contrast failures on DTC sites are muted gray text on white, brand-colored buttons with white text where the brand color is light, and sale badges with insufficient contrast. A contrast audit across the design system usually identifies 10 to 30 token-level fixes that cascade across the entire site.

Font size guidance:

• Minimum 16 pixel base body font on mobile and desktop
• No text-only images for content that could be rendered as text
• Line height at least 1.5x the font size
• Paragraph spacing at least 2x the font size
• User-resizable text up to 200 percent without loss of content or functionality

These are not just accessibility requirements. They are readability requirements that improve engagement metrics across the full user base.

Keyboard navigation and focus management

Keyboard navigation is the single most revealing accessibility test. Open your site, put your mouse away, and try to complete a purchase using only Tab, Shift-Tab, Enter, Space, and arrow keys. Most DTC sites fail this test somewhere between the homepage and the order confirmation.

The rules that make keyboard navigation work:

1. Every interactive element must be reachable by Tab.
2. Tab order must match visual order.
3. Focus must always be visible with a clear focus indicator.
4. Modals and drawers must trap focus inside them while open and return focus to the trigger on close.
5. Skip links at the top of the page must allow skipping to main content.
6. Custom components must handle arrow keys, Enter, Space, and Escape correctly.
7. Sticky headers and banners must not obscure focused elements (WCAG 2.2 criterion 2.4.11).

The sticky header problem deserves specific attention. A common pattern on DTC sites is a sticky announcement bar plus sticky navigation that together occupy 120 or more pixels at the top of the viewport. When a keyboard user tabs to an element just below the sticky area, that element is visually hidden. This is a WCAG 2.2 AA violation introduced specifically to address the pattern.

Screen reader compatibility

Screen reader testing is the final gate before calling a page accessible. Automated tools cannot simulate the experience of navigating a site by voice and keyboard alone.

The practical testing protocol:

• Test primary flows with NVDA plus Firefox on Windows
• Test with VoiceOver plus Safari on macOS and iOS
• Test with TalkBack plus Chrome on Android for mobile-critical flows
• Verify landmark structure with the rotor or elements list
• Verify heading hierarchy with heading navigation
• Verify form field labels and error announcements
• Verify dynamic content announcements (cart updates, form errors, success messages)
• Verify modal and drawer focus behavior

The common failures that only surface in screen reader testing:

1. Interactive elements announced as "clickable" with no name or role
2. Error messages that appear visually but are silent to screen readers
3. Cart counts that update visually but are not announced as a live region
4. Loading spinners with no text equivalent
5. Custom dropdowns that do not announce state changes
6. Icon-only buttons with no accessible name

The 90-day remediation roadmap

Days 1 to 14: Audit and risk assessment. Run automated scanning across home, collection, PDP, cart, checkout, and account pages. Complete a manual keyboard audit of the same pages. Complete a screen reader spot check on purchase flow. Prioritize findings by WCAG criterion and by legal risk. Publish an accessibility statement on the site that documents the conformance goal and the current status. The accessibility statement is both a good faith signal and a legal asset.

Days 15 to 45: Design system and global fixes. Fix color contrast at the design token level so every component inherits the change. Standardize focus indicator styling across all interactive elements. Establish alt text guidelines and backfill product image alt text across the catalog. Fix form labels, error handling, and focus management globally. Remove any overlay widgets and communicate the move internally.

Days 46 to 70: Page-level and component-level fixes. Rebuild variant pickers, cart drawers, and modals with proper ARIA and keyboard support. Fix third-party app embed issues or replace apps that cannot be made accessible. Complete sticky header audit for WCAG 2.2 criterion 2.4.11. Add skip links and verify landmark structure on every template.

Days 71 to 90: Testing, monitoring, and ownership. Complete manual QA with external testers who use assistive technology. Install automated accessibility checks in CI with a named owner. Schedule quarterly manual audits. Update the accessibility statement with the new conformance level. Train the product and design team on accessibility acceptance criteria for new features.

Impact and math

A substantive 90-day remediation typically produces these outcomes for a DTC brand:

• Conversion rate lift: plus 4 to 12 percent, with larger gains on mobile
• Average order value: plus 2 to 6 percent from reduced drop-off on considered purchase flows
• Bounce rate: minus 5 to 15 percent on the pages most affected by remediation
• Legal exposure: materially reduced, with most brands exiting the highest-risk tier
• Brand perception: measurable lift in NPS and repeat purchase intent in post-purchase surveys
• SEO: modest direct impact, with indirect benefits from improved semantic HTML and mobile usability

These ranges are empirical across the DTC brands Pixeltree has taken through full WCAG 2.2 AA remediation. Exact outcomes depend on the starting baseline, the product category, and the quality of the creative and merchandising already in place.

Industry-specific notes

Accessibility risk and opportunity varies by category. Apparel and fashion brands are at elevated risk because of heavy reliance on imagery and variant pickers. See our apparel and fashion industry page. Beauty and skincare brands see strong conversion lift from remediation because of an older customer demographic with higher rates of vision-related impairment. See our beauty and skincare industry page.

For related compliance work, see our writeups on claim substantiation and privacy compliance audits. Trust elements work alongside accessibility to build conversion confidence. See our guide on trust badges that actually convert.

What to ship this quarter

▸ Run an automated accessibility scan on home, PDP, cart, and checkout, and publish the findings internally. ▸ Remove any accessibility overlay widgets and communicate the decision to the team. ▸ Publish an accessibility statement documenting your conformance goal and current status. ▸ Fix color contrast at the design token level so every component inherits the change. ▸ Backfill descriptive alt text across the full product catalog. ▸ Rebuild cart drawer and variant picker with proper focus trap, keyboard support, and ARIA. ▸ Add persistent visible labels to every form field across the site. ▸ Install automated accessibility checks in CI with a named engineering owner. ▸ Complete manual keyboard and screen reader QA on the full checkout flow. ▸ Schedule the first quarterly manual audit and assign the accessibility owner role.

Accessibility is engineering discipline, not a checkbox. The brands that treat it as ongoing hygiene spend less on lawsuits, convert more of their traffic, and build better products for everyone. The brands that wait for the letter usually spend more on defense than the full remediation would have cost.