On a city, county or district website the PDFs are usually the largest single accessibility problem, larger than the theme and the forms combined. Agendas, minutes, packets, rate schedules, permit applications, annual reports: hundreds or thousands of documents, most of them exported without tags or scanned as images. The ADA Title II rule treats every one of them as web content. Start there, because the fix is mostly a change in how documents get made, and the sooner it changes the fewer you have to repair by hand.
Why PDFs are the biggest ADA problem on a government site
Count them. A mid-sized city posts an agenda and a packet for every council meeting, every planning commission, every board and every committee, plus minutes for each, plus the budget, the audit, the comprehensive plan, the zoning code, the fee schedule, every permit and application form, and every press release someone decided to upload as a document. Five years of that is easily 2,000 files. Most cities we look at have never counted.
Those files fall into two kinds. Scanned documents (a signed resolution, an old ordinance, anything that came through a copier) are images. A screen reader reads nothing. Exported documents (Word or InDesign to PDF) have text, so the words can be read aloud, but without tags there are no headings to move between, no reading order across columns, no table structure, and no way to know what a picture shows. On a 300-page packet that is the difference between a document and a wall.
The ADA Title II rule makes no distinction between a page and a document. WCAG 2.1 AA applies to both, and the criteria a PDF fails are the same ones a page fails: text alternatives, structure and relationships, reading order, page title, language, contrast. Our post on where government WordPress sites fail WCAG covers the page side; this one is about the documents.
What the document exception covers, and what it does not
The rule exempts "preexisting conventional electronic documents": Word, PDF, spreadsheet and presentation files that were available on the site before your compliance date. Read carefully, the exception does less than most people hope.
It only covers documents posted before the date. Everything posted after April 26, 2027 (population 50,000 or more) or April 26, 2028 (everyone else, and every special district) has to conform from the day it goes up. Every future agenda packet is inside the rule.
It ends the moment the document is "currently used" by residents to apply for, gain access to, or participate in a service, program or activity. A permit application from 2018 is still in use; it is covered. The zoning code residents consult before applying is covered. Last year's fee schedule that is still the fee schedule is covered. What the exception protects is the archive: past minutes, old reports, superseded plans.
It does not cover a document you edit. Update an exempt file and it is a new document.
A separate exception covers archived web content, but only if it sits in a labelled archive, is kept for reference, has not been changed, and was created before the date. Moving old minutes into a clearly labelled archive section is a legitimate way to use it. Leaving them mixed into the current meetings list is not.
What makes a PDF accessible
The technical standard for accessible PDF is PDF/UA (ISO 14289), and meeting it satisfies the parts of WCAG 2.1 AA that apply to documents. In practice a document needs the following.
| Requirement | What it means | The usual failure |
|---|---|---|
| Real text | Characters, not an image of characters | Scanned documents with no OCR |
| Tags | A structure tree marking headings, paragraphs, lists, tables | Exported with tags turned off, or from a tool that cannot make them |
| Reading order | The tags follow the order a reader would read | Two-column layouts read across instead of down |
| Headings | H1, H2, H3 in order, so a reader can move between sections | Bold text styled to look like a heading |
| Alt text | A description on every meaningful image, chart and the seal | None, or "image001.png" |
| Tables | Header cells marked as headers | Layout tables, merged cells, tables pasted as images |
| Title and language | A document title and a language set in the file properties | Title is the filename; language is blank |
| Form fields | Named, labelled, in tab order | Print-and-sign forms with no fields, or fields named "Text1" |
| Contrast | 4.5:1 for body text | Grey text, text over the watermark |
| Bookmarks | For long documents, a navigable outline | A 300-page packet with none |
Adobe Acrobat Pro's accessibility checker will flag most of these. PAC (the free PDF Accessibility Checker from the PDF/UA Foundation) is stricter and free. Neither one can judge whether the alt text makes sense or the reading order is right, so a person still opens the document with a screen reader for the documents that matter most.
Fix the source, not the output
Remediating a finished PDF is slow, per-page work. Producing an accessible PDF from an accessible source document is nearly free. The whole strategy for a government site is to move the work upstream.
In Microsoft Word, use real heading styles (Heading 1, Heading 2) rather than bold text, insert tables with a header row, add alt text to images through the picture properties, set the document title in the file properties, run Review, then Check Accessibility, and export with File, then Save As, PDF, with "Document structure tags for accessibility" checked. That produces a tagged PDF with correct reading order for most documents. The same applies to Excel and PowerPoint.
Google Docs is the trap. Its PDF export does not produce a tagged document, however well the source is structured. Staff who write in Docs need to export to Word first and produce the PDF from there, or publish the content as a web page instead.
InDesign can produce fully tagged PDFs but only if the designer sets up the article panel and export tags; most annual reports and comprehensive plans arrive from the design firm untagged. Put PDF/UA output in the contract.
Scanned documents need OCR first, which Acrobat does, and then tagging. Signed originals can stay as scans in the archive with an accessible text version alongside them.
Agenda management vendors (the systems that assemble packets) vary widely. Some produce tagged, bookmarked packets; some produce a single image-heavy file. Ask the vendor what their output passes, and put WCAG 2.1 AA in the renewal. Under the rule, their output is your content.
Triage: which PDFs to fix first
Nobody remediates 2,000 documents. The order is decided by two questions per document: is it still used to get a service, and will it be posted, or reposted, after the compliance date.
| Still used for a service? | Posted after your date? | What to do |
|---|---|---|
| Yes | Either | Fix now: applications, forms, current codes, fee schedules, current plans |
| No | Yes | Produce it accessibly from the source; that is the new default |
| No | No | Move to a labelled archive; leave it |
The first row is smaller than it looks. On a typical city site it is a few dozen forms and applications, the current code and fee schedules, the current budget and the current plans. Those get remediated by hand, or rebuilt as web forms and web pages, which is often faster and better.
The second row is the process change. From your compliance date every new agenda, packet, minutes file and report has to arrive accessible, and that comes from the Word template, the export settings and the vendor contract rather than from anyone remediating afterwards.
The third row is the archive. Old minutes and past reports move into a clearly labelled archive section, unchanged, and stay exempt.
Pull a list of PDFs sorted by download count from your analytics before you start. The twenty most-downloaded documents on most government sites are forms and the current fee schedule, and they are exactly the ones a resident, or a complaint, will hit first.
When to publish HTML instead of a PDF
For agendas, minutes, notices and most reports, the accessible answer is to publish the content as a web page and attach the PDF for printing. A page inherits the site's accessible theme automatically: headings, contrast, reading order and language are already handled. A PDF has to carry all of that itself, in every file, forever.
On WordPress this is a content type, not a project. A "Meetings" post type with fields for the body, date, agenda and minutes, plus an upload for the packet, gives residents a readable page and the clerk a form to fill in. The custom post types guide covers how that is built. Forms residents fill in belong in a form plugin rather than a fillable PDF, for the same reason: the plugin handles labels, errors and keyboard access once, and every form gets it.
The cases where a PDF is the right format are narrower than current practice: long documents people print, signed originals, and anything with a legal requirement to be a fixed document. Even those should have a tagged version and, for the important ones, a web summary.
Where TopSyde fits
Our free WCAG 2.1 AA review covers the site and the document library together. A senior developer scans every page, works the pages residents use with a keyboard and a screen reader, counts the PDFs, samples them, and sends a written list ranked by what to fix first, with the forms and current documents separated from the archive. Remediation and the WordPress side (a meetings post type, form plugin migration, the archive section) are quoted from that list.
Afterwards, hosting and maintenance is $89/mo per site with no contract, and the same developer who did the work keeps the templates and plugins from drifting. The request form is on the ADA compliance page; the cities and counties page walks through what the rule reaches on a municipal site.
Frequently Asked Questions
Do old meeting minutes have to be made accessible?
Minutes posted before your compliance date are exempt as pre-existing documents, as long as residents do not need them to access a service and you do not edit them. Move them into a clearly labelled archive section and leave them alone. Minutes posted after your date have to be accessible from the start, which is a matter of how they are produced rather than remediation.
Is a scanned, signed ordinance exempt because it is a scan?
No. A scan is a PDF like any other. If it was posted before the date and is not used to get a service, the pre-existing document exception may cover it. If residents need it, it needs an accessible version: run OCR on the scan and tag it, or post the text as a web page alongside the signed image.
Can our agenda software produce accessible packets?
Some agenda management systems produce tagged, bookmarked packets and some produce a single flattened file. Ask the vendor for their accessibility conformance report and test one packet with a checker. Under the Title II rule the vendor's output is the public entity's content, so put WCAG 2.1 AA in the contract at renewal.
How much does PDF remediation cost?
Remediation services price per page, and the price rises with tables, forms and images, so a 300-page packet costs far more than a 3-page notice. That pricing is the argument for fixing the source: a tagged export from Word costs nothing per page. Spend remediation money on the forms and current documents residents use, and stop producing new documents the old way.
Topics
Content & SEO Strategist
7+ years SEO & content strategy, Google Analytics certified
Elena drives content strategy and SEO at TopSyde, helping clients maximize organic visibility and AI search presence. She combines technical WordPress knowledge with data-driven content optimization.
