accessibility compliance

DOJ Title II Web Accessibility Deadline: 7 Moves Public Entities Should Make Before April 2027

DOJ Title II Web Accessibility Deadline: 7 Moves Public Entities Should Make Before April 2027

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

The DOJ Title II web accessibility deadline moved by one year — to 26 April 2027 for public entities with a total population of 50,000 or more, and 26 April 2028 for smaller entities and special district governments. The technical standard did not change: web content and mobile apps that state and local governments provide or make available must still meet WCAG 2.1 Level AA. Private businesses under Title III got no extra time.

That extension is now the live calendar on ADA.gov’s Title II web rule fact sheet, which records the Department of Justice Interim Final Rule published in the Federal Register on 20 April 2026. Fresh urgency came at the 2026 NASCIO Annual Conference on 28 September 2026, where state accessibility leaders told StateScoop that delays do not erase civil-rights obligations — and that document remediation and high-traffic systems remain the top failure modes.

This guide is written by accessibility testers who audit government and public-sector digital services. It is not legal advice. It explains what the DOJ Title II web accessibility deadline actually changed, what NASCIO’s state officer survey shows about readiness, and a seven-move programme you can start this quarter.

Title II Web Rule At A Glance

Choose Your Next Step

Most public entities start with a free call to sort their deadline, scope and priorities. Agencies ready for testing can request a government audit quote; see our ADA and Section 508 accessibility audit and pricing ($500 Quick Audit / $2,000 Complete Audit). For a quick first look at one page, AccessibilityScore.in (opens in a new tab) gives a free automated score, a starting point that does not replace a manual audit.

Free 30-Minute Call

Best for: agencies still working out their date, scope or budget

A first conversation with our founder about where your sites, apps and documents stand, which deadline applies and what to test first. No technical prep needed.

Book a free 30-minute call (opens in a new tab)

Government Audit Quote

Best for: cities, counties, schools, courts and agencies ready to baseline

Manual WCAG 2.1 AA testing of your highest-traffic journeys, active PDFs and vendor tools, with a prioritised, dated report you can show leadership.

Request a government audit quote

$100 Technical Consultation

Best for: teams with audit findings, a vendor ACR or a developer to bring

A one-hour hands-on session to walk through findings, review a vendor’s conformance report or check live issues with your developer. Not for first-time scoping.

Book the $100 technical hour

What the DOJ Title II Web Rule Requires

Title II of the ADA requires state and local governments to make their services, programs, and activities accessible to people with disabilities — including services offered online and through apps. On 24 April 2024, the Department of Justice published a final rule that made that duty concrete for web content and mobile apps: adopt WCAG 2.1 Level AA as the technical standard for content the public entity provides or makes available, directly or through contractual, licensing, or other arrangements.

ADA.gov’s fact sheet is explicit about scope. Covered entities include state and local agencies, public schools and universities, courts, elections offices, public hospitals, libraries, parks programmes, and transit agencies. If a county parks page is built by a vendor, the county still owns the WCAG 2.1 AA obligation. If a city parking app is run by a private company under contract, the city still owns it.

For how Title II sits next to Title III, Section 508, the EAA and VPATs, see our accessibility framework comparison. For public-sector programme delivery, see our government and public-sector accessibility specialty. For Title III private-sector lawsuit patterns (a different statute), see 2026 ADA website lawsuit statistics and Minnesota ADA website lawsuits.

What Changed on 20 April 2026 — and What Did Not

Four days before the original large-entity deadline, DOJ published an Interim Final Rule extending both compliance dates by one year. ADA.gov now publishes this table:

Public entityCompliance date now
Total population of 50,000 or more26 April 2027
Total population under 50,00026 April 2028
Special district government (any size)26 April 2028
What the April 2026 extension changed, and what it left alone
Rule elementChanged?What it means for you
Compliance datesYes, one year later26 April 2027 for 50,000 or more; 26 April 2028 for smaller entities and special districts
Technical standardNoWCAG 2.1 Level AA is still the yardstick for web content and mobile apps
CoverageNoStill includes content you provide or make available, including through vendors, contracts and licences
ExceptionsNoArchived content, preexisting conventional electronic documents, certain third-party posts, individualized password-protected documents and preexisting social media posts keep the same conditions ADA.gov lists
Existing Title II dutiesNoEffective communication, reasonable modifications and equal opportunity never paused; even when an exception applies, you may still need to provide content in an accessible format on request

One caveat for planning: the IFR itself says the Department “plans to engage in future rulemaking processes related to the substantive requirements of the 2024 final rule.” As of 14 October 2026, the Federal Register shows no new rule or proposal under the rule’s identifier (RIN 1190-AA82) since the IFR; the Department’s August 2026 regulatory agenda still lists the rulemaking. Plan to WCAG 2.1 AA, which is what the rule says today, and watch for a proposal.

