Digital accessibility for state and local government: outlook to 2027

The ADA Title II web and app rule now starts in April 2027, HHS's matching section 504 rule in May 2027, and both agencies say the substance may change before then.

The question for 2027

State and local governments were weeks from the first federal deadline for accessible websites and apps when the Justice Department moved it. The standard, the exceptions and the reach into vendor-run content survived; the calendar, and the room for a deeper revision, changed. This outlook sets out where the federal and state rules stand as checked on November 16, 2026. It then compares their reach across types of organization and sets out what is likely before the new dates.

The Title II rule as it stands

The Justice Department's final rule, published April 24, 2024 and effective June 24, 2024, added subpart H to the Title II regulations at 28 CFR part 35 [3]. Section 35.200 requires a public entity to make the web content and mobile apps it provides or makes available, directly or through contractual, licensing or other arrangements, conform to the Level A and Level AA success criteria of WCAG 2.1 [2]. The department's fact sheet lists who that reaches: benefit and social service offices, public schools, colleges and universities, police, courts, elections offices, public hospitals and clinics, parks, libraries and transit agencies, plus special purpose districts, Amtrak and commuter authorities [4].

The current compliance dates, set by an interim final rule effective April 20, 2026, are April 26, 2027 for a public entity, other than a special district government, with a total population of 50,000 or more, and April 26, 2028 for smaller entities and every special district government [1] [2]. The original dates were April 24, 2026 and April 26, 2027 [3]. The eCFR text current to November 12, 2026 carries the 2027 and 2028 dates and shows no later amendment [2].

Section 35.201 excludes five kinds of content: archived web content, preexisting conventional electronic documents unless they are still used to apply for or take part in a service, content posted by third parties not acting under an arrangement with the entity, individualized secured documents about a specific person or account, and social media posts made before the compliance date [2]. Section 35.205 treats an entity as compliant when it can show its nonconformance has so minimal an impact that people with disabilities can still get the same information, interactions and transactions with substantially equivalent timeliness, privacy, independence and ease of use [2]. Fundamental alteration and undue burden remain limits, but the entity must demonstrate them [2].

Why the date moved, and what the department said next

The interim final rule cites correspondence sent to OMB after its April 11, 2025 request for deregulation ideas, including from higher education associations and the Small Business Administration's Office of Advocacy, and the department's own view that it overestimated covered entities' staffing and technology capacity [1]. It also cites litigation risk: Title II carries a private right of action, and plaintiffs can recover injunctive relief and attorneys' fees [1].

The department put a number on the delay. It estimates the one-year move saves $2.775 billion in present value over ten years at a 7% discount rate, or $395 million a year, with small entities taking about 53% of that, and it says it was unable to quantify the delay's effect on benefits [1]. It puts the 2024 rule's total ten-year cost at $24.7 billion [1].

Two statements in the preamble matter more than the dates. The department plans future rulemaking on the substance of the 2024 rule and will consider proposing changes during the extension; if it does not, and circumstances suggesting further delay do not exist, it fully anticipates implementing the rule at the new dates [1]. And regardless of the dates, covered entities keep their existing Title II obligation to make services offered online accessible [1]. The entry for the rulemaking, RIN 1190-AA82, in the most recent Unified Agenda (the 2026 edition), is designated deregulatory and economically significant, describes reconsidering whether provisions of the 2024 rule could be made less burdensome, and lists the proposed rule's date as "To Be Determined" [6].

Moraph's view

Moraph's view: the extension did less to change what an entity must eventually do than to change what it can safely plan around. A proposed rule on substance would most likely target the hardest parts, such as legacy documents, course content and small governments, rather than drop the standard. Agencies that pause now are betting the second rulemaking arrives, and favors them, before April 2027; we think that is the weaker bet, because the Title II duty and the private right of action do not move with the regulation.

The litigation over the delay

On May 21, 2026 the National Federation of the Blind sued the Justice Department, HHS and their heads in the U.S. District Court for the District of Maryland (No. 1:26-cv-02007), challenging both agencies' interim final rules under the Administrative Procedure Act [7]. The complaint asks the court to hold unlawful, vacate or set aside the interim rules and to declare them unlawful [7]. As checked on November 16, 2026, we found no ruling on those claims, and the eCFR still carries the extended dates [2] [9].

Health care: the parallel HHS section 504 rule

