Free accessible agenda template
Start from a file that is already structured: accessible meeting agenda template (Word, 1 page). It uses real heading styles, numbered items and a title and language already set. An example PDF exported from it passes veraPDF PDF/UA-1 (validation report). In Word, export with File > Save As > PDF > Options > "Document structure tags for accessibility", then run Review > Check Accessibility.
Need the full set? The accessible meeting template pack ($24) adds minutes, a public hearing notice and a budget summary with row and column headers, each with an example PDF that passes veraPDF PDF/UA-1 and its report.
Have a backlog of past agendas and packets to fix? Email aaron.signalfeed@gmail.com for a free 2-page sample.
Agendas, packets and minutes are the documents public bodies post most often, so they are where most accessibility problems pile up. Under the ADA Title II web rule, new agendas posted after your compliance date need to meet WCAG 2.1 AA (which date applies to you). The good news: agendas follow the same pattern every time, so one good template fixes most of the problem.
Build the agenda as a structured document
- One Heading 1 with the body, meeting type and date: “Board of Trustees Regular Meeting, January 12, 2027”.
- Heading 2 for each section: Call to Order, Public Comment, Consent Agenda, New Business, Adjournment.
- Numbered lists for items, using Word's numbering rather than typed numbers, so “Item 7.2” is announced correctly.
- No layout tables. Two-column agendas built with tables or text boxes read in the wrong order. Put time, presenter and action on one line instead, e.g. “7.2 Water rate study (Finance Director, 15 minutes). Action: discussion and possible vote.”
- Meeting details as plain text: place, address, how to join online, and how to request an accommodation, with a contact name and number.
Attachments and packets
A packet is usually dozens of documents merged into one PDF. Each attachment needs to be accessible on its own, and a merged packet needs bookmarks for each item. Scanned signed contracts or letters need OCR and tagging (see making scanned minutes accessible); better, post the original digital file alongside the signed scan.
Link to attachments with descriptive text: “Item 7.2 attachment: Water rate study (PDF, 24 pages)”.
Minutes
Use the same headings as the agenda so readers can jump to the item they care about. Record votes as text (“Motion carried 4–1. Yes: Smith, Lee, Patel, Ruiz. No: Chen.”) rather than in a grid of checkmarks.
Consider posting the agenda as a web page
An agenda posted as an HTML page on your website is usually easier to make accessible than a PDF, reads better on phones, and is easier to search. Many agenda-management platforms can publish HTML; check yours before converting by hand.
Checklist before you post
- Title set in File > Info > Properties; language set.
- Headings and numbered lists used; no layout tables or text boxes.
- Alt text on any maps, site plans or charts.
- Exported with tags on (see Word to accessible PDF); not “Print to PDF”.
- Run through the free quick check.
Rather have it done?
I rebuild documents and templates as tagged PDFs plus accessible web pages, checked against WCAG 2.1 AA, with a free 2-page sample first. Hire me on Upwork or email aaron.signalfeed@gmail.com.