Guide
Accessible meeting agendas and packets for city clerks
Agendas, minutes and packets are the documents residents open most. Here is how to make them work for everyone.
Last reviewed October 20, 2026. General information for public agencies, not legal advice. Rules change, so check the sources below and ask your lawyer or civil rights office what applies to you.
Why agendas and packets matter most
Meeting agendas, minutes and packets are some of the documents residents open most, and they are how people learn what their council is about to decide. They are also hard to make accessible: an agenda is often built in a hurry, and a packet can combine dozens of files from different departments.
Under the ADA Title II web rule, documents you post after your compliance date have to be accessible from the start. Older documents may qualify for the archive exception if they are kept only for reference in an identified archive and have not been changed. See which PDFs Title II requires you to fix and the dates.
Build the agenda accessibly
- Write it in Word or your layout tool with real styles. Use heading styles for item titles, real numbered or bulleted lists, and table header rows. Do not fake headings by making text bold.
- Export a tagged PDF from that file instead of printing to PDF, which usually drops the structure.
- Use one clear reading order. Single column is easiest. Check that the order a screen reader gives matches the order on the page.
- Describe images that carry meaning, such as a site map, and leave decorative images out of the reading order.
- Make links say where they go. “Staff report for item 4” works. “Click here” does not.
Handle exhibits and scanned pages
Packets get hard when exhibits arrive as scans: a signed letter, a map, an old resolution. A scan is an image, so a screen reader has nothing to read unless text recognition (OCR) is run and the result is tagged. Ask departments for the accessible source file whenever they have one. For the rest, plan time to fix them before the packet is posted. Check a packet again after you combine files, because combining can change the structure.
Add an accessibility notice and a way to ask
Many cities put a standing notice on agendas that names an ADA contact and asks people to request help ahead of time. Santa Ana's packets do this, and Santa Clara's meeting notices refer to its Title II commitment to provide aids and services on request. Whatever wording you use, make sure a resident can actually reach a person and get an accessible version quickly.
A note on meeting software
Many clerks publish through systems such as Legistar, Granicus or CivicPlus. These systems publish the files you give them, so a packet is only as accessible as the PDFs in it. We have not tested what any vendor does to the files. Ask yours what it does, and test one of your own packets.
Before you post a packet
- Each file is a tagged PDF with a title and the right language.
- Headings, lists and tables are marked up, not just styled.
- Scanned pages have been through OCR and tagged.
- Links make sense on their own.
- The accessibility notice and contact are on the agenda.
- You listened to the first page with a screen reader.
The full checklist goes deeper.
Where idioma.chat fits
We built a sample agenda that is deliberately inaccessible so you can see the difference. Try the Document Reader on it. For documents you need fixed, pdf.idioma.chat repairs a PDF's structure for $0.50 per page, with your first 10 pages free. Some documents, such as complex diagrams or poor scans, still need a person to review them, and we do not certify compliance. If residents also need a packet in another language, the Document Reader can translate it as readable text, and vital documents should be reviewed by a qualified translator.
Sources
- City of Santa Ana: sample agenda packet with ADA notice
- City of Santa Clara: meeting disclosure citing Title II
- University of Wisconsin: exceptions to Title II