HHS's 2024 section 504 rule puts the same WCAG 2.1 Level A and AA standard on web content and mobile apps of every recipient of its financial assistance, including content provided through contractual, licensing or other arrangements [9]. An interim final rule published May 11, 2026 and effective May 7, 2026 moved the dates to May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for those with fewer, from May 11, 2026 and May 10, 2027 [8]. HHS, like the Justice Department, said it will consider proposing changes to the substance of the web and mobile requirements during the extension [8].

HHS was more explicit about the trade it made. Using its 2024 estimates, it found the delay lowers annualized costs by $114.3 million and annualized benefits by $204.6 million at a 7% discount rate, and says its cost savings leave out savings it could not quantify [8]. A separate HHS final rule published November 3, 2026, effective January 4, 2027, amends only the exclusions in the definition of disability, section 84.4(g), and leaves the web provisions alone [10].

The two rules draw their size lines differently: Title II by total population, the HHS rule by employee count [2] [9]. The Justice Department lists public hospitals and clinics as Title II entities [4], and one that takes HHS funding is also an HHS recipient [9]; a private health system that takes HHS funding falls under the HHS rule but not Title II. Kiosks sit in the HHS rule without a technical standard or compliance date [9].

Federal agencies: Section 508, unchanged since 2018

Federal agencies are on a different track and an older standard. The Access Board's Section 508 standards at 36 CFR part 1194 point to WCAG 2.0, and the eCFR shows no amendment to the part since 2018 [11] [12]. The Access Board describes that 2017 rule as the "refresh" of guidelines and standards first issued in 1998 and 2000 [12].

The federal record is weak even on the older standard. GSA's FY 2025 Governmentwide Section 508 Assessment, built from 212 agency, parent agency and component responses that agencies self-reported, puts governmentwide conformance at 1.96 on a 5-point scale and finds about half of agencies do not routinely test ICT for conformance [13]. Only 30% of agencies "almost always" verify ICT deliverables for Section 508 conformance, and GSA asks Congress to clarify which agencies Section 508 covers and to strengthen enforcement [13].

States: Colorado shows what a private remedy does

Colorado moved earlier than the federal rule. HB21-1110, enacted in 2021, made a public entity's or state agency's failure to fully comply with the Office of Information Technology's accessibility standards by July 1, 2024 a form of discrimination, placed liability for content on whoever manages the content and for the platform on whoever manages the platform, and set a statutory fine of $3,500 per plaintiff for each violation [14]. HB24-1454 then gave entities immunity until July 1, 2025 if they showed good faith efforts, including a progress report on their public web pages updated quarterly and an easy-to-find redress process; that grace provision repealed itself on July 1, 2025 [15]. OIT's guidance, as captured August 22, 2026, says an entity can comply by publishing an accessibility statement with two contact methods and meeting one of several options, including conformance or a published progress plan, and that enforcement is through the courts, with no state enforcement agency [16].

The 2024 federal rule does not limit state laws that give greater or equal protection, and if a state law requires WCAG 2.2, nothing in the rule prevents an entity from meeting it [3].

Moraph's view

Moraph's view: Colorado is the preview of 2027 for the rest of the country. Once a fixed standard, a fixed date and a per-violation remedy coexist, the useful evidence is a dated progress record and a working accommodation channel, not a perfect audit. Title II has no statutory fine, but it has fee-shifting, so a city that cannot show progress at the 2027 date is exposed in the same way.

Federal enforcement

The Justice Department has enforced web access under Title II without the technical rule. In June 2024 it announced settlements with four Texas counties over inaccessible election websites, under which the counties agreed to make existing and future election content accessible, hire an independent auditor, adopt policies and training, and designate a coordinator [17]. Its guidance tells governments to check whether their vendors can produce accessible content [5]. We found no Justice Department action enforcing subpart H itself, which is consistent with no compliance date having yet arrived.

What differs by organization

What differs by organization
OrganizationRule, standard and start date as checked on November 16, 2026
Larger state, county or city governmentADA Title II, WCAG 2.1 AA, from April 26, 2027 [2]
Smaller government or special districtADA Title II, WCAG 2.1 AA, from April 26, 2028 [2]
Larger HHS funding recipientSection 504, WCAG 2.1 AA, from May 11, 2027 [9]
Small HHS funding recipientSection 504, WCAG 2.1 AA, from May 10, 2028 [9]
Federal agencySection 508, WCAG 2.0 AA, required since January 18, 2018 [11] [12]
Colorado state agency or public entityState law and OIT rules, grace period ended July 1, 2025 [15]

