Customer making a card payment using a handheld payment terminal.

Image description: Customer making a card payment using a handheld payment terminal.

eCommerce checkout: The most litigated surface on the internet

AIOPSGROUP · Accessibility inteligence
Litigation analysis · Federal court filings · 2007–2026

eCommerce checkout: The most litigated surface on the internet

A dataset of 8,788 federal web-accessibility lawsuits reveals an unflattering pattern. The same handful of bugs ship to production at the same handful of stages – and the same handful of plaintiffs find them. Of 81,509 issues attorneys catalogued in court filings, more than 4,050 are concentrated in the five surfaces that turn a browser into a buyer: cart, address, payment, error states, and the checkout button itself.

4,050
checkout-stage issues cited in court filings (cart, address, payment, add-to-cart, checkout flow)
7.4×
growth in annual filings, 2021 → 2025 (466 → 3,449 cases)
97
median days from complaint filed to case closed (suggesting settlement)
83.4%
of all closed cases resolve in under six months – defendants pay or remediate, then move on. The cycle is engineered for volume, not contest.

Why checkout is the violation that costs you

Web-accessibility lawsuits are filed at every layer of a website – homepage, navigation, footer, search. But on the rare occasions a complaint reaches dispositive motion, courts are unmoved by aesthetic barriers. They are moved by transactional ones. A blind shopper who cannot find a hero banner has, in the bluntest legal terms, lost nothing. A blind shopper who cannot complete a purchase has been denied a service the seller offered to every other visitor. That is the textbook formulation of a Title III violation, and it is the same fact pattern that recurs in every demand letter the plaintiff bar drafts.

This is why the dataset’s most-cited surfaces are not the surfaces that produce the most complaints overall. “General / Uncategorized” is by far the largest issue bucket (38,671 issues). But on the basis of dollars at stake per failure, the checkout funnel out-litigates every other category combined. Each unlabeled CVC field is a denial of service. Each unannounced “Order Confirmed” is a transaction the user cannot prove they made. Each modal that traps focus on the “Apply Coupon” step is a discount the screen-reader user paid full price to skip.

The litigation primitive

In a US federal courtroom, the question is not “is the homepage accessible?” – it is “could the plaintiff buy what the defendant was selling?” Checkout is the only surface where the answer is binary, and the only surface where the damages are straightforward to plead.

The dataset

The analysis behind this article draws on two independent corpora. The first is a structured PACER snapshot of 8,788 federal civil cases filed under the Americans with Disabilities Act and parallel state statutes between January 2007 and April 2026, with each case linked to its plaintiff(s), defendant(s), filing date, and disposition date. The second is a parallel extraction of 81,509 distinct accessibility issues pulled from the text of those filings – the actual sentences attorneys wrote describing what their clients could not do.

The two together let us answer questions a single source cannot. We know not just which sites were sued, but what attorneys told the court was broken – and at which point in the user journey it broke. For this article we filtered the issue corpus to five purchase-funnel categories: CHECKOUT FLOW SHOPPING CART ADD TO CART PAYMENT ADDRESS MANAGEMENT. Together these five surfaces account for 4,050 issues – about 5% of the corpus, but the slice with the strongest causal link to dispositive harm.

Note on coverage The 8,788 figure includes accessibility cases targeting any digital surface; not all involved retail e-commerce. However, e-commerce sites and the franchises that operate them dominate the defendant list – Marriott, TJX, Tapestry, Wolverine World Wide, Five Below, Walgreens, Target, Genesco, Sherwin-Williams, GameStop, and Caleres each appear five or more times.

The curve nobody priced into the Q4 plan

Before discussing the inside of the funnel, it is worth establishing how steep the outside has become. Annual filings have grown by an order of magnitude since 2020 and continue to accelerate. The 2026 figure below covers only Q1; the full-year extrapolation places it on track to exceed 4,500 – almost ten times the 2021 baseline.

Fig. 1 Federal web-accessibility lawsuit filings by year, n=8,788
2019
6
0.07%
2020
45
0.51%
2021
466
5.30%
2022
755
8.59%
2023
1,018
11.58%
2024
2,156
24.53%
2025
3,449
39.25%
2026
878 ▱
Q1 only

▱ 2026 partial: filings through April 2026. At the Q1 pace the year is on track for ~3,500 filings, in line with the 2025 trend.

