Knowledge base
Accessible Documents: PDFs, Agendas, Minutes and Forms Under the ADA Web Rule
For most government entities, documents are the largest accessibility gap on the books: years of PDFs that a screen reader reads as a wall of noise, or cannot read at all. The rule covers the documents people currently use to access or take part in your services, and it writes a narrow exception for old ones that are out of use.
Sources
Key takeaways
- Covered: agendas, minutes, budgets, forms, notices and applications people currently use to take part in public life or access a service.
- Generally excepted: conventional documents posted before your compliance date that are no longer in use, and archived content meeting all four archive conditions.
- What accessible means for a PDF: real text (not a scan of paper), tags, a reading order, labeled form fields, document language and a title.
- The practical move: inventory the library, fix the documents in active use first, and make accessibility part of how new documents are published.
Which documents does the rule cover?
The DOJ's web rule covers web content, and documents published on the web are web content. The test is use: a form residents fill in today, this year's budget, the agenda for next week's meeting, the application for a permit. If people currently use it to apply for, access or take part in a service, it has to be accessible.
In detail
The exception runs the other way: conventional electronic documents, PDFs, word processor files, presentations and spreadsheets, that were posted before your compliance date and are not currently used to take part in services generally fall under the rule's preexisting-documents exception. Separately, archived content is excepted when it meets all four of the rule's archive conditions. Both are explained in the DOJ's fact sheet. An exception narrows the checklist; a resident who needs an excepted document to access a service can still request an accessible version, and the entity's other ADA duties still apply.
What makes a PDF accessible?
Six properties, all of them checkable: the text is real text rather than a photograph of paper; the document is tagged so a screen reader knows what is a heading, a list or a table; the reading order is deliberate; form fields carry labels; the document declares its language; and it has a meaningful title. A scanned image of a council agenda has none of these, which is why scans are the most common failure in any document library.
In detail
The same logic extends to other formats. Word and spreadsheet files need heading styles, alt text on images and charts, and real tables rather than layout-by-spaces. Video posted with the minutes needs captions; audio needs a transcript. The underlying checkpoints are part of WCAG 2.1, published by the W3C, and the ones the rule requires are in our checklist.
How do you get a library of accessible documents under control?
In three moves. Inventory first: list what is actually published, where, and what is still in use; most entities find the list is both bigger and older than anyone thought. Then fix in priority order: the forms and notices residents use today come first, the 2011 newsletter does not. Then fix the pipeline, so documents are published accessible from now on instead of being repaired later.
In detail
This is exactly the shape of our initial assessment: the inventory, the testing, and priorities ordered by use and impact. Documents added after the baseline are caught by the next monthly scan, which matters because new documents are published every week and each one is a chance for the gap to reopen.