Vendors sit across all of these. Because both federal rules cover content provided through contractual, licensing or other arrangements, the payment page, permit portal, learning platform or patient app a vendor runs is inside the customer's duty [2] [9].

Moraph's view

Moraph's view: the vendor market will settle on WCAG 2.1 AA, documented in a conformance report, as the floor for public-sector and health contracts in 2027 whatever happens to the dates, because the buyers' exposure under Title II and section 504 does not wait for the regulation. Vendors that can show WCAG 2.2 conformance will also meet the states that ask for more.

What this means for you

  • Cities, counties and states of 50,000 or more: Plan to the April 26, 2027 date in the current text [2] and keep a dated record of progress; the Justice Department says the existing Title II obligation applies regardless of the dates [1].
  • Small governments and special districts: Use the extra year to inventory content against the five exceptions in section 35.201, especially archived content and documents no longer used to apply for services [2].
  • Public hospitals and HHS-funded health systems: Map which content falls under Title II, section 504 or both, since the HHS dates turn on employee count and the Title II dates on population [2] [9].
  • Vendors to government and health care: Expect WCAG 2.1 AA conformance clauses and evidence requests: both rules reach content customers provide through contractual, licensing or other arrangements [2] [9], and the Justice Department tells governments to check whether their vendors can produce accessible content [5].
  • Federal agencies and their contractors: Treat acquisition as the control point: GSA found only 30% of agencies "almost always" verify ICT deliverables for Section 508 conformance [13].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 60% Open

    The Justice Department publishes in the Federal Register a notice of proposed rulemaking that would change the substantive requirements of 28 CFR part 35, subpart H.

    How we will check: A Federal Register document of type Proposed Rule from the Department of Justice, dated on or before December 31, 2027, proposing amendments to any of 28 CFR 35.200 to 35.205 or the related definitions in 35.104 other than compliance dates alone.

    Basis: The April 2026 interim final rule says the department plans future rulemaking on the substance of the 2024 rule and will consider issuing a proposal during the extension [1]; the Unified Agenda lists the proposal as deregulatory with its date to be determined [6].

  2. P2 By Confidence 55% Open

    The compliance date for public entities of 50,000 or more in 28 CFR 35.200(b)(1) is later than April 26, 2027 when that day arrives.

    How we will check: The eCFR text of 28 CFR 35.200(b)(1) in effect on April 26, 2027 shows a compliance date later than April 26, 2027, or a Federal Register rule published on or before that day extends or suspends it.

    Basis: The department moved the first date four days before it arrived, cited compliance capacity and litigation risk, and conditioned implementation at the new date on no proposal being issued and no circumstances suggesting further delay [1]; the extended date is in the current text [2].

  3. P3 By Confidence 75% Open

    No court vacates or stays the Justice Department's April 20, 2026 interim final rule extending the Title II web and mobile compliance dates.

    How we will check: No order of the U.S. District Court for the District of Maryland in National Federation of the Blind v. Department of Justice, No. 1:26-cv-02007, or of any other court, entered on or before April 26, 2027, vacates, sets aside or stays the interim final rule (91 FR 20902).

    Basis: The complaint seeks vacatur under the Administrative Procedure Act [7]; the interim rule was issued with post-publication comment and states the department's reasons for acting without prior notice [1]; the extended dates remain in the eCFR as checked [2].

  4. P4 By Confidence 85% Open

    The Access Board does not publish a proposed rule to revise the Section 508 ICT standards in 36 CFR part 1194.

    How we will check: No Federal Register document of type Proposed Rule or Rule from the Architectural and Transportation Barriers Compliance Board, dated on or before December 31, 2027, proposes or makes changes to the technical requirements in 36 CFR part 1194.

    Basis: The eCFR shows no amendment to part 1194 since 2018 [11], and the Access Board's ICT rulemaking record ends with the 2017 refresh and its 2018 correction [12].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

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

  • ADA Title II
  • 28 CFR part 35
  • WCAG 2.1
  • section 504
  • Section 508
  • web accessibility
  • mobile apps
  • Colorado HB21-1110
  • state and local government