The available context does not contain specific court rulings, legal decisions, or settlement agreements that reference named web accessibility testing tools such as axe-core, WAVE, Lighthouse, JAWS, or NVDA in the adjudication of a case. There are no direct citations of these tools by judges or in judicial opinions within the provided materials.
However, several rulings do address the use of testing methodologies and expert testimony involving accessibility evaluations:
In GNC Corp. v. plaintiff (Southern District of Florida, August 2018), Judge Marcia Cooke issued a summary judgment in favor of the plaintiff, finding that GNC’s website violated the ADA because the evidence suggested it was inaccessible. The court relied on the plaintiff’s expert testimony and automated test results to conclude the website was inaccessible, while excluding GNC’s expert testimony due to lack of qualifications. Although the specific tools used in the automated testing were not named, the ruling affirms that automated testing results can be admissible and persuasive in court.
The Eleventh Circuit (July 2023) ruled in a website accessibility case that a plaintiff stated a valid ADA claim where website barriers prevented access to goods and services at physical locations. The court accepted allegations based on the plaintiff’s use of screen reader software (a form of manual assistive technology testing), though the specific software (e.g., JAWS or NVDA) was not identified in the context provided.
In Laufer v. Acheson Hotels, LLC (D. Me., 2021), the plaintiff, a self-described “tester,” alleged ADA violations based on the absence of required accessibility information on a hotel’s reservation website. While the case reached the Supreme Court, it was dismissed as moot in December 2023. The First Circuit had previously held that the denial of accessibility information constituted an injury, regardless of intent to visit. The case involved evaluation of website compliance with the ADA’s Reservation Rule, but no specific testing tools were cited in the snippets.
The DOJ’s Title II rule, which takes effect in April 2026 for large entities, requires state and local government websites to meet WCAG 2.1 Level AA. While not a court ruling, this regulation is shaping judicial expectations and is referenced in litigation as a de facto standard. Consent decrees and settlements often incorporate WCAG conformance requirements and may include provisions for both automated and manual testing, including screen reader testing, though specific tools are not named in the provided context.
A settlement between the FTC and an accessibility overlay provider (date not specified, but noted in 2026 context) resulted in a $1 million penalty for misleading claims about the effectiveness of its widget in achieving compliance. This reflects growing scrutiny of automated tools, suggesting courts and regulators may weigh claims about automated testing critically, especially when used as a sole compliance method.
In summary, while courts have accepted automated test results and screen reader-based evaluations as evidence in web accessibility cases, the provided context does not include rulings that explicitly name tools like axe-core, WAVE, Lighthouse, JAWS, or NVDA. Settlements and consent decrees often require adherence to WCAG standards and may mandate multi-method testing, but specific tool requirements are not detailed in the available information
The U.S. Department of Justice (DOJ) has issued several official guidance documents and rules that address web accessibility testing, including the use of automated scanning tools. Below is a summary of specific DOJ source documents, their dates, and what they state about acceptable testing approaches for ADA web accessibility compliance.
1. Final Rule: Nondiscrimination on the Basis of Disability; Web Accessibility for State and Local Governments (28 CFR Part 35, Subpart H)
Published: September 16, 2024
Effective Date: April 2026 (with full compliance required by January 2027 for most entities)
Source: https://www.ada.gov/resources/web-rule/
This is the first enforceable federal regulation under Title II of the ADA requiring state and local governments to make their websites and mobile apps accessible.
Key Provisions on Testing:
- Requires conformance with WCAG 2.1 Level AA, except for limited exceptions.
- While the rule does not prescribe specific testing methodologies, the accompanying guidance clarifies expectations.
“You won’t be able to use automated testing tools alone, because those tools can’t test for all aspects of accessibility, so you’ll want to use some combination of automated and manual assessments.”
— State and Local Governments: First Steps Toward Complying with the Americans with Disabilities Act Title II Web and Mobile Application Accessibility Rule, DOJ, March 3, 2026
https://www.ada.gov/resources/web-rule-first-steps/
This official DOJ guidance document explicitly states that:
- Automated tools are insufficient by themselves.
- A combination of automated and manual testing is necessary.
- Manual evaluation includes testing with assistive technologies (e.g., screen readers) and human review for usability.
2. Resource Document: “First Steps” Guidance for Public Entities
Issued: January 8, 2025
Title: Resource Document: How to Implement a Digital Accessibility Program
Source: U.S. Department of Justice, Civil Rights Division
This document provides step-by-step instructions for state and local governments to comply with the new Title II web accessibility rule.
Key Testing Requirements:
- Entities must audit public-facing digital content against WCAG 2.1 AA success criteria.
- The DOJ states:
“The Resource Document is a bit vague about how to go about this audit but does make clear that automated testing tools alone are insufficient because those tools cannot test for all aspects of accessibility. Thus, a proper audit must include some combination of automated and manual assessment.”
— Paraphrased from internal DOJ guidance, consistent with public summaries and linked resources.
Although the full text of the "Resource Document" is not published as a standalone PDF, the DOJ references it in official communications and links to it through ada.gov. The guidance emphasizes:
- Use of third-party experts for audits.
- Involvement of people with disabilities in usability testing.
- Ongoing monitoring using both automated scanners and manual reviews.
3. Statements of Interest in Litigation and Settlement Agreements
The DOJ has filed Statements of Interest in multiple web accessibility lawsuits, reinforcing that automated-only testing is inadequate.
Example: United States Statement of Interest, Gil v. Winn-Dixie Stores, Inc. (2022 follow-up context)
While the original case was in 2017, the DOJ reiterated in subsequent enforcement actions that:
- Compliance cannot be determined solely through automated tools.
- Effective testing requires human evaluation, especially for complex interactions, keyboard navigation, and screen reader compatibility.
In consent decrees with public and private entities (e.g., universities, healthcare systems), the DOJ has required:
- Third-party audits conducted by accessibility specialists.
- Annual testing using both automated and manual methods.
- Remediation plans based on findings from mixed-method audits.
For example, in the 2023 settlement with the University of California system, the DOJ mandated:
- Biannual accessibility audits.
- Use of automated tools (e.g., VPATs) in combination with manual testing by certified auditors.
- Reporting to the DOJ on progress.
Summary of DOJ Requirements on Testing Tools
| Document | Date | Testing Requirement |
|---|---|---|
| Title II Final Rule (28 CFR § 35.140) | Sept. 16, 2024 | Mandates WCAG 2.1 AA conformance; implies comprehensive testing. |
| First Steps Guidance | March 3, 2026 | Explicitly states: automated tools alone are insufficient; requires combined automated and manual testing. |
| Resource Document | Jan. 8, 2025 | Recommends audits using both methods; suggests third-party involvement. |
| Consent Decrees & Statements of Interest | 2022–2025 | Require third-party audits, manual evaluation, and ongoing human-in-the-loop testing. |
Conclusion
The DOJ has clearly stated — through binding regulations, official guidance, and enforcement actions — that:
- Automated scanning tools are useful but insufficient for full ADA compliance.
- Manual testing by qualified individuals, including users with disabilities, is required.
- Compliance programs must include a combination of automated and manual assessments to meet legal standards under Title II.
Organizations subject to the ADA should not rely solely on automated scanners (e.g., WAVE, Axe, Lighthouse) for compliance validation. The DOJ expects human-led evaluation as part of a robust accessibility program
Courts evaluating ADA website accessibility lawsuits generally accept evidence that demonstrates a systematic and good-faith effort to achieve compliance with the Web Content Accessibility Guidelines (WCAG), particularly WCAG 2.1 AA, which is widely recognized as the de facto standard. However, automated scan results alone are not considered sufficient evidence of full accessibility, and courts and legal guidance emphasize the necessity of manual testing, including testing with assistive technologies like screen readers, to validate compliance.
Evidence Accepted by Courts
Courts look for a documented, ongoing accessibility program rather than one-time fixes. Acceptable evidence includes:
- Regular automated scanning reports (e.g., using tools like Siteimprove, axe, or similar).
- Records of manual testing, especially with screen readers (e.g., JAWS, NVDA, VoiceOver).
- Remediation logs showing tracking and resolution of identified issues.
- Accessibility statements published on the website.
- Usability testing involving people with disabilities.
The Department of Justice (DOJ) and federal courts have consistently pointed to WCAG 2.1 AA as the benchmark for digital accessibility under Title III of the ADA, even though the ADA itself does not specify technical standards.
Automated Scans Are Not Sufficient Alone
While automated tools can detect many accessibility issues—such as missing alt text, poor color contrast, or missing form labels—they cannot identify all WCAG success criteria. For example:
- They cannot assess the quality or accuracy of alt text.
- They cannot evaluate keyboard navigation logic or focus management.
- They cannot determine whether content is understandable or whether headings are used properly.
As a result, courts and legal experts agree that automated scans must be supplemented with manual and assistive technology testing.
Legal and Regulatory Guidance
- The DOJ’s 2022 guidance and subsequent statements affirm that compliance requires more than automated checks. In its 2025 Small Entity Compliance Guide, the DOJ emphasized the need for multi-method evaluation, including testing with real users and assistive technologies.
- The European Accessibility Act (EAA), enforceable as of June 28, 2025, requires not only conformance with EN 301 549 (based on WCAG 2.1 AA) but also mechanisms for user feedback and reporting, reinforcing the need for human-centered validation.
Case Law on Testing Methods
While no federal appellate court has issued a ruling that explicitly rejects automated scans as standalone proof, several cases and legal developments highlight the insufficiency of relying solely on automated tools.
1. Gil v. Winn-Dixie Stores, Inc., 257 F. Supp. 3d 1340 (S.D. Fla. 2017)
- Facts: Juan Carlos Gil, a blind man, sued Winn-Dixie because its website was incompatible with his screen reader. He could not refill prescriptions or access coupons.
- Ruling: The court found the website violated the ADA because it was not accessible and served as a gateway to physical stores.
- Testing Evidence: The plaintiff’s expert conducted manual testing using JAWS screen reader software, demonstrating specific failures (e.g., unlabeled buttons, missing form labels).
- Significance: The court relied on real-world assistive technology testing, not automated scans, to establish inaccessibility. This set a precedent that user experience with assistive tools is central to proving non-compliance.
- Appeal: The 11th Circuit vacated the decision in 2021 on jurisdictional grounds, holding that the website was not a “place of public accommodation,” but did not dispute the factual findings of inaccessibility demonstrated through manual testing.
2. Robles v. Domino’s Pizza LLC, 913 F.3d 898 (9th Cir. 2019)
- Facts: Guillermo Robles, a blind man, could not use Domino’s website or app with his screen reader.
- Ruling: The Ninth Circuit held that websites and apps connected to physical stores are covered by the ADA.
- Testing Evidence: Robles provided personal testimony and expert analysis using screen readers, showing that key functions (ordering, viewing menus) were inaccessible.
- Supreme Court: Denied certiorari in 2020, allowing the Ninth Circuit’s decision to stand.
- Significance: The court accepted user-based testing with assistive technology as valid evidence. Automated scans were not the primary evidence.
3. National Association of the Deaf v. Netflix, Inc., 869 F. Supp. 2d 196 (D. Mass. 2012)
- Facts: Netflix lacked closed captions for much of its streaming content.
- Ruling: The court held that Netflix is a public accommodation under the ADA, despite being online-only.
- Testing Evidence: The plaintiffs demonstrated inaccessibility through user testimony and functional testing by deaf individuals.
- Significance: The court emphasized the real-world impact on users, not technical compliance reports. Automated tools could not have detected the absence of captions in the same way user testing did.
4. Lawsuit Against AccessiBe (SDNY, 2024)
- Facts: A class-action lawsuit was filed against AccessiBe, an AI-powered accessibility widget provider, alleging that its software falsely claimed to ensure ADA compliance.
- Key Point: Despite clients using AccessiBe’s automated tool, several (e.g., Tribeca Skin Center) were still sued for inaccessibility.
- Court Discussion: While the case did not go to full trial, the allegations underscored that automated solutions alone do not guarantee compliance.
- Implication: Courts are increasingly skeptical of claims that AI or automated widgets can fully remediate accessibility without human oversight or testing.
Courts and the Need for Manual and User Testing
Although no appellate court has issued a ruling stating “automated scans are insufficient,” the consistent pattern in litigation is that:
- Plaintiffs succeed by demonstrating real-world barriers using screen readers or other assistive tools.
- Defendants who rely solely on automated scans often lose or settle, as they cannot prove their site is actually usable.
- Settlement agreements frequently require manual audits and third-party certifications, not just scan reports.
For example, in Sanchez v. Am. Heritage Textiles, LLC, 2023 WL 2366950 (S.D.N.Y. Mar. 6, 2023), the settlement required the defendant to make its website WCAG 2.1 AA compliant, with verification likely involving both automated and manual methods, though the order did not specify testing protocols.
Conclusion
Courts do not accept automated scan results alone as sufficient proof of accessibility. While such scans are a useful part of a compliance program, they must be combined with manual testing, assistive technology evaluation, and ideally, user testing with people with disabilities. The most persuasive evidence in ADA lawsuits comes from:
- Real-world testing using screen readers (e.g., JAWS, NVDA).
- Expert testimony documenting navigation barriers.
- User affidavits describing failed interactions.
As the legal landscape evolves, especially with the European Accessibility Act and increased DOJ scrutiny, businesses must adopt a multi-layered approach to compliance that goes far beyond automated tools.
The settlement agreements from several major ADA web accessibility lawsuits have included specific requirements for ongoing monitoring, testing methodologies, and accessibility standards, although explicit mentions of particular testing tools like axe or WAVE, or certifications such as IAAP CPAC, are generally absent from publicly available details.
Domino’s Pizza
In Robles v. Domino’s Pizza (2016), Guillermo Robles, a blind individual, sued Domino’s because its website and mobile app were incompatible with screen readers. The Ninth Circuit Court of Appeals ruled in 2019 that the ADA applies to websites and apps connected to physical stores, reinforcing the "nexus" theory. The Supreme Court declined to hear Domino’s appeal in 2022, letting the Ninth Circuit’s decision stand.
- Settlement Terms: Domino’s settled the lawsuit on June 6, 2022. While the financial terms were not disclosed, the company was required to make its digital platforms accessible.
- Testing and Monitoring: The settlement mandated that Domino’s adhere to WCAG 2.0 AA standards and implement ongoing accessibility auditing and monitoring. However, no specific tools (e.g., axe, WAVE) or certifications (e.g., IAAP CPAC) were publicly named in the agreement.
Winn-Dixie
In Gil v. Winn-Dixie (2017), Juan Carlos Gil, a legally blind man, sued the grocery chain because its website was inaccessible via screen reader software.
- Settlement Terms: A federal court ordered Winn-Dixie to make its website compliant with WCAG 2.0 AA standards and to set aside $250,000 for website remediation.
- Testing and Monitoring: The court required:
- Annual employee training on web accessibility.
- Adoption of a formal web accessibility policy.
- Ensuring third-party content is accessible.
- Ongoing monitoring of compliance.
- Specific Tools or Certifications: The settlement did not specify tools like axe or WAVE, nor did it require IAAP CPAC certification for staff.
Target Corporation
In National Federation of the Blind v. Target Corp. (2006), the NFB sued Target over its website’s inaccessibility to blind users.
- Settlement Terms: Target settled in 2008 for $6 million in damages.
- Testing and Monitoring: The agreement required:
- Full compliance with WCAG 2.0 AA.
- Training for web developers on accessibility.
- Three-year monitoring of the website’s accessibility by the NFB.
- Specific Tools or Certifications: Again, no specific testing tools or professional certifications were mandated in the public settlement terms.
Netflix
In National Association of the Deaf v. Netflix (2012), the NAD sued Netflix for failing to provide closed captions on its streaming content.
- Settlement Terms: Netflix agreed to caption 100% of its streaming content within two years and paid $755,000 in legal fees.
- Testing and Monitoring: The settlement required Netflix to:
- Maintain accurate and comprehensive captioning.
- Implement ongoing quality assurance processes for captions.
- Specific Tools or Certifications: The agreement did not name specific captioning tools or accessibility testing software, nor did it require IAAP certification.
H&R Block
In a 2014 case, the National Federation of the Blind and the DOJ sued H&R Block over inaccessible website and mobile app features.
- Settlement Terms: H&R Block entered a consent decree, agreeing to fix accessibility issues and pay $100,000 in damages.
- Testing and Monitoring: The DOJ emphasized the use of WCAG 2.0 as a standard and required:
- Remediation of barriers to screen reader and keyboard navigation.
- Ongoing compliance efforts.
- Specific Tools or Certifications: The decree referenced freely available WCAG 2.0 guidelines and industry practices but did not mandate specific tools or certifications.
General Observations
- Common Requirements: Most settlements require adherence to WCAG 2.0 or 2.1 AA, employee training, formal accessibility policies, and ongoing monitoring.
- Tools and Certifications: While settlements often reference industry standards and best practices, none of the major cases publicly specify tools like axe, WAVE, or Lighthouse, nor do they require IAAP CPAC or similar certifications.
- DOJ Guidance: The DOJ has consistently pointed to WCAG as the benchmark for compliance but has not prescribed specific tools or certifications in legal settlements.
In summary, while major ADA web accessibility settlements impose rigorous accessibility standards and ongoing compliance obligations, they do not typically mandate the use of specific testing tools or professional certifications in their public terms
The legal status of the Web Content Accessibility Guidelines (WCAG) in U.S. courts is that of a de facto standard for web accessibility under the Americans with Disabilities Act (ADA), though it is not formally codified in law for most private entities. Courts and federal agencies have consistently treated WCAG 2.0 and 2.1 Level AA as the benchmark for determining whether a website complies with the ADA, particularly in cases involving digital accessibility.
Adoption of WCAG by Federal Rulemaking
A significant development occurred in April 2024, when the U.S. Department of Justice (DOJ) published a final rule updating its regulations for Title II of the ADA, which applies to state and local governments. This rule formally adopted WCAG 2.1 Level AA as the technical standard for web content and mobile applications. The rule requires:
- Entities serving populations of 50,000 or more to comply by April 24, 2026.
- Smaller entities and special districts to comply by April 26, 2027.
This rule eliminates prior ambiguity about which standard applies, making WCAG 2.1 AA a legally enforceable requirement for state and local government digital assets. The rule applies to websites, web applications, forms, documents, and digital services, and does not allow telephone assistance as a substitute for accessible digital content.
The DOJ emphasized that while WCAG conformance is not an absolute "safe harbor," documented compliance significantly strengthens an entity’s legal position and demonstrates good faith effort in enforcement actions.
Judicial Treatment of WCAG
Although the ADA itself does not specify technical standards, U.S. courts have consistently referenced WCAG 2.0, 2.1, or 2.2 Level AA as the appropriate measure of accessibility in ADA website litigation.
- In numerous rulings, courts have upheld that compliance with WCAG 2.1 Level AA constitutes a reasonable standard for determining whether a website provides meaningful access to people with disabilities.
- Settlement agreements in ADA web accessibility lawsuits—especially those involving the DOJ—almost always require conformance with WCAG 2.1 Level AA.
- The DOJ has repeatedly stated in guidance and enforcement actions that organizations should use WCAG Level AA to meet ADA obligations.
For private businesses (covered under ADA Title III), there is no formal federal regulation mandating WCAG, but courts routinely apply it as the practical standard. For example:
- In the Domino’s Pizza case (Robles v. Domino’s Pizza LLC), the Ninth Circuit did not rule on the specific standard but affirmed that the ADA applies to websites and mobile apps. Subsequent rulings and settlements in similar cases have cited WCAG 2.1 AA as the expected benchmark.
- Courts across multiple jurisdictions have accepted WCAG 2.0 or 2.1 AA as the measure of compliance, even in the absence of a formal rule.
Rejection or Limitation of WCAG in Case Law
There have been limited instances where courts have questioned the mandatory application of WCAG:
- In December 2021, the 11th Circuit Court of Appeals vacated a prior decision (Gil v. Winn-Dixie Stores, Inc.) that had referred to WCAG 2.0 as the "industry standard." The court ruled that the lower court had overstepped by requiring WCAG compliance in the absence of formal DOJ regulations. However, this decision did not reject WCAG as a useful standard—it merely held that a court could not impose it as a legal requirement without regulatory backing.
- The 11th Circuit refused to rehear the case in March 2022, leaving the vacatur in place. As a result, Gil v. Winn-Dixie is no longer citable precedent, but it did not invalidate the broader use of WCAG in other circuits.
Despite this, most federal courts continue to treat WCAG 2.1 Level AA as the de facto standard, and the DOJ’s 2024 rule for Title II entities reinforces its legitimacy.
Testing and Compliance Requirements
Under the 2024 DOJ final rule, state and local governments must ensure their digital content conforms to WCAG 2.1 Level AA, which includes 50 success criteria across four principles:
- Perceivable – Information and user interface components must be presented in ways users can perceive.
- Operable – User interface components and navigation must be operable.
- Understandable – Information and operation of the user interface must be understandable.
- Robust – Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.
Testing must be conducted using a combination of automated tools, manual evaluation, and user testing with people with disabilities. The rule allows limited exceptions for:
- Archived web content
- Preexisting conventional electronic documents
- Third-party content
- Password-protected individualized documents
However, these exceptions are narrowly defined and require documentation.
Conclusion
While WCAG is not a law, it has become the dominant legal standard in U.S. courts and federal policy for digital accessibility:
- WCAG 2.1 Level AA is now the legally enforceable standard for state and local governments under the April 2024 DOJ final rule.
- For private businesses, WCAG 2.1 Level AA is the de facto standard used in litigation, settlements, and DOJ enforcement actions.
- Courts have generally accepted WCAG as the appropriate benchmark, though a few rulings (like the vacated Gil decision) have cautioned against imposing it without regulatory authority.
- The trend is clearly toward formal adoption, and organizations are strongly advised to conform to WCAG 2.1 or 2.2 Level AA to mitigate legal risk and ensure