Two points worth absorbing. First, the inflection year is 2021 – coinciding with the post-pandemic e-commerce boom and a wave of state-court precedent (notably Robles v. Domino’s, denied cert by the Supreme Court in 2019) that left federal courts in the Ninth Circuit reading websites into Title III’s “places of public accommodation.” Second, growth has not plateaued. Each year since 2021 has set a new high, and each new annual high has been hit while Title III has remained, formally, unregulated for private commercial sites.

The funnel within the funnel

Of the 81,509 issues catalogued from filings, 4,050 fall into one of the five purchase-funnel categories below. The proportional distribution maps almost perfectly onto the canonical conversion funnel: more issues are reported earlier in the journey, with each step shedding both legitimate users and litigated barriers.

Fig. 2 Issue counts by purchase-funnel stage, n=4,050
Checkout Flow (overall)40.9%
1,656 issues
Shopping Cart / Basket Page25.2%
1,022 issues
Add to Cart / Basket17.7%
718 issues
Payment12.9%
524 issues
Address Management3.2%
130 issues

The “Checkout Flow” bucket is the largest because most filings narrate the experience as a single journey. But the breakdown is instructive: the cart and add-to-cart together (1,740 issues) generate slightly more litigated complaints than the checkout page itself. That is partly because the cart is where the first irreversible action happens – once the screen-reader user cannot confirm an item was added, every step that follows is performed in the dark. Issues that begin upstream compound downstream.

The five failures, in order of frequency

When the 4,050 checkout-stage issues are pattern-matched against their plain-text descriptions, five failure modes account for the majority of plaintiff complaints. We surface them below in order of how often they appear in filings, with the WCAG criteria attorneys most commonly cite alongside each.

№ 1
“I added it to my cart, but I never knew it was there.”
639filings reference add-to-cart failure

Add-to-Cart triggers a visual confirmation – toast, mini-cart slide-out, badge increment – that screen readers do not announce. The user re-clicks, doubles the order, or gives up. This is the single most-cited barrier in cart-related filings.

WCAG 4.1.3 status messagesWCAG 4.1.2 name role value
№ 2
“The promo code field told me nothing when it failed.”
566filings reference coupon / discount-code barriers

Coupon-code fields are unlabeled, error suggestions are not announced, and inline validation appears only as colored text. Plaintiffs commonly plead they paid full price because the discount channel was inaccessible – concrete monetary harm.

WCAG 3.3.1 error IDWCAG 3.3.3 error suggestions
№ 3
“A pop-up appeared. My focus did not.”
511filings reference modal / overlay focus failures

Address-confirmation dialogs, “are you sure?” interstitials, upsells, and CAPTCHA challenges appear visually but never receive programmatic focus. Keyboard and screen-reader users either cannot dismiss them or cannot proceed past them.

WCAG 2.4.3 focus orderWCAG 2.1.2 no keyboard trap
№ 4
“My CVC was wrong. The form said nothing.”
468filings reference unannounced error states

Required fields blank, regex-failed credit cards, and address mismatches surface only via red borders or vanishing-text validators. The screen-reader user submits, hears no feedback, and assumes the order went through. WCAG 3.3.1 is the single most-cited criterion in checkout filings.

WCAG 3.3.1 error IDWCAG 3.3.2 labels
№ 5
“The field was announced as ‘blank.'”
330filings reference unlabeled input fields

Card number, expiry, ZIP, “Same as billing” – unlabeled inputs are announced as “blank” or “edit text”. Users cannot tell which field is which, fill them in the wrong order, and trigger validation errors that themselves are not announced (see № 4).

WCAG 1.3.1 info & relationshipsWCAG 4.1.2 name role value
№ 6
“I had to start the checkout over.”
163filings reference forced re-entry

When a single field fails validation, some checkouts wipe and restart the entire form on reload. For users who took six minutes to complete it the first time with assistive tech, this is a barrier that does not exist for sighted, mouse-using buyers – the textbook unequal access claim.

WCAG 3.3.4 error preventionWCAG 2.5.3 label in name

The criteria attorneys actually cite

Most filings do not cite WCAG criteria explicitly – they describe symptoms. Where attorneys do cite specific criteria in checkout-stage allegations, however, the distribution is heavily skewed. Six criteria account for 89% of all explicit citations; the remaining sixty-plus criteria of WCAG 2.2 are mentioned in long-tail noise.

