2026 DOJ Rule: Why WCAG vs ADA Now Means WCAG 2.1 AA for U.S. Teams

In the United States, the ADA is the civil-rights law and WCAG is the technical standard courts and regulators commonly use to measure website and app accessibility. The ADA doesn’t spell out pixel-level rules; WCAG does. When the Department of Justice or a federal court needs a yardstick for “accessible enough,” they reach for WCAG, usually Level AA. Treat WCAG 2.1 AA as your working baseline and you’re aligned with how enforcement actually happens.

---

TL;DR:

• Rely on WCAG 2.1 AA as the practical standard for legal compliance, since courts and the DOJ unofficially accept it as the de facto measure.
• Automated scans alone are insufficient; organizations must combine them with manual testing, assistive-technology user testing, and documented remediation efforts.
• The March 2024 DOJ rule mandates that all state and local government websites and apps meet WCAG 2.1 AA, with phased deadlines based on jurisdiction size.
• Private businesses are increasingly held accountable to WCAG AA standards through litigation and government actions, making compliance essential regardless of direct regulation.
• Live captioning tools like Live Caption AI can support WCAG compliance when integrated into a broader accessibility program, but text accuracy and documentation remain crucial.

---

Table of Contents

• WCAG vs ADA: How These Two Frameworks Actually Differ
• How Courts and the DOJ Actually Use WCAG in ADA Cases
• WCAG Levels Explained: Which Version and Level Actually Matter
• Testing and Documenting WCAG Compliance the Right Way
• The DOJ’s 2024 Title II Rule: What Government Entities Must Do
• What Private Businesses Get Wrong About WCAG and ADA Requirements
• Where Live Caption AI Fits Into Your Captioning Strategy
• Getting Started: Where U.S. Teams Should Focus First
• Sources

WCAG vs ADA: How These Two Frameworks Actually Differ

The confusion starts because people treat “ADA compliant” and “WCAG conformant” as interchangeable. They aren’t, and the gap between them explains most of the bad advice floating around procurement contracts and vendor pitches.

The Americans with Disabilities Act is a federal civil-rights statute passed in 1990, long before responsive design or mobile apps existed. Title II covers state and local government services, including their websites and apps. Title III covers “public accommodations,” a category courts have increasingly stretched to include commercial websites, e-commerce platforms, and online booking systems. Neither title mentions color contrast ratios or focus indicators. The ADA sets the legal obligation not to discriminate against people with disabilities; it never defines the technical means of avoiding that discrimination.

WCAG fills that gap. The Web Content Accessibility Guidelines come from the World Wide Web Consortium, the international body that also standardizes HTML and CSS. WCAG organizes its requirements around four principles known as POUR: content must be Perceivable, Operable, Understandable, and Robust. Under that framework sit dozens of specific success criteria, each assigned to one of three conformance levels, A, AA, or AAA, roughly ordered from baseline to aspirational.

Section 508 adds a third layer specific to federal agencies and contractors. It’s a separate statute (an amendment to the Rehabilitation Act) that governs federal procurement and technology, and it has formally adopted WCAG 2.0 Level AA as its technical benchmark, with Section508 providing implementation tools and training for agencies and vendors navigating that overlap.

In practice, digital accessibility requirements tend to cluster around a familiar set of items:

• Captions and transcripts for audio and video content
• Full keyboard operability, with no mouse-only interactions
• Descriptive alt text for meaningful images
• Sufficient color contrast between text and background
• Clear form labels and error messages
• Logical heading structure and screen-reader-friendly markup

None of these appear in the ADA’s statutory text. All of them appear in WCAG. That’s the entire relationship in one sentence: the ADA tells you discrimination is illegal, and WCAG tells you what non-discriminatory code looks like.

How Courts and the DOJ Actually Use WCAG in ADA Cases

Here’s where legal teams get tripped up: WCAG has never been formally adopted as the ADA’s legal text for private businesses, yet it dominates enforcement anyway. Courts, plaintiffs’ attorneys, and the DOJ itself have converged on WCAG 2.1 AA as the de facto measuring stick, even in cases where no regulation explicitly requires it.

Settlement agreements are the clearest evidence of this pattern. When the DOJ or a private plaintiff settles an ADA web accessibility claim, the resulting consent decree almost always specifies WCAG 2.1 AA (increasingly 2.2 AA) as the remediation target, with a compliance timeline and third-party audit requirement. Judges cite WCAG in opinions not because a statute compels them to, but because it’s the only widely accepted technical standard available, and courts need something concrete to measure against.

