🏛️ Government & Public Sector

Government Websites Have Two Title II Deadlines: April 2027 and April 2028

By Compliapoint · Last reviewed

The Department of Justice’s 2024 Title II rule requires state and local government web content and mobile apps to meet WCAG 2.1 Level AA. An interim final rule published April 20, 2026 pushed both compliance dates back a year. Which one is yours depends on your population, or on whether you are a special district.

Compliapoint works on WordPress (including WooCommerce) and Shopify sites.

Apr 26, 2027total population 50,000 or more
Apr 26, 2028under 50,000, and every special district
WCAG 2.1 AAthe standard the rule names
2platforms we fix at source: WordPress and Shopify

Which Title II Deadline Is Yours

🏛️

April 26, 2027

A state, and any city, county or other public entity whose total population is 50,000 or more. Special districts are excluded from this tier whatever their size.

🏘️

April 26, 2028

Any public entity whose total population is under 50,000: most villages, towns, townships and small counties, and independent school districts below the line.

💧

April 26, 2028, at any size

Every special district government: a single-purpose public body such as a water, fire or library district, which the rule places in the later tier regardless of population.

“Total population” is a defined term. For most entities it is the most recent decennial Census count. An independent school district uses the Census Bureau’s Small Area Income and Poverty Estimates instead. A transit or other authority created by several governments takes their combined Census population, which can put a small-sounding authority in the 2027 tier.

Both dates are in 28 CFR 35.200, as amended by the interim final rule at 91 FR 20902. Before that rule, the dates were April 24, 2026 and April 26, 2027, which is why much of what is still online gives April 2027 as the deadline for smaller entities too.

If you are in the 2028 tier, plan for 2028

A township clerk or a fire district reading “April 2027” on a vendor’s site could believe there are six months left when there are eighteen. We would rather you used that year to do the work properly, documents and video included, than rushed it to beat a date that does not apply to you.

The rule also covers content you provide “through contractual, licensing, or other arrangements,” so a vendor-hosted payment portal or an online store is yours to answer for. The exceptions, including archived content and older documents, are set out on our Title II compliance guide.

What the Title II Rule Means in Practice

Government websites and mobile apps must be fully accessible to residents with disabilities. This includes city websites, county portals, public transit sites, court systems, permitting systems, public library sites, parks and recreation registration, emergency alert systems, and every other digital service a government provides.

The standard is not aspirational — it's a federal mandate. Title II has always covered a government's services, programs and activities, and its website is one of them. What the 2024 rule added was a named technical standard and a date by which to meet it.

⚠️ After Your Date: What Changes

Once your compliance date passes, a resident who cannot use your site can point to a specific standard and a specific date, in a complaint to the Department of Justice or in a lawsuit. The rule does let an entity show that full compliance would fundamentally alter a service or impose an undue financial and administrative burden; whether that applies to you is a question for your counsel, not for us.

🇺🇸 Why U.S.-Based Matters for Government

Government agencies — especially those handling sensitive constituent data — should know who is touching their site. Compliapoint is based in the United States, does the work itself, and keeps your engagement’s data on servers in the United States. And because we fix your code rather than install a widget, no third-party script ends up running on your pages and reading what residents type into them.

Common Violations in Government Websites

WCAG 1.1.1

Image-Heavy PDFs & Documents

Government forms, ordinances, meeting minutes, and public notices as scanned image PDFs with no accessible text.

WCAG 2.4.4

Vague Navigation Links

Links like 'Click Here', 'Read More', and 'Download' with no context — a major screen reader problem.

WCAG 1.2.2

Council Meeting Videos

City council, board meetings, and public hearings posted as video without captions. A livestream is a separate requirement: live captions under 1.2.4, a Level AA criterion, and real-time captioning is not a service we provide.

WCAG 1.4.3

Low Contrast Site Text

Aging government website designs with poor contrast ratios that haven't been updated in years.

WCAG 3.1.1

No Language Declaration

Multi-language government sites without proper lang attributes — screen readers use the wrong language engine.

WCAG 2.4.1

Complex Page Navigation

Large government portals with extensive navigation and no skip-to-content links.

How Government Sites Fail: Three Illustrations

📋

The Permit Application Trap