Fig. 3 WCAG 2.x criteria explicitly cited in 4,050 checkout-stage filings
WCAG Criterion name Level Cited in Share Where it bites in checkout
3.3.1 Error Identification A 104 32.5% Form failed to flag required fields and validation errors
2.4.3 Focus Order A 72 22.5% Modals, dialogs and step transitions did not move focus
2.1.1 Keyboard A 43 13.4% PayPal / express buttons unreachable without a mouse
4.1.3 Status Messages AA 26 8.1% “Added to cart,” “discount applied,” “order placed” silent
4.1.2 Name, Role, Value A 23 7.2% Custom radio/select widgets do not expose state to AT
3.3.2 Labels or Instructions A 18 5.6% CVC, ZIP, “Same as billing” announced as “blank”
1.3.1 Info and Relationships A 7 2.2% Step indicators not exposed; required-field grouping
2.4.7 Focus Visible AA 4 1.2% No visible focus on payment buttons
2.5.3 Label in Name A 1 0.3% Voice-control mismatches between visible and accessible name
Reading the table carefully

Only 320 of 4,050 issues (about 8%) cite a WCAG criterion by number. The rest describe the symptom in plain language. The implication: even if you ship a flawless WCAG 2.2 AA audit report, your engineering team is still being measured against the symptoms – “user could not complete purchase” is the standard a court will care about, not “Success Criterion 3.3.1 violated.”

What plaintiffs actually wrote

The dataset is built from court-filed pleadings. The sentences below are reproduced from those filings – anonymized to remove site references but otherwise unedited. They are useful because they communicate to engineering teams what users describe, in their own words, the way attorneys translated those descriptions into legal exhibits.

“Each of the text fields are announced as ‘blank.’ Options under the ‘Size’ drop-down are not accessible for the keyboard-only users.”– Forms allegation, S.D.N.Y. complaint
“After clicking the ‘Add to Cart’ button, a success message is displayed beside the button. This message is the only indicator that the item was successfully added – and it is not announced.”– Add-to-Cart allegation
“When the user tries to checkout and does not enter a zip code, there is no message to identify the error.”– Address Management allegation, repeated across 11 filings against different defendants
“Plaintiff was unable to determine if the form fields were mandatory (‘Required’) on the Checkout page. The lack of detailed instructions while filling in the form, prevented Plaintiff from successfully submitting.”– Checkout Flow allegation
“PayPal Button Not Keyboard Operable (Checkout Page) – The PayPal button receives visual focus but cannot be activated using the Enter key.”– Payment allegation, citing WCAG 2.1.1
“Plaintiff was unable to go back and make any corrections to form fields without reloading the whole page and starting over.”– Checkout Flow allegation, S.D.N.Y. case

What unifies the dataset is not technical sophistication. The barriers attorneys cite are not novel or obscure – they are the same dozen patterns, repeated across thousands of filings, against thousands of defendants. The plaintiff bar has effectively industrialized the discovery of bugs that engineering teams have not noticed because the engineering teams have not run their own checkouts with a screen reader.

The 97-day phenomenon

Of the 8,788 cases in the dataset, 6,945 had closed by April 2026 with valid filing and disposition dates. Their durations form one of the more revealing distributions in the corpus. The median time from complaint to closure is 97 days; 83.4% of all closures occur in under six months.

Fig. 4 Distribution of case duration from filing to closure, n=6,945
7.7%
< 30d534
37.6%
30–90d2,609
38.1%
90–180d2,643
12.6%
180–365d872
3.3%
1–2y227
0.9%
>2y60

Cases that close in under 180 days almost without exception do not produce a published merits ruling. They are settled. The shape of this distribution tells the strategic story of the entire plaintiff bar: file in volume, settle quickly, and avoid the small handful of dispositive opinions that would let defendants distinguish their checkouts from another company’s. The median settlement happens before either party files a motion to dismiss.

Why this matters operationally

Because cases close fast, there is no body of binding case law clarifying what “accessible checkout” means at the level a senior engineer would want. The standard is set instead by the cumulative content of settlement agreements – most of which require WCAG 2.1 AA conformance, an annual audit, and a remediation plan. Companies are paying for compliance with a standard that is established in private contracts but never adjudicated in published opinions.

The volume model: ten plaintiffs, 1,289 cases

The headline number – 8,788 cases – is misleading without one further breakdown. The plaintiff side of the docket is heavily concentrated. The ten most-active named plaintiffs in the dataset, taken together, account for 14.7% of all filings. The most prolific single plaintiff filed 256 separate cases.

Fig. 5 Top 10 plaintiffs by federal case volume (anonymized)
#Plaintiff (anonymized)Cases% of total
01Plaintiff A – most-prolific filer in the dataset
2562.91%
02Plaintiff B
2072.36%
03Plaintiff C
1581.80%
04Plaintiff D
1311.49%
05Plaintiff E
1211.38%
06Plaintiff F
1151.31%
07Plaintiff G
991.13%
08Plaintiff H
971.10%
09Plaintiff I
941.07%
10Plaintiff J
860.98%