The DOJ’s own guidance confirms this pattern rather than inventing it. Its web accessibility guidance points businesses toward WCAG as the standard it references when evaluating whether a website meets Title II or Title III obligations, even in contexts where WCAG hasn’t been codified into a specific regulation for private entities.

That reliance creates real leverage for organizations that can show good-faith effort. If your organization faces a demand letter or lawsuit, three categories of evidence carry weight in negotiations and in court:

1. Accessibility audit reports dated and scoped, showing you evaluated your site against a named WCAG version and level.
2. Remediation logs documenting what was fixed, when, and by whom, ideally tied back to specific success criteria.
3. User testing records involving people who actually use assistive technology, not just automated scan results.

The limits matter just as much as the leverage. ADA liability is broader than a single technical pass or fail. A site can score well on an automated WCAG scan and still trigger a viable claim if a screen-reader user genuinely cannot complete a core task, like booking an appointment or paying a bill. Courts look at functional outcomes for real users, not just checklist completion.

Pro Tip: Keep a dated accessibility statement on your site describing your target WCAG version, your testing cadence, and how users can report barriers. That single document does more to demonstrate good faith than any automated scan certificate, and plaintiffs’ attorneys notice its absence.

Organizations should maintain a standing file of policy documents, vendor accessibility contracts, training records, and audit history. When a claim arrives, that file is the difference between a fast settlement and a prolonged discovery fight.

WCAG Levels Explained: Which Version and Level Actually Matter

WCAG has gone through three major iterations, and the version numbers confuse more people than the levels do. WCAG 2.0 shipped in 2008 and became the baseline referenced by most early regulations, including the original Section 508 refresh. WCAG 2.1 added criteria for mobile accessibility, low vision, and cognitive disabilities. WCAG 2.2, the current stable version, added further criteria around focus visibility and drag interactions.

Critically, each version is backward-compatible: a site that meets WCAG 2.2 AA also meets 2.1 AA and 2.0 AA, because newer versions only add success criteria, never remove them. The W3C recommends adopting the latest stable version specifically because that backward compatibility future-proofs your compliance work instead of locking you into an aging standard.

Within any version, three conformance levels apply:

• Level A: the minimum, covering barriers so severe that some users simply cannot access content at all.
• Level AA: the standard most regulations and settlements target, addressing common barriers without requiring exhaustive accommodation.
• Level AAA: the highest level, often impractical to apply site-wide (some criteria conflict with real-world content needs) but useful for critical flows.

Level AA has become the practical consensus target because it’s what the DOJ, most settlements, and Section 508 all converge on. Aiming for AAA site-wide is rarely realistic and rarely required; aiming below AA leaves obvious gaps.

Among AA criteria, a handful come up constantly in audits and litigation. Captioning falls under Success Criterion 1.2.4, which requires synchronized captions for live audio content, a criterion that matters enormously for churches, conferences, and webinars streaming in real time. Keyboard accessibility, alt text for informative images, a 4.5:1 contrast ratio for normal text, and correct ARIA labeling round out the criteria that generate the most audit findings and the most legal claims.

One industry review found that a striking share of tested sites still fail basic WCAG 2.2 AA checks even after remediation efforts, which underscores how much manual attention these criteria actually require beyond a one-time automated fix, according to an industry analysis of accessibility compliance rates.

Testing and Documenting WCAG Compliance the Right Way

Automated scanners catch maybe a third of real accessibility barriers. They’re fast and cheap, and they’re also the reason so many organizations think they’re compliant when they aren’t. A tool can confirm that an image has an alt attribute; it cannot confirm that the alt text actually describes the image usefully. That gap is why every defensible accessibility program layers three methods rather than relying on one.

A workable testing workflow looks like this:

1. Scope the properties and user flows that matter most, starting with anything tied to a core transaction (checkout, appointment booking, account login).
2. Sample representative pages rather than attempting to test every URL on day one.
3. Test using automated scans first, then manual keyboard and screen-reader walkthroughs, then assistive-technology user testing with people who rely on that technology daily.
4. Remediate findings, prioritized by severity and how many users a given barrier blocks.
5. Document every step, from initial audit scope to final fix, with dates and owners attached.
6. Monitor continuously, since new content and new features reintroduce barriers constantly.

The artifacts that come out of this process, an audit report, a remediation tracker, a public accessibility statement, and user-test logs, are what regulators and plaintiffs’ attorneys ask for first. A screenshot of a passing automated scan is not one of them.

Pro Tip: Automated tools reliably miss context-dependent problems: whether an alt description actually conveys meaning, whether a modal traps keyboard focus, whether a live caption feed lags enough to break comprehension. Budget for at least one round of assistive-technology user testing before calling any major flow “done.”