Public hospitals, clinics and health agencies that receive HHS funding should also track a separate clock. An HHS interim final rule published on 11 May 2026 moved the Section 504 web and app compliance dates to 11 May 2027 for recipients with 15 or more employees and 10 May 2028 for smaller recipients. Our healthcare accessibility page covers that work.

“Total population” is generally the 2020 U.S. Census Bureau population of the government the entity belongs to, not student headcount or app users. ADA.gov’s examples: a city police department or city library uses the population of the city that runs it; a school district is not a special district — a city school district uses the city’s population, a county school district uses the county’s, and an independent school district uses the most recent Small Area Income and Poverty Estimates.

Why September 2026 Refreshed the Story

The extension is months old. The operational story is not. On 28 September 2026, NASCIO’s Annual Conference in San Diego hosted an IT Accessibility Panel, which StateScoop covered the next day. Panelists Kris Adams (Pennsylvania chief accessibility officer) and Marie Cohan (Texas statewide digital accessibility officer), with NASCIO’s Kalea Young-Gibson, argued that accessibility should be treated as a core capability like cybersecurity, not a one-time compliance milestone.

StateScoop also summarised CIO-survey context that matters for programme design:

State CIO context reported by StateScoop, September 2026
SignalFigureWhy it matters for Title II
Rank on NASCIO’s 2026 State CIO Top 10Number six (up from ten)Leadership attention is rising, so budget asks tied to the deadline land better now
States without a chief accessibility officer46%Without a named owner, deadlines slip between agencies
States without dedicated accessibility funding67%Remediation has to be prioritised by risk, not done all at once

That is the practical backdrop for the DOJ Title II web accessibility deadline: more leadership attention, still-thin budgets, and a calendar that now ends in April 2027 for large entities.

Timeline for the DOJ Title II web accessibility deadline: April 2026 IFR, September 2026 NASCIO panel, April 2027 for entities of 50,000 or more and April 2028 for smaller entities

What NASCIO’s State Accessibility Officer Survey Found

NASCIO’s inaugural State Accessibility Officer survey, published on 20 August 2026 as Here to Stay, Here to Grow: A National Portrait of State Digital Accessibility Officers, drew responses from 36 of 40 known state digital accessibility officers. Key findings, as published by NASCIO and reported by StateScoop:

Key findings from NASCIO’s 2026 State Accessibility Officer survey
FindingResult
Self-reported status against the 2024 DOJ Final RuleMost states partially or mostly compliant; only two reported minimal compliance or noncompliance
Resources to remediate all state websites and apps69% said they do not have the resources or staff (StateScoop framed this against the April 2027 deadline)
Dedicated digital accessibility budget67% reported none
Authority across all state agenciesOnly 17% had oversight authority across all agencies; 23% had no formal enforcement authority; more than half had no team reporting to them
Team size, where a team exists80% have fewer than 10 people
Top named challengesLack of funding, lack of authority, and lack of understanding among state personnel
Labour-intensive gapsDocument remediation, high-traffic system remediation, expanded testing, exception identification and remediation workflows

NASCIO’s report also ranks the areas where states expect DOJ Final Rule non-compliance. StateScoop’s September panel coverage summarised the top two together at 75%. That matches what we see in public-sector audits: PDF forms and benefit portals fail long after homepage contrast is fixed.

DOJ Final Rule non-compliance areas named by NASCIO respondents
AreaShare of respondentsWhere to start
Document remediation75%PDF document remediation
Remediating high-traffic systems and digital services70%Accessibility remediation
Expanded testing60%ADA and Section 508 audit
Identifying content that fits rule exceptions55%Move 5 below

The 7 Moves At A Glance

Use this table as the programme outline; each move is explained below.

Seven moves before the DOJ Title II web accessibility deadline
MoveWhat to doHelpful resource
1. Confirm your dateUse ADA.gov population rules, then write the date into your charter and contractsADA.gov fact sheet
2. InventoryList every site, app, subdomain and vendor tool residents useFree needs assessment
3. Baseline with manual testingTest top journeys with keyboard and screen readers, keep a dated baselineGovernment audit quote
4. DocumentsRetire, archive, convert to HTML or remediate active PDFs and formsPDF remediation
5. Exceptions disciplineApply exceptions only when every ADA.gov condition is metPublisher training
6. ProcurementRequire a current ACR, a dated fix plan and WCAG 2.1 AA contract languageVPAT and ACR services
7. Leadership, training, monitoringName an owner, train staff and monitor new contentMonitoring and governance

