You're facing a specific choice: which compliance date applies to your entity under the DOJ's Interim Final Rule extending the Title II web accessibility deadlines. This choice dictates your planning timeline, resource allocation, and documentation strategy for the next 12 to 36 months.
This isn't about whether to comply. The Department of Justice has made it clear that covered entities must ensure their services, programs, and activities offered through web content and mobile apps are accessible to individuals with disabilities under Title II. The extension only changes when formal conformance to WCAG 2.1 Level AA must be complete.
Here's how to determine your path and what it means for your program.
The Decision You're Facing
Your entity falls into one of three categories under the Interim Final Rule:
- Category A: State or local government entity serving a population of 50,000 or more
- Category B: Public entity serving a population under 50,000
- Category C: Special district government (regardless of population)
Each category has a different compliance date. Getting this wrong means either rushing unnecessarily or missing a hard deadline.
Key Factors That Affect Your Choice
Population count matters, but it's not always obvious. If you're a county government, count the total county population. If you're a city within that county, count only the city's population. Multi-jurisdictional entities need to determine which jurisdiction's population threshold applies to each service they offer.
Special district status overrides population. Fire districts, water authorities, transit agencies, and similar entities typically qualify as special districts. If you're unsure whether you meet this definition, check your enabling legislation or consult your legal counsel. Special districts get the longest runway regardless of how many people they serve.
Your obligation started before any of these dates. The extension affects when you must demonstrate full WCAG 2.1 Level AA conformance. It doesn't create a safe harbor for accessibility complaints filed before your deadline. If someone requests an accessible version of a document today, you're required to provide it.
Path A: April 26, 2027 (Population 50,000+)
If you serve 50,000 or more people, your compliance date is April 26, 2027.
When to choose this path:
- You're a state agency (all state agencies fall here by default)
- You're a county with 50,000+ residents
- You're a city with 50,000+ residents
- You're a regional authority serving multiple jurisdictions whose combined population exceeds 50,000
What this timeline requires: You have roughly 12 months from publication of this article. That's enough time to complete a baseline audit, prioritize high-impact pages, remediate critical barriers, establish an accommodation request process, and document your progress. Don't waste time on vendor evaluations that go nowhere or pilot programs that never scale.
Start with your most-used services: permit applications, payment portals, public meeting agendas, and emergency notifications. These typically account for 80% of user interactions even if they represent 20% of your total pages.
You'll need a system to track accommodation requests. The DOJ acknowledged that during the extension period, individuals with disabilities may need to request accessible versions of certain electronic documents and wait for those requests to be fulfilled. That means you need a documented process for receiving, routing, fulfilling, and logging those requests before your deadline arrives.
Path B: April 26, 2028 (Population Under 50,000, Non-Special Districts)
If you serve fewer than 50,000 people and you're not a special district, your compliance date is April 26, 2028.
When to choose this path:
- You're a small city or town
- You're a county with fewer than 50,000 residents
- You're a local government entity that doesn't meet special district criteria
What this timeline requires: You have roughly 24 months. Use the first year to build infrastructure: establish governance, train staff, document your current state, and create a remediation workflow. Use the second year to execute fixes and validate conformance.
The longer timeline doesn't mean you can defer accommodation requests. If a resident asks for an accessible version of a tax form in June 2026, you must provide it then, not in 2028. Treat your extended deadline as time to build systemic capability, not as permission to ignore individual requests.
Smaller entities often lack dedicated accessibility staff. That makes process design more important, not less. You need a workflow that doesn't depend on one person remembering to check contrast ratios or test keyboard navigation.
Path C: April 26, 2028 (Special District Governments)
If you're a special district government, your compliance date is April 26, 2028, regardless of population.
When to choose this path:
- You're a fire district
- You're a water or wastewater authority
- You're a transit agency
- You're a school district
- You're any other entity created under special district enabling legislation
What this timeline requires: Special districts often operate with lean IT teams and limited budgets. The 24-month window acknowledges that reality, but it doesn't change the technical requirements. You still need to meet WCAG 2.1 Level AA.
Focus on the digital services that matter most to your constituents. For a fire district, that might be burn permit applications and public safety notices. For a transit agency, it's route maps, service alerts, and fare information. Don't try to remediate every page Assistive Technology once. Prioritize based on user impact and legal risk.
Many special districts rely on third-party vendors for website hosting and content management. Review your vendor contracts now. If your provider can't demonstrate WCAG conformance, you need time to migrate before your deadline.
Summary Matrix
| Entity Type | Population Threshold | Compliance Date | Planning Window (from now) |
|---|---|---|---|
| State/local government | 50,000 or more | April 26, 2027 | ~12 months |
| State/local government | Under 50,000 | April 26, 2028 | ~24 months |
| Special district | Any | April 26, 2028 | ~24 months |
Applies to all paths:
- Ongoing obligation to provide accessible content when requested
- WCAG 2.1 Level AA is the standard
- Private right of action exists under Title II
- Extension applies to formal compliance date, not to underlying nondiscrimination obligation
What Happens Next
Determine your category, mark your calendar, and start building your conformance record now. The extension bought you time to do the work properly. It didn't change what the work is or whether you're required to do it.
If you're tracking accommodation requests manually in email or spreadsheets, that system will break under load. If you're running automated scans but not validating the results with manual testing, you're missing barriers the scanner can't detect. If you're remediating pages without documenting what you fixed and when, you can't demonstrate progress when someone asks.
The deadline is real. The obligation is older. Use the time you have.
