For cities and counties
Accessible agendas, minutes and forms for cities and counties.
50,000+ population: April 26, 2027 · Under 50,000: April 26, 2028
The DOJ's ADA Title II rule reaches the documents your clerk publishes: agenda packets, minutes, budgets, permit forms, public notices. From your compliance date they have to be accessible, along with the older files residents still use.
DocoMatic remediates them on your publishing schedule and proves every file with a verification report.
Free scan, no account. Trial: 100 credits, 14 days, 10 documents, no card.
- 50,000 or more
- 7 months to April 26, 2027
- Under 50,000
- 19 months to April 26, 2028
Whole months from today, by your city or county's last decennial Census count.
The rule and the two dates
The rule reaches the clerk's office first
Not every old PDF has to be fixed
The rule has exceptions, at 28 CFR 35.201(opens in new tab). Documents posted before your compliance date are excepted unless they are currently used to apply for, gain access to, or participate in your services, programs or activities; so is archived content kept only for reference, research or record-keeping in a clearly identified archive, third-party content, and a password-protected document about one person — a resident's own permit or bill. How the archive work gets ordered is below.
The Department of Justice's 2024 final rule under ADA Title II requires state and local government web content, including posted documents, to meet WCAG 2.1 Level AA. Cities, counties and townships of every size are covered; the requirement is at 28 CFR 35.200(opens in new tab).
Entities with a population of 50,000 or more must comply by April 26, 2027; smaller cities, towns and townships have until April 26, 2028. The cohort is determined by Census population figures — the entity's own, under 28 CFR 35.104(opens in new tab).
The clerk's office feels this first: agenda packets go out on a legal timetable, and a single packet can run hundreds of pages. A rule that covers documents effectively covers the weekly publishing cycle — which is why remediation has to happen at publish time, not as an annual cleanup project.
| Compliance date | Applies to | Basis |
|---|---|---|
| April 26, 2027 | Cities and counties with 50,000 or more residents | The entity's own count in the last decennial Census — a county's, not its cities' or the metro's |
| April 26, 2028 | Cities, towns and townships under 50,000 — most US municipalities | The same figure. A small city in a large county keeps its date; a city-run department follows the city |
Both dates: the Department of Justice's interim final rule of April 20, 2026(opens in new tab), 91 FR 20902 (April 20, 2026), amending 28 CFR 35.200(b).
A self-governing district? See special districts, school districts, or all solutions by organization type.
- The current dates are set91 FR 20902 (April 20, 2026), amending 28 CFR 35.200(b)
- ADA Title II, population 50,000 or moreCities and counties with 50,000 or more residents
- ADA Title II, under 50,000, and every special districtCities, towns and townships under 50,000 — most US municipalities
Sources
Every regulatory claim on this page is cited to one of these primary sources.
- ADA Title II compliance-date extension, Federal Register, April 20, 2026 (91 FR 20902)
- ADA Title II final rule, Federal Register, April 24, 2024 (dates since extended)
- US Census Bureau population estimates
- DOJ fact sheet: ADA Title II rule on web and mobile accessibility (ada.gov)
- ADA.gov — DOJ information and technical assistance
What you publish
The documents cities and counties publish
Agenda packets and minutes
Published on a statutory timetable and often several hundred pages from several departments — the highest-volume, highest-frequency, lowest-notice publication a city produces.
Monitoring picks each packet up from the URL it publishes to, so the cycle stays covered without your clerk adding a step.
The expensive pages in a packet are usually the inserts — a permit form, a scanned plat, a signed exhibit. The level is set per document: a packet with a fillable form is recommended for Level 3 as a whole, credit estimate shown first.
Permit and service forms
Building permits, business licenses, records requests — fillable forms with labeled fields and a logical tab order. Forms are Level 3.
Budgets and financial reports
Table-heavy documents where header tagging decides whether your residents using screen readers can read the numbers at all.
Public notices and ordinances
Legally required publications that must be readable by every resident they notify.
Staff reports and plans
Maps, charts and figures that need meaningful alt text and a correct reading order.
The publishing cycle
One agenda cycle, start to finish
What happens next Friday, and how much lands on your team.
| When | What happens | Who does it |
|---|---|---|
| Friday, the packet publishes | Your clerk posts the packet exactly as today. Nothing changes upstream. | Clerk — no change |
| The next scan | Monitoring finds and checks the new file — weekly or monthly on Growth, daily on Scale, or on Scan now. | Nobody |
| One click | Send the packet on; the recommended level and credit estimate come first. Nothing is remediated, or billed, because a scan found it. A connection with remediate-on-ingest on skips this step. | ADA coordinator, a minute |
| Back in your queue | The remediated packet arrives with its verification report. A scanned insert or an ambiguous map is flagged there for a person; human review is one switch. | ADA coordinator, minutes |
| You replace the posted file | The replacement list pairs the original URL with the verified file; publish it in place of the original. We never write to your site. | Clerk, minutes |
| Next cycle | Routine. | — |
What your team actually does: choose what gets remediated, and replace the published file.
What doesn't change: where packets are assembled, who assembles them, or the tools they are built in.
How it works
Built around the clerk's publishing cycle
Step 1
Connect your domains
We crawl your public sites and build a live inventory of every document. If your packets publish somewhere our crawler cannot reach, point us at the published packet URLs or push them to us over our webhook ingest API (for developers).
Step 2
Remediation runs on publish
Your clerk publishes as usual. The next scan finds each new packet, form or notice; one click sends it to be remediated to WCAG 2.1 AA and PDF/UA — automatically over a connection with remediate-on-ingest on. See one cycle.
Step 3
Your ADA coordinator approves
Flagged files — complex forms, maps, ambiguous figures — go to human review with a clear record of what changed.
Step 4
Verified files, ready for the record
Every document carries a verification report and audit trail fit for a council packet or a compliance inquiry.
The archive question
What about decades of archived minutes?
The rule reaches the documents people still use to reach services, not every file that has ever existed. So the honest answer is an order of work — document monitoring's own ranking.
Remediate first
Anything linked from current navigation, any form a resident must complete, anything from the last year or two.
Remediate next
Older documents still linked from live pages; the inventory shows which.
Consider leaving
Minutes from 2004 in a clearly marked archive, linked from nowhere current. The inventory shows where each file is linked and when it last changed, so you are not quoted for all of them.
Not legal advice — your counsel decides what your obligation reaches; this is how the work is sequenced so the first invoice is affordable.
Sizing it first is free. Scan a domain — start with the clerk's site.
From the registry
See your city or county backlog
Our scanner counts the public documents on a city or county website; run the free scan for yours.
A surveyed city or county
We are surveying entities state by state.
No city or county in the launch states has a published survey yet. Scan your own site now and you will have the number in minutes — we do not need to have crawled you first.
Look up a city or county
Per page, in credits
Pricing for municipal volume
Priced per page by level, at published credit rates: a backlog pack for the archive, then a monthly plan for the publishing cycle.
Worked example: a city of 60,000, 39,040 pages
| Level | Pages | Per page | Credits |
|---|---|---|---|
| Level 1 — text | 36,000 | 1 | 36,000 |
| Level 2 — tables and images | 3,000 | 4 | 12,000 |
| Level 3 — fillable forms | 40 | 30 | 1,200 |
| Human review on the forms | 40 | 10 | 400 |
| Total | 39,040 | 49,600 |
The 50,000-credit backlog pack is $9,000.00 — $0.18 a credit, 24 months — and covers this backlog.
For the publishing cycle, Growth is $999.00 a month for 4,000 credits and 3 monitored domains.
An estimate, not a quote.
You are not charged for a document that fails verification. How the no-charge rule works.
How cities and counties buy
Card payment opens with our billing launch; today plans and credits are arranged by quote and paid by purchase order.
Net-30 to net-60 by ACH; a W-9 on request; no cooperative purchasing contract yet.
FAQ
City and county questions
Buying for a larger organization?
Book a 20-minute demo(opens in new tab)When is the ADA Title II deadline for my city or county?
Do agenda packets really have to be accessible?
What about decades of archived minutes?
Will this slow down agenda publishing?
How does the cost compare to remediation services?
Do you need access to our website or our CMS?
How many domains does a plan cover?
Our district is run by the city — same deadline?
Start with a count
Make the next agenda packet accessible
Start with 100 free credits — around 100 simple pages or 25 complex ones, across up to 10 documents in 14 days. Or scan your site first.