Plaintiff names redacted; counts derived from PACER metadata. Of 8,788 filings the top ten plaintiffs filed 1,289 cases combined (14.66%). The top single plaintiff appears as named party in nearly 1 of every 35 cases in the dataset.

This concentration is not a sign of bad faith – many of these plaintiffs have legitimate, documented disabilities and have personally encountered the barriers their filings describe. But it is a sign that defendants who lose in court rarely lose to a stranger. The same names recur, often represented by the same firms, often filing on near-identical templates. The structure of the litigation rewards efficiency on the plaintiff side and rewards capitulation on the defendant side. It does not reward novel arguments from either.

The triage matrix

If the question is “what should I fix first,” the answer is a function of two things: how often a given barrier is cited (frequency), and how directly it blocks a transaction (severity). The matrix below combines both. Cells are coloured by relative volume of citations in our 4,050-issue checkout corpus, with the darkest cells representing the failure modes most worth a sprint.

Fig. 6 Failure × Stage matrix (citation density)
Failure pattern Add to Cart Cart Address Payment Confirmation
Status not announced High High Med Med High
Unlabeled fields Low High High
Errors not announced Low Med High High Med
Modal / focus loss High High Med Med Med
Keyboard inoperability Med Med Low High Low
Forced re-entry on error Low Med Med
CAPTCHA inaccessibility Low Med
Not commonly cited Low Medium High Very high

Two cells worth singling out. “Status not announced × Add-to-Cart” is the single most-cited barrier in the entire dataset; if you fix nothing else, fix this. “Unlabeled fields × Payment” is the textbook compliance failure – a credit-card form with announced-as-blank fields is the violation that cannot be argued.

What does this cost you, today, before any lawsuit?

Litigation exposure is one cost of an inaccessible checkout. The other – usually larger and always present – is the orders that never close because the buyer could not complete the form. The calculator below uses three inputs you can change to estimate that cost for your own funnel. Defaults are conservative, drawn from cross-industry baselines; adjust them to fit your business.

Inaccessible-checkout exposure model

All inputs are sliders. Numbers update live as you adjust. None of this is a quote – it is a back-of-envelope model intended to prompt a more rigorous one.

Monthly orders blocked
650
screen-reader / keyboard users abandoning
Monthly revenue forgone
$78,000
at the AOV you provided
Annualized revenue at risk
$936,000
linear projection, no growth assumed

Methodology. WebAIM and BOIA estimates place active screen-reader use at roughly 1–3% of US web visitors; with broader keyboard-only / motor-impairment users included the figure rises. The 65% blocking rate is the upper end of the WebAIM Million’s 2024 measurement of how often a homepage scan returns at least one blocking barrier (95.9%); checkout barriers are typically narrower in scope. Use your own data where you have it. This model excludes litigation exposure, brand cost, and the value of customers lost permanently after a failed checkout – all of which compound the figures shown.

What an accessible checkout looks like, by contrast

The compare grid below pairs the failure modes most-cited in the dataset against the engineering pattern that resolves each. None of the right-hand patterns are speculative – every one of them is a documented WCAG 2.2 AA technique.

What plaintiffs filed against

  • “Add to Cart” toast appears visually with no role="status" region; assistive tech is not informed
  • CVC input has placeholder text only – no programmatic <label>
  • Address-confirmation modal opens, but focus stays on the previous “Continue” button
  • Inline validation appears in red text below the field; screen reader does not announce it
  • PayPal / Apple Pay buttons rendered as <div> with click handler; no keyboard event listener
  • Failed submit reloads the page and clears the form; user begins again from name and email

What an accessible checkout does

  • “Item added” announced via aria-live="polite" region or role="status"
  • Every input wrapped in a programmatically associated <label> – placeholder is not a label
  • Modal opens, focus moves to dialog heading, focus is trapped, ESC restores prior focus
  • Errors announced via aria-describedby and the field receives aria-invalid="true"
  • Payment buttons are real <button> elements with a visible focus outline ≥ 2px
  • Errors return inline; previously valid fields remain populated; no whole-page reset

The thirteen-step remediation checklist

Drawn from the citation-density patterns in the dataset, the items below are sequenced in descending order of how often each appears in checkout-stage filings. Working top to bottom of this list addresses the great majority of allegations a serial-plaintiff complaint will plead.