A resident with low vision tries to submit a building permit application online. The PDF form is a scanned image — not fillable, not readable by screen readers. They must drive to City Hall, take time off work, and wait in line. The rule’s exception for documents posted before your compliance date does not reach this one, because it is used to apply for a service.

🎬

The Inaccessible Council Meeting

Your city posts council meeting recordings to YouTube without captions. A deaf resident cannot follow local governance. Recordings posted after your compliance date need captions. An older one escapes only as archived content: kept for reference, unchanged, and stored in an area clearly marked as an archive.

🚨

The Emergency Alert Failure

During a wildfire evacuation, your alert opens in a modal dialog with no accessible name, and keyboard focus never moves into it. A blind resident cannot reach the evacuation instructions. That fails WCAG 4.1.2 and 2.4.3, and on that page it is also a safety failure.

Your Deadline Does Not Care Which CMS You Run

Many government sites run on vendor platforms such as CivicPlus or Granicus, where only the vendor can change the code; our Title II guide explains what we can still do for you there. Many others, especially smaller towns, districts and agencies with no full-time web team, run on WordPress. That is one of our two core platforms.

A government WordPress site is usually not one build. It is a theme someone chose years ago, a child theme a vendor bolted on, a dozen plugins rendering forms and document libraries and meeting calendars, and years of uploaded PDFs. Each layer introduces WCAG violations, and the Title II deadline applies to all of them.

We audit against WCAG 2.2 AA; per W3C, 2.2 keeps every 2.1 success criterion except 4.1.1 Parsing, which it made obsolete. Then we fix each failure in the layer that produced it: the child theme, the plugin template or the content, not an overlay widget. Specializing in WordPress and Shopify is what lets us go past the report and into the code.

🖥️ Platform Support

  • WordPress — Full WCAG audit plus source-code remediation in your theme, child theme and plugin templates
  • Shopify, where it fits — some entities sell park passes, event tickets or visitor-center merchandise through a Shopify store. That store is web content you make available, so the same date applies. We fix the theme; Shopify’s checkout is Shopify’s code, so we test it and document it for you to raise with them
  • Documents — PDF remediation at $6.38 a page, quoted on your page count, and a VPAT/ACR for $298. Title II covers the documents you post; Section 508 binds federal agencies, and reaches a city or county through state law or a federal contract
Why This Matters for Procurement

If your agency runs WordPress, you don't need to switch platforms to get compliant. We audit what you already have and fix it in place — no CMS migration, no overlay widget, no vendor lock-in. Meeting-calendar, agenda and document-library plugins are where government WordPress sites most often differ from anyone else’s, and they are part of the audit, not left out of it.

What Compliapoint Fixes for You

  • Remediates PDF documents — forms, ordinances, meeting minutes, public notices — starting with the ones residents use to apply for something
  • Captions recorded meetings and hearings, delivered as SRT and VTT files, quoted per project
  • Fixes navigation links with descriptive, contextual text
  • Corrects color contrast across all government portal pages
  • Adds proper language declarations for multilingual government sites
  • Prepares a VPAT/ACR for procurement and audit files
  • Maps findings to Section 508 in the ACR, for contracts that require it
  • Covers every department’s pages within the scoped site in one engagement; there are no seats or licenses, because we deliver work, not software
✅ Source Code Fixes — Not a Widget

Every fix Compliapoint makes is written directly into your site's code. No JavaScript overlay. No band-aid. What we tested and changed is set down in a dated Test Record, which names the theme and plugin versions in place on that date.

🗳️ Built for a Board or Council Vote

You get a fixed price in a written proposal, valid for 30 days, before anything is owed. We accept ACH, company check and credit card. Nothing renews on its own: monitoring is the only recurring service, and it is optional.

Professional Remediation Service

  • Full WCAG 2.2 AA Accessibility Audit
  • Source-level code remediation — not an overlay
  • PDF & document remediation
  • Video caption services
  • VPAT / ACR for procurement files
  • Dated Accessibility Test Record, and a 30-day recheck in every Complete Package
  • No obligation until you approve the written proposal
Start Your Assessment

We review your site and confirm scope before any work begins

Plan the Work Around the Date You Actually Have

Once work starts, standard turnaround is 7–10 business days. What usually takes longer is approval: a budget line, a vote, a purchase order. Start the assessment and you will have a fixed written price to put in front of that vote.