Move 1: Confirm Your Exact Date From Population, Not Intuition

Mis-sorting entities is the fastest way to brief the wrong deadline. Use ADA.gov’s population rules, not “we’re a small agency” feelings. A 40,000-student public university in a large state still tracks the large-entity date. A special district (water board, many transit authorities) gets 26 April 2028 regardless of size. School districts follow city/county/independent rules — they are not automatically special districts.

Write the date into your programme charter and vendor contracts so every workstream uses the same clock.

Move 2: Inventory Sites, Apps, and Vendor Tools Residents Actually Use

List every property the public uses to apply for benefits, pay fees, book appointments, register for school, or read emergency information — including subdomains and third-party widgets. ADA.gov is clear that calendars, payment systems, maps, and booking tools posted by the entity usually must meet WCAG 2.1 AA even when a vendor built them.

Mark owner, platform, traffic, and whether the journey is time-sensitive (elections, tax, licensing, benefits). That inventory becomes the risk register Adams and Cohan described when they told StateScoop to prioritise highest-traffic, highest-impact services first.

Move 3: Baseline High-Traffic Journeys With Manual Testing, Not Scans Alone

Automated scans are useful for backlog sizing. They are not a conformance claim. Walk the top journeys with keyboard-only navigation and at least one screen reader on the browsers your residents use. Our guides on manual keyboard accessibility testing, screen reader accessibility testing, automated accessibility testing, and mobile accessibility testing spell out the methods.

Keep a dated baseline. When counsel or executives ask whether the extra year was used, a timestamped audit beats a slide deck.

HalfAccessible’s ADA and Section 508 accessibility audit, accessibility audit services, and government accessibility audit request page are built for that public-sector baseline. See also the sample audit report.

Government benefits form on a monitor being tested with a keyboard and screen reader before the Title II deadline

Move 4: Treat Documents as a First-Class Workstream

NASCIO respondents keep naming document remediation as a top gap — for good reason. The DOJ rule’s “preexisting conventional electronic documents” exception only helps files that meet every condition ADA.gov lists, and it does not cover documents currently used to apply for, access, or participate in a service. A 2020 PDF business-license application still in active use is not off the hook because it is old.

Sort documents into: retire, archive under a true archive exception, replace with accessible HTML, or remediate. Prioritise active forms and instructions. Our document accessibility testing, PDF accessibility guide, and PDF document remediation services map onto that queue.

Move 5: Fix Exceptions Discipline Before You Lean on Them

Exceptions are narrow. Archived content needs all four ADA.gov conditions (created before the compliance date or reproducing older physical media; kept only for reference/research/recordkeeping; stored in a special archive area; unchanged since archive). Preexisting social media posts are limited to posts made before your compliance date. Third-party user posts on a message board may be excepted; the platform the entity installed usually is not.

When the deadline moved, the “preexisting” cutoff moved with it — which is useful for genuinely old reference files and a trap for anyone who parks active service content in a folder named “archive.” Train publishers on the difference.

Move 6: Put WCAG 2.1 AA Into Procurement and Vendor Escalation

If residents pay, book, or apply through a vendor product, that product is on your Title II clock. Ask for a current Accessibility Conformance Report (VPAT/ACR), a dated remediation plan for known gaps, and contract language that names WCAG 2.1 Level AA. NASCIO’s officer survey found states are relatively stronger on accessibility policy and procurement language than on full remediation capacity — use that strength while you staff the backlog.

Pair vendor pressure with internal ADA compliance remediation so your own templates and design system stop reintroducing the same failures.

Move 7: Fund Leadership, Training, and Monitoring — Not a One-Week Blitz

StateScoop’s September coverage stressed writing chief accessibility officer roles into policy (ideally statute) so the programme survives budget cycles. Adams described getting accessibility into the software development lifecycle early; Cohan compared accessibility to security and privacy as an ongoing technology control.

That means:

  1. A named accountable owner (even in a federated IT model).
  2. Accessibility training workshops for publishers and developers.
  3. Accessibility monitoring and governance so new pages and PDFs do not undo spring remediation.
  4. A realistic budget ask tied to high-risk journeys — 67% of states lacking dedicated funding is a programme risk, not a reason to wait until March 2027.
Public-sector accessibility governance checklist for the DOJ Title II deadline: inventory, audit, documents, vendors, training and monitoring

Private Businesses: This Extension Is Not Yours

