Accessible public documents for towns, counties, school districts and special districts
Agents repair the PDFs (portable document format files) you post now and the forms people still use, then test every file against a listed set of WCAG 2.1 AA (Web Content Accessibility Guidelines 2.1, W3C Recommendation 05 June 2018, Level AA) and PDF/UA (PDF Universal Accessibility) checks. You get the fixed files and the test reports. Priced for small offices.
Plain fact: our sample files are machine-tested only. No human screen-reader test has been done yet.
Contact: coming soonSee pricing
Not legal advice. We report automated test results; we do not certify ADA (Americans with Disabilities Act) compliance.
Your documents are the hard part of the Title II web rule
In April 2024 the U.S. Department of Justice (DOJ) published a rule under Title II of the ADA. It requires state and local governments' web content and mobile apps to meet WCAG 2.1 Level A and AA (28 CFR 35.200). DOJ estimated 91,489 state and local government entities running 109,893 websites that the rule affects.
The compliance dates, as extended by DOJ in April 2026:
- April 26, 2027 for entities, other than special district governments, with a total population of 50,000 or more.
- April 26, 2028 for entities under 50,000 and for every special district government, whatever its size.
Documents count. PDFs, Word files, spreadsheets and slide decks on your website are "conventional electronic documents" under the rule (28 CFR 35.104).
Small offices feel it most. Clerks and part-time staff post agendas, minutes, fee schedules and permit forms every week, often as scans, and rarely have time to learn tagging tools.
The volume adds up even for larger governments. A Cass County, North Dakota staff memo (March 27, 2026) reported: "A recent analysis of 1,020 links across County web properties identified at least 802 documents that require accessible formatting" (county memo).
You don't have to fix everything
The rule lists exceptions (28 CFR 35.201). In plain terms:
- Usually covered: every document you post after your compliance date, and older documents people still use to apply for, get, or take part in a service (applications, permit forms, current fee schedules).
- Usually not covered: older documents posted before your date that nobody uses for a service; archived web content that meets all four parts of the definition in 28 CFR 35.104; certain content posted by a third party (unless the third party is posting because of a contractual, licensing, or other arrangement with your entity); documents that are both about a specific individual, their property, or their account and password-protected or otherwise secured; and pre-existing social media posts.
So we start with what the rule covers: your new postings and your in-use forms. Back-catalog cleanup is optional, quoted separately, and is a decision for you and your counsel. This is a summary, not legal advice.
What you get
- The repaired files. Agents fix tags, headings, reading order, tables, form field names, document title and language, and alt text (text descriptions of images). Scanned pages get real, searchable text. Where it helps, an accessible HTML (web page) version too.
- A machine validation report for every file: veraPDF PDF/UA-1 output (veraPDF is an open-source PDF checker) plus our structure check.
- A color-contrast report (automated).
- A text-fidelity check confirming the words in the fixed file match the original.
- A screen-reader simulation transcript, clearly labeled as a simulation, not a human test.
- A plain-English summary you can file with your accessibility records: what was tested, on what date, with which tools, and what still needs a person to check.
We don't sell an overlay or widget. We fix the document itself.
How it works
- Send a list or links. Tell us which documents you post regularly and which forms are in use.
- Agents repair and test. Each file is fixed and run through the listed checks.
- You review and post. You get the files plus every report. Anything a machine can't judge (is this alt text accurate? does this reading order make sense out loud?) is flagged for a person.
What a first batch looked like
We tested the approach on 6 public PDFs from small-city websites (42 pages): meeting minutes, newsletters, a scanned fee table and a fillable building-permit form.
| Measure | Before | After |
|---|---|---|
| Failed automated checks (veraPDF PDF/UA-1 plus structure checks) | 2,690 | 0 on all 6 files (Nov 18, 2026) |
| Scanned fee table | Image of a table | 22 real data tables with headers |
| Building-permit form | Unnamed fields | 43 fields, each with a spoken name |
How our sample files were tested (plain facts): the sample files were agent-tested. That means automated checks only: veraPDF PDF/UA-1 validation (0 failed checks on every sample file), an automated color-contrast check, an automated screen-reader check (a script that reads each file's tag tree), and an agent-driven run of the free Orca screen reader. No person using a screen reader has tested these files yet. Human screen-reader testing is pending. Passing automated checks does not by itself mean a document works for every user.
See a sample report (PDF, 2 pages, automated checks only). It covers the 6 desk-test files and lists which checks a machine did and which still need a person.
Who it's for
- City and town clerks who post agendas, minutes and notices.
- ADA coordinators building a Title II plan.
- Communications and IT (information technology) staff who run the website.
- School district and county offices under 50,000 population, and every special district government (water, fire, parks, library, transit districts) whatever its size, all with the April 26, 2028 date.
- Larger entities with the April 26, 2027 date are welcome to get in touch once contact opens.
Pricing
Offer prices for the agent-checked service. No checkout on this site. Any paid work is done under a written quote.
Agent-checked, per page
$1.00 per page
$5 minimum per document. Repaired file plus all automated reports.
Human-checked
Coming later
A person tests each file with a screen reader. Not available yet; we'll offer it only after our own human testing process is in place and logged.
Questions
When do we have to meet the Title II web rule?
It depends on your total population as the rule defines it (generally the Census Bureau figure; school districts use the Census Small Area Income and Poverty Estimates). Entities of 50,000 or more, other than special district governments: April 26, 2027. Under 50,000, and all special district governments whatever their size: April 26, 2028. DOJ moved these dates back one year in April 2026. A lawsuit, National Federation of the Blind v. Department of Justice, No. 1:26-cv-02007 (D. Md.), challenges the April 2026 extension; when we checked the CourtListener docket on November 21, 2026, the court had not ruled, so these dates could change. Check ADA.gov before you plan. Not legal advice.
What standard do the documents have to meet?
WCAG 2.1 (W3C Recommendation 05 June 2018), Level A and Level AA success criteria, as incorporated in 28 CFR 35.104 and 35.200.
Do our old PDFs have to be fixed?
Often not. Documents posted before your compliance date are generally exempt unless people currently use them to apply for, get, or take part in a service. Forms and current fee schedules usually fall in that group. Ask your counsel about anything unclear.
Will this make us "ADA compliant"?
No vendor can promise that, and we don't. We repair files and report which listed automated checks each file passed and on what date. Compliance depends on your whole website, your processes, and how you respond to requests. Not legal advice.
Is a person testing the files with a screen reader?
Not in the current (agent-checked) service. Each file ships with a screen-reader simulation transcript, labeled as such. A human-checked option will come later.
How is this different from a $1-per-page tool or a website widget?
Agents also fix reading order, tables and form fields, and every file comes with its test outputs, so you can see what was checked. We don't use overlays.
What do you need from us?
Public links to the documents, or the files. We only work on documents you choose to publish. We don't need logins.
Can you convert PDFs to web pages instead?
Yes, where that makes sense (for example, agendas and minutes), we can deliver an accessible HTML version alongside the PDF.
How long does it take?
In our desk test, machine processing took about 0.1–1.3 seconds per document, plus OCR (optical character recognition, turning a scan into text) time for scans. Turnaround for real batches is not set yet.
Get in touch
Contact is coming soon. When it opens, you'll be able to ask for a free sample report on one of your public PDFs.
No checkout, no obligation. Not legal advice.