Litigation-exposure remediation, ordered by citation frequency

  1. Announce add-to-cart status. Add a visually-hidden role="status" live region; populate it with “Item added – N items in cart” on every successful add.
  2. Label every input field programmatically. Run your checkout against an axe-core or WAVE scan; resolve every label-missing rule. Placeholders are never labels.
  3. Announce coupon and promo errors. Tie error <span> elements to the input via aria-describedby; add aria-invalid="true" on failed validation.
  4. Move focus into modals. When a confirmation dialog opens, set focus on the heading or the first interactive element. On close, restore focus to the trigger.
  5. Trap focus within active modals. Within an open dialog, Tab and Shift+Tab cycle within the dialog; Esc closes it.
  6. Make payment buttons real buttons. Replace any <div onclick> wrappers around PayPal, Apple Pay, Google Pay, and “Place Order” with <button> elements. Add visible focus styles ≥ 2px.
  7. Mark required fields semantically. Add aria-required="true" and a visible “Required” indicator. Group related required fields with <fieldset>.
  8. Preserve form state on validation failure. Errors should not clear correctly-filled fields. Return inline; focus the first invalid input.
  9. Announce success states. “Order placed” and “Discount applied” must reach assistive tech via the same role="status" mechanism as add-to-cart.
  10. Use accessible CAPTCHA. If you must use one, audio fallback and reCAPTCHA’s a11y mode are the minimum. Better: replace with invisible / behavioral verification.
  11. Make step indicators meaningful. If your checkout has steps, expose them as a <nav aria-label="Checkout progress"> with a <ol> and aria-current="step".
  12. Test with a real screen reader. Run the entire checkout end-to-end with NVDA + Firefox or VoiceOver + Safari. Automated scans miss roughly half of barriers your users will hit.
  13. Fix at the design-system level. Most checkout failures originate in shared components (Modal, Input, Toast). Fixing the component once propagates the fix to every checkout that consumes it; fixing the page once does not.
A pattern worth internalizing

The dataset’s checkout-stage barriers cluster in five components: the toast, the modal, the input, the error message, and the submit button. If those five components are tested with a screen reader, in isolation, before they ever ship to a checkout, the entire body of allegations in the corpus shrinks to a long tail. The leverage is at the design-system level. The litigation, unfortunately, is at the page level – and arrives by certified mail.

Closing – the engineering question, restated

The thesis of this article – that checkout is the most-litigated surface on the internet – does not depend on the volume of filings, although the volume is striking. It depends on the structure of the user journey. Of all the surfaces on a commercial website, checkout is the one whose failure most precisely matches the legal definition of a denial of service, the one whose damages most cleanly translate into a complaint, and the one whose bugs are most consistent across defendants. None of those facts will change in 2027. What can change is the engineering decision that produces them.

The 4,050 issues this article catalogues are not, on inspection, mysterious. They are the same five or six failures shipping out of the same five or six components. The most efficient remediation a retailer can perform is not on a checkout page; it is on the design system that builds the checkout page. Fix the toast, the modal, the input, the error message, and the submit button – once, in the component library – and the dataset behind this article slims by something like an order of magnitude. The plaintiff bar will move on to a different surface. Your customers will not.

FILED · ANALYZED · FILED AGAIN

Sources & methodology

Federal civil-case metadata is extracted from PACER (Public Access to Court Electronic Records) and covers 8,788 web-accessibility cases filed in US district courts between January 2007 and April 2026, identified by ADA Title III claim codes and search-string filtering on the term “website”. Issue-level analysis is performed against an OCR-and-NLP extract of the same filings, yielding 81,509 distinct accessibility issue mentions categorized into 28 surface taxonomies.

WCAG references are to WCAG 2.1 (the most-cited standard in private-sector US settlement agreements) and WCAG 2.2 (the latest published recommendation as of October 2023, ratified December 2024). Where filings cite the EAA, EN 301 549, or DOJ Title II Final Rule (April 2024), criteria are normalized to their WCAG 2.1 AA equivalent.

Plaintiff names are redacted from this article. All complainants are real and their cases are matters of public record on PACER. The aggregation pattern is presented for analytical purposes; the original docket entries are publicly searchable for any reader who wishes to verify a specific filing.

The exposure calculator in §11 is illustrative. WebAIM’s screen-reader user surveys (2014–2024) and the WebAIM Million’s annual home-page audit are the principal industry baselines for visitor-share and barrier-frequency estimates. Adjust the calculator’s defaults to your own analytics where you have them.

Citation: AIOPSGROUP Accessibility Intelligence (2026). E-commerce Checkout: The Most Litigated Surface on the Internet. Issue 04:12.