Why the ADA Web Rule Locks In the 2018 WCAG 2.1 Text

The Department of Justice’s Title II web-accessibility rule (28 CFR part 35, subpart H) requires conformance to one specific, dated document: the W3C Recommendation of WCAG 2.1 published June 5, 2018. That is not the page most readers reach by following W3C’s own “latest published version” link for WCAG 2.1, https://www.w3.org/TR/WCAG21/ — that address today serves an entirely different, later W3C Recommendation dated May 6, 2025. According to the rule’s own appendix, DOJ knew about a September 2023 revision to WCAG 2.1 and about the finalized WCAG 2.2, and deliberately adopted neither. This overview explains what the rule’s text requires; it does not itself assess whether any particular website complies with WCAG 2.1 or the ADA web rule.

Abstract blank document with tactile dots, a path shape, and a magnifying lens on a muted paper surface. — Illustrative record-reading guide for accessibility and disability coverage; it contains no factual claim or record data.

This original record-reading guide is a general reading aid, not cited evidence. It does not depict a source record; the article text and source links provide the facts.

Key points

The rule freezes the 2018 text: “subpart H of this part requires conformance to the version of WCAG 2.1 that was published in 2018.”
DOJ acknowledged a later revision existed — “the WAI published some revisions to WCAG 2.1 on September 21, 2023” — and chose not to adopt it, because “the Department believes that public entities have not had sufficient time to become familiar with the 2023 version.”
WCAG 2.2 “was published in final form on October 5, 2023, which was after the NPRM associated with the final rule was published and after the comment period closed,” and DOJ notes that W3C itself “has made clear that WCAG 2.2 does not ‘deprecate or supersede’ WCAG 2.1.”
One concrete result of freezing the 2018 text: Success Criterion 4.1.1, which W3C “has described… as ‘obsolete’ and stated that it ‘is no longer needed for accessibility’,” is nonetheless still required — “conformance to Success Criterion 4.1.1 is still required by subpart H of this part.”
W3C’s own “latest published version” link for WCAG 2.1 no longer points to the 2018 text the rule cites; that address now resolves to a W3C Recommendation dated May 6, 2025. (W3C latest published version)

A Fixed, Dated Citation

The rule cites a dated document, not a moving target. The 2018 WCAG 2.1 Recommendation itself is explicit about being a fixed, dated artifact. Its header reads “W3C Recommendation 05 June 2018,” and the document separately labels its own permanent address, “This version: https://www.w3.org/TR/2018/REC-WCAG21-20180605/,” distinct from “Latest published version: https://www.w3.org/TR/WCAG21/.” The ADA rule’s appendix confirms it is the fixed, dated address the rule relies on: “subpart H of this part requires conformance to the version of WCAG 2.1 that was published in 2018.” A reader who instead follows W3C’s “latest published version” link lands on a different document — the page at that address is now a separate W3C Recommendation dated May 6, 2025 (“W3C Recommendation 06 May 2025”), not the 2018 text subpart H names.

A Revision DOJ Declined

DOJ knew about the September 2023 revision to WCAG 2.1 and did not adopt it. The rule’s own explanation rules out any reading that the 2018 reference was an oversight. DOJ’s appendix states plainly that “the WAI published some revisions to WCAG 2.1 on September 21, 2023,” so the Department was aware a newer version of the same guideline existed. It chose the earlier text anyway, giving its reasoning directly: “the Department believes that public entities have not had sufficient time to become familiar with the 2023 version.” The freeze on 2018 is therefore a stated policy choice, not an artifact of when the rule happened to be drafted.

The WCAG 2.2 Timing Gap

WCAG 2.2 was finalized before the rule itself was final, and DOJ still did not move to it — WCAG 2.2 followed a path similar to the September 2023 revision. Per the appendix, it “was published as a candidate recommendation—a prefinalization stage—in May 2023, and was published in final form on October 5, 2023, which was after the NPRM associated with the final rule was published and after the comment period closed.” DOJ also cites W3C’s own position that adopting WCAG 2.2 was not strictly required to keep pace with WCAG 2.1: W3C “has made clear that WCAG 2.2 does not ‘deprecate or supersede’ WCAG 2.1.” Both points — timing and W3C’s own framing — are the appendix’s stated basis for keeping subpart H tied to the 2018 text rather than moving to WCAG 2.2.

Whether a future DOJ rulemaking will eventually move subpart H to WCAG 2.2, or to a later revision of WCAG 2.1, is not something the current rule’s text settles. The discussion above describes only what the existing appendix says about the timing of WCAG 2.2’s finalization and W3C’s own framing of it; it does not predict what any future rulemaking will adopt.

Frozen criterion status

Freezing the reference to 2018 carries a concrete, named cost: Success Criterion 4.1.1. The appendix notes that W3C itself “has described Success Criterion 4.1.1 as ‘obsolete’ and stated that it ‘is no longer needed for accessibility’.” Despite that assessment from WCAG’s own publisher, the appendix is direct about the rule’s effect: “Therefore, conformance to Success Criterion 4.1.1 is still required by subpart H of this part.” Because the rule points to the 2018 document rather than to WCAG 2.1 as currently maintained, a checkpoint W3C no longer considers necessary remains a mandatory one under this rule.

This explains how the rule treats that checkpoint, not what the checkpoint itself technically requires. The quotes above describe the rule’s treatment of Success Criterion 4.1.1 — that it remains a mandatory conformance item despite W3C’s own “obsolete” label — not a technical explanation of what the criterion covers or why W3C reached that assessment.

The Wrong Link to Follow

The practical consequence of that distinction follows directly: only the dated 2018 address is what subpart H names, so treating W3C’s generic “latest” link as equivalent to the rule’s citation is a mistake, even though both addresses describe WCAG 2.1. (ADA rule appendix, W3C latest published version) Someone trying to confirm what the ADA rule currently requires should rely on the 2018 URL specifically rather than W3C’s “latest published version” address, because the “latest” address will keep moving to whatever document W3C publishes next — exactly as it already has once, per the earlier point about where that address resolves today.