Section 508 standards (36 CFR part 1194) and the ADA Title II web rule: how the two fit together, explained

Federal agencies follow the Access Board’s Section 508 standards, which point to WCAG 2.0 Level AA; state and local governments follow the Justice Department’s Title II rule, which points to WCAG 2.1 Level AA from April 26, 2027 or April 26, 2028. Vendors serving both need to know which applies.

Two federal accessibility regimes govern public-sector websites, documents and apps in the United States. Section 508 of the Rehabilitation Act covers the federal government’s own technology. Title II of the Americans with Disabilities Act covers state and local governments, and since 2024 it has had its own technical rule for the web and mobile apps. They share a lineage in the Web Content Accessibility Guidelines (WCAG), but they differ in who is covered, which WCAG version applies, how exceptions work and when compliance is due. This explainer sets the two side by side.

Section 508: the federal standard

The Access Board revised its Section 508 standards in a final rule published January 18, 2017. The rule took effect March 20, 2017, and compliance with the Section 508-based standards was required from January 18, 2018 [2]. The Access Board issued a correction on January 22, 2018 to restore provisions for TTY access [3].

The standards are at 36 CFR part 1194. Section 1194.1 places them in appendices A, C and D, covering technology developed, procured, maintained or used by federal agencies [1]. The Access Board notes that the standards are part of the Federal Acquisition Regulation [3]. Their main features [1]:

  • Scope (E201): technology procured, developed, maintained or used by agencies must conform. Compliance is mandatory for agencies subject to Section 508.
  • Electronic content (E205): public-facing content, such as an agency website, blog or social media page, must meet WCAG 2.0 Level A and AA. Non-public content must also conform when it is official business in listed categories, including emergency notifications, benefit and eligibility notices, forms, training materials and intranet content designed as a web page.
  • Software (E207): user interfaces and platform and application content must meet WCAG 2.0 Level A and AA, with word substitutions and four excepted success criteria for non-web software and non-web documents.
  • Hardware (E206) and support documentation and services (E208) have their own requirements in the technical chapters.
  • Exceptions (E202): unaltered legacy technology that met the earlier standard, national security systems, technology a contractor acquires incidentally to a contract, and undue burden or fundamental alteration, which the agency must document and pair with an alternative means of access. Where conforming products are not commercially available, the agency buys what best meets the standards and documents its market research.

ADA Title II: the state and local rule

The Justice Department’s final rule, published April 24, 2024 and effective June 24, 2024, added subpart H to the Title II regulations [5]. Section 35.200 requires a public entity to ensure that the web content and mobile apps it provides or makes available, directly or through contractual, licensing or other arrangements, meet WCAG 2.1 Level A and AA [4]. The Department’s fact sheet says the rule applies to all state and local governments, including those that contract with other entities to provide services [7].

An interim final rule, effective April 20, 2026, extended the compliance dates without changing the substantive requirements [6]. The current text sets [4]:

  • April 26, 2027 for a public entity, other than a special district government, with a total population of 50,000 or more;
  • April 26, 2028 for a public entity with a total population under 50,000 and for any special district government.

Subpart H has five exceptions: archived web content, preexisting conventional electronic documents, content posted by third parties not acting under an arrangement with the entity, individualized secured documents, and preexisting social media posts. It also allows conforming alternate versions only where technical or legal limits make direct accessibility impossible, permits equivalent facilitation, keeps the fundamental alteration and undue burden limits, and treats noncompliance with minimal impact on access as meeting the requirement in limited circumstances [4]. Our Title II explainer covers the rule in more detail.

Where the two differ, and why

  • Who: Section 508 binds federal agencies [1]; subpart H binds state and local public entities [4]. In our reading, neither applies directly to a private vendor, but both reach vendors through procurement and contracts.
  • Which WCAG: Section 508 uses WCAG 2.0 [1]; subpart H uses WCAG 2.1 [4]. In the 2024 rule, the Justice Department explained that the Small Business Administration had urged WCAG 2.0 to match the federal standard, and that when the Access Board adopted WCAG 2.0 in 2017, WCAG 2.1 had not been finalized. The Department chose WCAG 2.1 because it adds accessibility features not in WCAG 2.0 and an increasing number of governmental entities use it [5].
  • Documents and apps: Section 508 exempts non-web documents and software from four WCAG success criteria. The Justice Department considered that approach and declined to copy it, preferring one standard applied to the extent the criteria can be applied [5].
  • Perfect conformance: the Department said requiring perfect conformance would be less appropriate under subpart H than under Section 508, given the wide variety of public entities Title II covers and their varying resources, compared with the relatively limited number of federal agencies that follow Section 508 [5].

A related deadline sits outside both rules. HHS extended the web accessibility dates in its Section 504 rule for recipients of its financial assistance to May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller recipients [8]. In our reading, a public hospital or health department may be covered by both Title II and that rule.

What this means for teams that build for government

Because the Justice Department describes WCAG 2.1 as adding features beyond WCAG 2.0 [5], in our view a product built and tested to WCAG 2.1 Level AA generally positions a supplier for both federal and state and local buyers, though the Section 508 hardware, software interoperability and documentation requirements still need separate review. Accessibility conformance reports should say which standard and version they test against. Contracts with state and local governments should allocate responsibility for content the vendor hosts, since subpart H reaches content provided through contractual arrangements [4]. These are practice points, not requirements beyond those cited.

This explainer describes the rules as checked on November 14, 2026; it is not legal advice, and organizations should confirm with counsel how they apply.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • Section 508
  • 36 CFR part 1194
  • Access Board
  • ADA Title II
  • 28 CFR part 35
  • WCAG
  • digital accessibility