The DOJ Title II web accessibility deadline applies to state and local government. It does not set a Title III technical standard or deadline for shops, clinics, or SaaS companies. Title III website risk continues through private litigation and related state claims — tracked separately in sources such as Seyfarth’s mid-year Title III filing counts and digital-accessibility trackers. For post-filing remediation patterns on private sites, see our ADA lawsuit remediation guide. If a private operator tells you “the ADA deadline was pushed,” correct the statute before you change the roadmap.

Start Before the DOJ Title II Web Accessibility Deadline Owns Your Calendar

The deadline moved; the standard did not; NASCIO’s state officers are already telling peers that funding, authority, documents and high-traffic systems are the binding constraints. Public entities that inventory now, audit critical journeys, remediate active documents, and bind vendors to WCAG 2.1 AA will treat April 2027 (or 2028) as a verification milestone — not a discovery crisis.

If you need a prioritised public-sector backlog, request a government accessibility audit, review our ADA and Section 508 accessibility audit, or start with a free 30-minute call to scope audit, PDF remediation, training and monitoring. Teams that already have findings or a vendor ACR to review can book the $100 one-hour technical consultation.

Frequently Asked Questions

What is the DOJ Title II web accessibility deadline now?

According to ADA.gov’s updated fact sheet, public entities with a total population of 50,000 or more must comply by 26 April 2027. Public entities with a total population under 50,000, and special district governments of any size, must comply by 26 April 2028. Those dates come from the Department’s Interim Final Rule published 20 April 2026.

Did the technical standard change when the deadline moved?

No. The fact sheet still identifies WCAG 2.1 Level AA as the technical standard for covered web content and mobile apps. The IFR extended dates; it did not rewrite the success criteria, exceptions framework, or coverage of vendor-provided content. DOJ has said it plans future rulemaking on the rule’s substantive requirements, but no proposal had been published in the Federal Register as of 3 October 2026.

Does the extension pause existing ADA Title II duties?

No. ADA.gov continues to emphasise longstanding Title II obligations such as effective communication and equal opportunity to participate. The rule gives a specific WCAG yardstick and schedule; it does not create a gap year where inaccessible online services are somehow permitted.

Do private websites get the same extension?

No. This rule covers Title II public entities. Private businesses open to the public are addressed under Title III, which did not receive this compliance-date extension. Treat Title III website risk as a separate workstream — see our ADA lawsuit remediation guide and 2026 ADA website lawsuit statistics.

Why do documents keep showing up in NASCIO findings?

Because active PDFs and office files are labor-intensive to remediate, and many remain in current use for applications and services. In NASCIO’s 2026 officer survey, 75% of respondents named document remediation and 70% named remediating high-traffic systems among their DOJ Final Rule non-compliance areas. The preexisting-document exception does not rescue files still used to apply for or participate in a service.

Should we aim for WCAG 2.2 instead of 2.1?

The Title II rule names WCAG 2.1 Level AA. Testing to WCAG 2.2 AA generally covers the 2.1 AA set (with 4.1.1 Parsing removed as obsolete) plus newer criteria, which can be smart engineering hygiene — especially if you also face EAA / EN 301 549 work. For a Title II conformance claim, document against the standard the rule cites unless counsel directs otherwise. For European WCAG 2.2 / EAA context, see our European Accessibility Act guide, European Accessibility Act compliance, and EN 301 549 v4.1.1 articles.

How should a small city or special district plan differently from a large state?

Same playbook, different pace. Small entities and special districts have until 26 April 2028, but they often have less staff. Inventory early, fix the few journeys residents cannot avoid (payments, applications, emergency info), and put WCAG 2.1 AA into every vendor renewal so the 2028 date is not spent rediscovering the same third-party failures.

How much does a Title II website accessibility audit cost?

It depends on how many sites, templates, apps and documents are in scope. On our pricing page, the $500 Quick Audit covers up to 5 templates with a top-10 issues report, and the $2,000 Complete Audit covers up to 25 templates or key user flows with full manual testing in JAWS, NVDA, VoiceOver and keyboard, a severity-ranked report and a re-test. Larger government portfolios and PDF libraries are quoted through our government accessibility audit request. If you are not sure of your scope yet, start with a free 30-minute call.

Do public hospitals and health agencies have a separate web accessibility deadline?

Often, yes. A public hospital run by a state or local government is covered by the Title II dates above. If it also receives HHS funding, the HHS Section 504 web rule applies too, and an HHS interim final rule of 11 May 2026 moved those dates to 11 May 2027 for recipients with 15 or more employees and 10 May 2028 for smaller recipients. Plan to the earliest date that applies to you. This is not legal advice; confirm with counsel. See our healthcare accessibility page for portal and patient-document testing.

Written by Shadab Saifi Published Last updated

Related Articles

View all