A recurring defense argument in ADA Title III website lawsuits is that the plaintiff never actually intended to buy anything, book anything, or use the service in question. They visited the site, found an accessibility barrier, and filed suit, sometimes as part of a pattern of similar filings against other businesses. Defendants call this a "tester" plaintiff and argue they lack the real, personal stake in the outcome that federal courts require for Article III standing. Plaintiffs' attorneys argue testers serve exactly the enforcement role Congress intended when it modeled the ADA partly on fair housing testing schemes that courts have long upheld. In late 2023, the Supreme Court had a chance to resolve which side is right nationally. It did not.
Acheson Hotels, LLC v. Laufer reached the Supreme Court specifically on the question of whether a self-appointed ADA tester, someone who visited a hotel's website to check for disability accommodation information despite having no intention of ever staying there, had Article III standing to sue. The Court heard the case and issued a decision in December 2023, but not on the merits of the standing question. The plaintiff's original attorney had been suspended from practicing law during the litigation over unrelated misconduct, and she voluntarily dismissed many of her pending suits, including this one. Because there was no longer a live dispute for the underlying claim on her side, the Supreme Court dismissed the case as moot in a 9-0 decision. It vacated the lower court's ruling. It did not decide whether tester plaintiffs have standing.
The Fact: In Acheson Hotels, LLC v. Laufer, the Supreme Court dismissed the case as moot in December 2023 without deciding the ADA tester standing question on its merits, and the federal circuit split on the issue remains unresolved. (Source: Supreme Court of the United States, Acheson Hotels, LLC v. Laufer, decided Dec. 5, 2023)
What the Circuit Split Actually Looks Like
Even before Laufer reached the Supreme Court, federal appellate circuits had already split on tester standing, and that split persisted after the Court declined to resolve it. Some circuits have been more receptive to tester plaintiffs, reasoning that testing is a legitimate and legally recognized method of uncovering discrimination, consistent with how courts have long treated fair housing testers under a separate but analogous legal framework. Other circuits have taken a stricter view, requiring a plaintiff to show a concrete, personal intent to actually use the business or its services, not just an abstract interest in confirming whether it complies with the law. Justice Thomas, in a concurrence in Laufer that was not joined by a majority of the Court, wrote that he would have found the plaintiff lacked standing specifically because she had disclaimed any intent to visit the hotel in question, but that view did not become binding law nationally.
The practical result is that whether a tester plaintiff can sue your organization for a website accessibility barrier may currently depend more on which federal circuit the case is filed in than on any single, settled national rule. That is an unusually unstable legal environment to be operating a public-facing website in, and it is likely to stay unstable until either Congress acts or another case reaches the Supreme Court with a live, non-moot dispute that forces a ruling on the merits.
Why This Uncertainty Is Not Good News for Defendants
It is tempting to read an unresolved legal question as a source of leverage, an opening to argue standing in every case and hope for a favorable circuit. In practice, this uncertainty cuts against organizations more than it helps them, for a simple reason: plaintiffs' attorneys can choose where to file, within jurisdictional limits, and have every incentive to file in circuits that have already recognized tester standing. A business operating nationally, reachable from any state, cannot assume it will get the benefit of a favorable circuit's rule. It has to assume the opposite: that a plaintiff will select the jurisdiction most likely to allow the case to proceed on standing grounds, leaving the actual accessibility of the website, not the standing question, as the real point of dispute.
What Actually Reduces Exposure Here
Standing arguments are a defense to a lawsuit that has already been filed. They are not a substitute for the underlying fix, and they are an increasingly unreliable one given the circuit split described above. The far more durable position is not having the accessibility barrier a tester would find in the first place. Our piece on why 'we'll fix it later' is how the lawsuit starts covers the pattern of organizations that know about a specific barrier and delay remediation, which is exactly the fact pattern that removes any standing argument as a meaningful defense, since a documented, known, unfixed barrier is discoverable regardless of who eventually finds and reports it.
Organizations sometimes treat legal uncertainty like the tester standing split as a reason to wait and see how the law develops before investing in remediation. Given how unresolved and genuinely unpredictable this specific question remains, that is close to the opposite of the rational response. The safest position, procedurally, is one where the underlying barrier does not exist, which makes the standing question moot in the way that actually matters, not the technical mootness that ended Laufer without answering it.
If your organization wants a clear picture of where real accessibility barriers exist on your site, independent of any standing argument that may or may not hold up in the specific court a future plaintiff chooses, our team can run a full audit. Reach us at experts@wcag.world, or review the Supreme Court's decision in Acheson Hotels, LLC v. Laufer and ADA.gov's web guidance directly for the primary sources behind this.
A practical review loop
Start with the task a person needs to complete, not with the score produced by a single automated scan. Write down the entry point, the expected focus order, the announcement a screen reader should receive, and the recovery path when something goes wrong. Then repeat that task with a keyboard and at least one assistive technology setup. This turns a vague accessibility concern into an observable acceptance test.
The useful evidence is specific. Capture the URL, the control label, the keystrokes, the browser state, and the expected result. Separate a defect from a design choice, and separate both from a limitation in the test environment. Give the product owner a short reproduction and a clear severity rationale. A developer can fix a named interaction. Nobody can reliably fix a general instruction to make a page more accessible.
Finally, put the check into the delivery process. Add the scenario to a pull request checklist, retest it after JavaScript changes, and keep a small set of representative pages available for regression testing. That routine protects the people who depend on the workflow and gives the team a defensible record of what was tested, when it was tested, and what happened.
For the next review, use these related resources: we audited 50 accessible websites 47 failed, section 508 rejection kills federal deal before it starts.
For the next review, use these related resources: request the relevant WCAG review.