All resources
EbookBy Logan Nathan · Jul 2026 · 45 min read

The 2027 DOJ Deadline Survival Guide for Local Government

If you're the IT director, compliance officer, or city manager holding the ADA Title II bag inside a city, county, or municipality, this is the field manual. Read the rule, size up your risk, build the plan, then walk into the council meeting with something that isn't a shrug.

About This Ebook

82 pages. Published July 2026. Written by Logan Nathan for the people who actually have to execute compliance: IT directors, ADA coordinators, city managers, and the elected officials asking questions in Tuesday night meetings. No legal jargon. Real frameworks. Plans that fit agencies from 3,000 residents to 3 million.

What's Inside

Most ADA Title II resources fail in one of two ways. Lawyers write for lawyers, so the content is dense and useless at 4pm on a Thursday. Vendors write sales pitches wearing the costume of a guide. This one is neither. It's a working field manual for people executing compliance across the SLED sector(state, local, and education) with tight budgets, small teams, and a council that hasn't connected the dots on the risk yet.

Chapter 1Why This Deadline Is Different from Every Other Government Tech Mandate
Pages 1 to 14

Most government tech mandates arrive with money, guidance, and time. This one arrived with none of the three. Chapter 1 lays out why the ADA Title II web rule hits harder: enforcement runs through private complaints and DOJ investigation, there's no implementation funding, and WCAG 2.1 AA demands expertise most agencies don't have on staff. It also explains the political problem. You often can't build the will to act on this until a complaint lands, and by then you're on the back foot.

Key Insights

  • Why WCAG 2.1 AA is harder than Section 508
  • How DOJ complaints get triggered and what happens after
  • Why "we'll deal with it if a complaint comes" is the wrong strategy
  • The compounding cost of waiting: why earlier is cheaper
Chapter 2Who Must Comply and What Exactly Must Be Fixed
Pages 15 to 26

A precise read of the rule's coverage: which entities, which content, which exceptions. Chapter 2 gives you the language to answer department heads on the spot. Does this apply to the GIS portal? The employee intranet? The 2012 meeting minutes still sitting on the site? Each common scenario gets a decision tree. Content types get a straight table with their compliance status. No hedging.

Key Insights

  • The third-party vendor responsibility question answered definitively
  • Which archived content exceptions actually apply (and how narrow they are)
  • Mobile app coverage: what the rule says and doesn't say
  • How content posted by residents (comments, user submissions) is treated
Chapter 3The Urgency Reality Check: Where Your Agency Actually Stands
Pages 27 to 38

An honest self-assessment framework. Chapter 3 walks through the five ways agencies overestimate where they stand. Believing a WCAG-compliant template means WCAG-compliant content. Assuming an accessibility overlay tool counts. Treating a past audit as current evidence. Underestimating PDF volume. Assuming staff training actually changed publishing behavior. You get a scorecard to generate your own urgency rating in about 30 minutes.

Key Insights

  • Why accessibility overlay tools don't provide legal compliance
  • The "compliant template, non-compliant content" trap
  • What a 2021 audit tells you about your 2026 compliance status (not much)
  • How to estimate your PDF risk exposure in 30 minutes
Chapter 4The 6-Month Action Plan by Agency Size
Pages 39 to 56

The heart of the guide. Three detailed 6-month plans for three archetypes. Small municipality under 10,000 residents with 1 to 2 staff. Mid-sized city or county between 10,000 and 200,000, with 3 to 8 staff. Large agency at 200,000+ or multi-department with dedicated IT. Each plan lays out month-by-month milestones, who owns each piece, budget ranges, and success metrics. Templates included: internal project brief, vendor evaluation matrix, milestone tracking spreadsheet.

Key Insights

  • Month-by-month milestone plans for three agency sizes
  • What you can accomplish with a $5,000 compliance budget vs. $50,000
  • When to hire consultants vs. when to use platform tools
  • The minimum viable compliance path for the last 6 months before a deadline
Chapter 5Making the Case to Elected Officials and Leadership
Pages 57 to 68

This is the conversation IT directors dread. Explaining to a city council or county board why a website compliance project needs real money. Chapter 5 hands you the framing, the analogies, the risk language, and the specific numbers that land with elected officials. You get a 5-minute presentation script for council night, plus a one-page executive summary you can drop into a packet the morning of.

Key Insights

  • The liability framing: what a DOJ consent decree actually looks like
  • Comparing web accessibility cost to the cost of sidewalk ADA compliance (which council already approved)
  • How to answer "can't we just wait and see if a complaint comes?"
  • The budget justification language that works with finance officers
Chapter 6Vendor Evaluation: What to Ask, What to Require, What to Watch Out For
Pages 69 to 82

How to evaluate government CMS platforms for real accessibility compliance, not vendor claims about it. Chapter 6 gives you the 12 questions every CMS evaluation must ask, the red flags that should end a demo early, how to read a VPAT critically instead of taking it at face value, and the contract language that gives your agency recourse when a vendor's accessibility promises don't hold up in an audit.

Key Insights

  • The 12 CMS evaluation questions for accessibility compliance
  • 5 red flags that disqualify a vendor immediately
  • How to read a VPAT: what "Partially Supports" actually means
  • Contract language that gives you recourse when vendor accessibility claims are wrong

Page count by chapter

82 pages total

Chapter 4, the 6-month action plans by agency size, takes the largest share of the book.

Ch. 4: 6-Month Action Plan
18
Ch. 1: Why This Deadline Is Different
14
Ch. 6: Vendor Evaluation
14
Ch. 2: Who Must Comply
12
Ch. 3: Urgency Reality Check
12
Ch. 5: Making the Case
12
Chapter 4 runs 18 pages because it carries three month-by-month plans, one for each agency archetype.

Who This Guide Is For

City/County IT Directors

You brief leadership, evaluate vendors, and own the technical timeline. This is your playbook.

ADA Coordinators / Compliance Officers

You read the rule, coordinate the response, and document every step for the file.

City/County Managers

You approve the budget and answer for the risk when the council starts asking.

School District Technology Directors

You're juggling Section 504 and Title II at the same time, on a budget that doesn't stretch far.

Special District Administrators

No IT staff, no consultant on retainer, and a website that still has to be compliant.

Elected Officials

You get the one-page summary and the risk framing. Chapter 5 was written for you.

Chapter 4 agency archetypes by staff size

3 plans, one book

02468Staff on the plan1 to 23 to 8Dedicated ITSmallunder 10,000residentsMid-sized10,000 to 200,000residentsLarge200,000 plusor multi-department
Staff range on the compliance plan
Budget ranges scale with the team. Chapter 4 sizes the work from a $5,000 plan to a $50,000 plan.

Get the Full Ebook

Book a 30-minute demo. We'll walk you through the guide and show how WPPersona runs the Chapter 4 plan for an agency your size.

Schedule Demo to Get Access