The complete municipal guide to the ADA web rule
Deadlines, covered content, PDF requirements, the exceptions and their fine print, and answers to the questions every city asks — in plain language, sourced from the rule itself.
Entities 50,000+April 26, 2027
Entities under 50,000 & special districtsApril 26, 2028
Required standardWCAG 2.1 Level AA
Private lawsuitsPossible today — the deadline is not a shield
The rule at a glance
In April 2024, the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act requiring all state and local government web content and mobile apps to conform to WCAG 2.1 Level AA. In April 2026 the compliance dates were extended — but every substantive requirement stayed exactly the same, and the DOJ stated it fully anticipates implementing the rule at the new deadlines.
Who must comply
Every state and local government entity — with no exemption for size. If it's government-run and has a digital presence, the rule applies.
Municipalities & counties
Cities, towns, villages, townships, boroughs, and county governments — every department, from the clerk's office to parks and rec, police, fire, and courts.
Special districts
Water and sewer districts, transit authorities, library systems, port and park districts — independent special-purpose governments are explicitly covered, on the 2028 timeline.
Schools & public institutions
Public school districts, community colleges, public universities, and public hospitals — including course content, portals, and enrollment systems.
What content is covered
The rule reaches everything a public entity provides "directly or through contractual, licensing, or other arrangements" — meaning your vendors' failures are your liability.
Websites & apps
Every public-facing page, portal, and mobile app — navigation, forms, search, payment flows.
Documents
PDFs, Word files, spreadsheets, presentations — agendas, minutes, budgets, applications, permits.
Audio & video
Council meeting recordings and published video need captions; live-audio content needs them in real time.
Social media
Posts made after your compliance date must conform — alt text on images, captions on video.
Vendor systems
Utility billing, agenda platforms, recreation registration, permit portals — contracted content counts as yours.
The standard: WCAG 2.1 Level AA
The Web Content Accessibility Guidelines organize roughly 50 testable success criteria under four principles — content must be:
Perceivable
- Text alternatives for images
- Captions for video
- Sufficient color contrast
- Content that reflows on zoom
Operable
- Everything works by keyboard
- No keyboard traps
- Visible focus indicators
- Enough time to complete tasks
Understandable
- Labeled form fields
- Clear error messages
- Consistent navigation
- Declared page language
Robust
- Valid, semantic markup
- Works with screen readers
- Compatible with assistive tech
The failures audits find most often on municipal sites
- Scanned-image PDFs with no readable text layer
- Images and charts without alt text
- Online forms with unlabeled fields
- Payment portals that can't be completed by keyboard
- Meeting videos without captions
- Link text like "click here" with no context
- Color contrast below the 4.5:1 minimum
- Heading structures that skip levels or don't exist
- Tables used for layout that scramble screen-reader order
- Focus indicators removed by the site's stylesheet
- Time-limited sessions that expire without warning
- Maps and calendars with no accessible alternative
PDFs: where most municipal compliance lives or dies
The average city publishes hundreds to thousands of PDFs — agendas, minutes, budgets, applications. A PDF is only accessible if it's built or remediated to be; printing to PDF or scanning paper produces a document a screen reader cannot use.
What an accessible PDF has
- A real text layer (not a picture of text)
- Tags defining headings, lists, and tables
- A logical reading order
- Alt text on images and charts
- Labeled, fillable form fields
- A document title and language setting
The carve-out that catches cities
Documents created before your compliance date are exempt — unless they're currently used to apply for, access, or participate in your services. Your 2021 permit application, utility connection form, and recreation packet are in active use, so they must conform no matter their age.
The practical strategy
Inventory every published document, separate genuinely exempt files from active-use ones, remediate what must conform, and fix the workflow so tomorrow's uploads come out accessible. Triage typically cuts the remediation scope dramatically.
The exceptions — and their fine print
The rule includes limited exceptions. Every one is narrower than it sounds, and misreading them is the most common compliance-planning mistake.
Archived web content
Exempt only if it meets all four conditions:
- Created before your compliance date (or reproduces pre-date paper records)
- Kept only for reference, research, or recordkeeping
- Stored in a dedicated, clearly identified archive section
- Unchanged since it was archived — one edit voids the exception
Old minutes mixed into a general "Documents" page are not archived — they're just old content, and they must conform.
The other exceptions
- Preexisting documents — unless in active use for services (see the PDF carve-out above)
- Third-party content — posted by the public, not by your vendors or contractors
- Individualized password-protected documents — e.g., a specific resident's water bill
- Preexisting social media posts — everything after your deadline must conform
Even exempt content must be made accessible on request if a person with a disability needs it to access services.
Common questions
Our town has 3,000 residents. Does this really apply to us?
Yes. There is no small-entity exemption — only a later deadline (April 26, 2028, for entities under 50,000 and special districts). The requirements themselves are identical for every entity.
The deadline was pushed back once. Will it be pushed again or repealed?
No one can promise either way — but when the DOJ extended the dates in April 2026, it left every requirement untouched and stated it fully anticipates implementing the rule at the new deadlines. And regardless of the rule's fate, the underlying ADA obligation and private right of action already exist.
Can we just put a phone number on the site for people who can't use it?
Not anymore. The rule requires proactive conformance to WCAG 2.1 AA — an accommodation-on-request workaround means residents with disabilities get services on slower, different terms, which is the exact inequality the rule was written to end.
Does WCAG 2.2 replace 2.1? Should we wait?
The legal standard in the rule is WCAG 2.1 AA. Newer versions only add criteria on top — everything remediated for 2.1 counts toward 2.2 — so waiting buys nothing and shrinks your runway.
Our website vendor says we're already compliant. Are we done?
Ask three things in writing: will they certify WCAG 2.1 AA conformance in the contract and indemnify you if it fails; can they show a manual assistive-technology testing report with dates; and what's their remediation commitment when new content breaks conformance. Under the rule, the liability for vendor-provided content sits with the public entity — not the vendor's marketing materials.
What happens if we miss the deadline?
Two exposure paths: federal enforcement by the DOJ, and — more common in practice — private lawsuits and demand letters from residents, which can begin before the deadline. Remediation done on your own schedule is a budget line; remediation under a settlement is a crisis with legal fees attached.
Do our old council meeting videos need captions?
Video posted before your compliance date may fall under the preexisting-content exception if it isn't needed to access current services; everything published after your deadline needs captions. Many entities caption going forward and handle older videos on request.
Where do we even start?
With an audit. You can't budget, prioritize, or defend what you haven't measured. A written gap analysis against WCAG 2.1 AA tells you what fails, what's exempt, and what it takes to close the gap — and it's the document your council needs to approve the spend. Ours is free.
Official resources
Don't take our word for it — the primary sources, straight from the government and the standards body:
This page is provided for general information and is not legal advice. Deadlines and requirements are summarized from the DOJ's rule as of mid-2026; consult the primary sources above and your municipal attorney regarding your entity's specific obligations.
From first scan to defensible record
A sequence, in the order it actually happens — and the audit costs you nothing either way.
We scan, then we test
Automated audit of your full web presence, followed by manual testing with screen readers and keyboard-only navigation. You get a written gap analysis against WCAG 2.1 AA — free, whether or not you hire us.
Fix what fails, document what passes
We rebuild or remediate the failures, separate genuinely exempt content from must-fix content, and structure your archive so the rule's exceptions actually apply.
Stay conformant, stay covered
Ongoing monitoring, accessible publishing workflows for your staff, and a living conformance record — testing methodology, dates, results — ready before anyone asks for it.