For any organization producing live or recorded video, caption quality deserves specific manual review rather than a checkbox. Automated captioning services vary wildly in accuracy on technical or specialized vocabulary, and a technically-present-but-garbled caption track can still fail a functional accessibility review even though a scanner would mark the criterion as met.

The DOJ’s 2024 Title II Rule: What Government Entities Must Do

In April 2024, the DOJ finalized a rule that removed the ambiguity Title II had lived with for over three decades: state and local governments must now meet WCAG 2.1 Level AA for their web content and mobile applications, full stop. This is the first time WCAG has been directly codified into a Title II regulation rather than treated as a persuasive benchmark.

The rule’s key provisions:

• Standard: WCAG 2.1 Level AA, applied to both web content and mobile apps operated by or on behalf of state and local governments.
• Timeline: phased by jurisdiction population, with larger jurisdictions facing an earlier deadline than smaller ones, generally within a few years of the rule’s publication date, per the Federal Register notice.
• Equivalent facilitation: entities can use an alternative approach if it provides equal or greater accessibility than strict WCAG conformance, but they need documentation and testing to back that claim up if challenged.

The [SBA Office of Advocacy’s summary](https://advocacy.sba.gov/2024/04/25/justice-department-finalizes-rule-requiring-state-and-local-governments-to-make-their websites-accessible/) of the rule notes that the phased timeline gives smaller municipalities more runway, but it doesn’t lower the bar. Every covered entity eventually lands at the same WCAG 2.1 AA standard.

Vendors serving government clients feel this rule as much as the agencies do. Procurement contracts are already shifting to require WCAG 2.1 AA conformance documentation upfront, and any company selling software, streaming, or event technology into the government sector should expect accessibility clauses to become standard rather than optional.

What Private Businesses Get Wrong About WCAG and ADA Requirements

The DOJ’s 2024 rule only binds state and local governments directly, but private businesses shouldn’t read that as a pass. Courts already apply the same WCAG AA benchmark to Title III public accommodations claims, and the rule’s existence makes that benchmark harder for a defendant to argue against in court.

Three myths cause the most expensive mistakes. First, an automated scanner returning a clean report doesn’t mean a site is accessible; it means the scanner didn’t catch the failures a person would. Second, accessibility overlay widgets that promise instant compliance through a script tag routinely fail to fix underlying code issues and have themselves become the subject of lawsuits. Third, small business size doesn’t create blanket ADA exemption. Title III’s public accommodation reach doesn’t scale down neatly with employee count.

A workable risk mitigation checklist looks like this:

• Adopt a written accessibility policy naming WCAG 2.1 AA (or 2.2 AA) as your target
• Schedule recurring audits rather than a one-time assessment
• Maintain an active remediation plan with owners and deadlines
• Train content teams on captioning, alt text, and heading structure
• Add accessibility conformance clauses to vendor and platform contracts

Pro Tip: Write down the date you adopted your accessibility policy and every remediation deadline you set, even informally. In litigation, a documented timeline showing good-faith progress carries more legal weight than a perfect score achieved only after a demand letter arrives.

Where Live Caption AI Fits Into Your Captioning Strategy

Captions sit squarely inside WCAG’s technical requirements, specifically the success criteria covering synchronized captions for live and recorded audio, and getting them right takes more than a checkbox. Live Caption AI provides real-time captioning that turns any phone into a caption receiver through a simple QR code, no dedicated hardware or stenographer required, across 29 languages, translating from one source language to one target language per session. Sessions export to TXT, SRT, JSON, or PDF, audio is never stored, and transcripts stay owner-only. The Professional plan runs $19.99 a month. Whether captions from any tool actually satisfy WCAG’s criteria for your event or platform depends on the accuracy of the output and how the content owner integrates and documents it, but a reliable live-captioning workflow is one practical piece of a broader accessibility effort. If you run church services, conferences, or professional events that need real-time captions, see how Live Caption AI works and start a trial for your next live session.

Getting Started: Where U.S. Teams Should Focus First

Start with WCAG 2.1 AA on your highest-traffic, highest-risk flows, checkout, account access, appointment booking, not your entire site at once. Layer in manual and user testing early. Assign a named owner and a remediation deadline. Document everything, because the paper trail is what protects you later.

— Ryan

Sources

• Web Content Accessibility Guidelines (WCAG) 2.2 — W3C
• Nondiscrimination on the basis of disability: Accessibility of web information and services of state and local government entities — Federal Register

Recommended

• Web Accessibility Statement Examples for Live Events
• Accessibility for Schools: A Practical Compliance Roadmap