Includoc, home

Accessible agendas, packets and minutes: a weekly playbook for clerks

A repeatable workflow for clerks and comms staff to make meeting agendas, agenda packets and minutes accessible every week, from template to posting.

Last updated

Meeting agendas and minutes stacked beside a gavel and a weekly planner with tasks checked off

To make agendas, packets and minutes accessible every week, fix the process, not just each file. Build them from an accessible Word template, export tagged PDFs with the same settings every time, ask departments for accessible source files, check every PDF before it's posted, and treat the merged packet as its own document that needs a check. This playbook is for clerks, deputy clerks and communications staff who post documents for councils, boards and commissions.

Why meeting documents need a system

Meeting documents are posted on a fixed schedule, often under time pressure, and they come from many hands: the clerk's office, every department, consultants and applicants. For many local governments they're the largest recurring flow of documents on the website.

Under the ADA Title II web rule, documents you post after your compliance date must meet WCAG 2.1 AA. Older agendas and minutes may fall under the preexisting documents or archived content exceptions, but upcoming meeting materials, which people use to take part in public meetings, don't. Our guide to the Title II exceptions explains the details (it's general information, not legal advice).

The practical problem is volume. Fixing a 300-page packet by hand every week isn't realistic. Building accessibility into the template and the export settings is.

The weekly workflow at a glance

WhenWhat happensWho
Once, then yearlyBuild and maintain the accessible agenda and minutes templatesClerk and communications
Before the deadline for staff reportsDepartments write reports from accessible templates and send Word files, not scansDepartment staff
Agenda dayDraft the agenda from the template and export a tagged PDFClerk
Packet dayCheck each attachment, then post them separately or merge and check the packetClerk
PostingUpload with clear link text and a contact for accessible formatsClerk or web team
After the meetingDraft minutes from the template; post approved minutes the same wayClerk
MonthlySpot-check what was posted and fix the template, not just the fileCommunications or ADA coordinator

Step 1: Build an accessible agenda template

Do this once, in Word, and save it as a template (.dotx) where everyone can find it.

  1. Use real heading styles. Heading 1 for the meeting name and date ("City Council Regular Meeting, March 9, 2027"). Heading 2 for sections such as Consent Calendar or Public Hearings. For long agendas, make each item a Heading 3 so screen reader users can jump from item to item.
  2. Use Word's numbering, not typed numbers. Use a numbered or multilevel list (Home > Numbering or Multilevel List) for items like 5.a and 5.b. Never indent with spaces or tabs.
  3. Write descriptive links. "Staff report: Oak Avenue paving contract (PDF)" tells people where the link goes. "Click here" and bare web addresses don't.
  4. Handle the seal or logo. Mark it as decorative if the organization's name is in the heading, or give it short alt text.
  5. Keep key information out of headers and footers. Word usually exports headers and footers as page decoration, which screen readers skip. Put the meeting date and body in the main text too.
  6. Avoid layout tricks. No text boxes, no columns built with tabs, no blank lines for spacing (use paragraph spacing instead), no underscores for blanks.
  7. Don't use color alone. If you highlight added or changed items, add a word such as "Added:" or "Revised:" as well.
  8. Add the accessibility notice. Include how to request the agenda in another format, or a disability-related accommodation, with a name, phone and email.
  9. Set the document properties. Set the language (Review > Language), and give each agenda a title in File > Info > Properties, such as "City Council Agenda, March 9, 2027". Update the title for every meeting.

Run Word's checker (Review > Check Accessibility) on the template itself. Our Word accessibility checker guide explains each result.

Step 2: Get accessible attachments from departments

A packet is only as accessible as its weakest attachment. Most problems arrive from outside the clerk's office as scanned staff reports, untagged exports or slide decks without alt text.

  • Give departments templates. Offer a staff report template with the same styles as the agenda.
  • Ask for source files. Request Word or PowerPoint files, not PDFs and never scans. The clerk's office can export them consistently.
  • Ask for a checker pass. Ask authors to run Review > Check Accessibility before sending, and fix what it finds.
  • Set a rule for signed documents. Post an accessible version (for example, with the signer's name typed, such as "/s/ [name]") and keep the signed original on file. Check this with your records rules and attorney first.
  • Plan for hard content. Large engineering drawings, maps and site plans need a text summary of what matters, and a contact for anyone who needs more help.

Documents written by others but posted by you, such as consultant reports, applicant materials or comment letters in a packet, are generally treated as your content, not "third-party" content.

Step 3: Export the same way every time

From Word on Windows, use File > Save As, choose PDF, then select Options and make sure these are checked:

  • Document structure tags for accessibility
  • Create bookmarks using: Headings
  • Document properties

On a Mac, choose Best for electronic distribution and accessibility (uses Microsoft online service), which sends the file to a Microsoft service for conversion. If you have Adobe Acrobat installed, its Create PDF button in Word also produces tagged PDFs when its accessibility setting is on.

Never "Print to PDF" and never scan a document you have in Word. Printing to PDF throws away the tags, and scanning throws away the text.

If you use an agenda management system, find out how it builds PDFs. Export a sample agenda, run it through a checker, and repeat after every vendor update. Ask the vendor for its Accessibility Conformance Report (ACR) covering the documents it generates.

Step 4: Assemble the packet without breaking it

You have two options.

Option A: post attachments separately. Link each staff report from the agenda as its own PDF. Each file is checked on its own, people download only what they need, and one bad attachment doesn't drag down the whole packet. For many organizations this is the simplest way to stay accessible.

Option B: merge into one packet. If your process requires a single packet, watch for these pitfalls:

  • Untagged or scanned attachments add pages that screen readers can't read. Fix or OCR them first; see scanned PDFs and OCR.
  • The packet's title and language may come from the first file or be missing. Set them on the merged file.
  • Bookmarks from a merge often use file names. Rename them to agenda item numbers and titles, so the outline matches the agenda.
  • Order matters. The packet's tag order should follow the agenda, with the cover agenda first.
  • Size. Very large packets are hard for everyone to use. Consider splitting by agenda section.

Whichever option you choose, check the final file you're about to post, not just the pieces.

Step 5: Minutes

  • Use the same template approach. Headings for each agenda item, real lists and the same export settings.
  • Write votes as text. For example: "Motion carried 4 to 1. Yes: Members A, B, C and D. No: Member E." If you use a table for roll-call votes, give it a header row.
  • Don't post scans of signed minutes. Post the accessible approved version, and keep the signed copy on file.
  • Replace draft minutes cleanly. When the board approves the minutes, the approved version needs the same checks as the draft.
  • Don't forget recordings. If you post meeting video or audio, captions and transcripts are covered by WCAG too, separately from the documents.

Step 6: Check every file before it's posted

This takes a few minutes per file once the template is right.

  1. Run a checker. Upload the PDF to our free checker, or use Acrobat Pro's accessibility check.
  2. Confirm the basics. The file is tagged, has a real title and a language, and has no image-only pages.
  3. Skim the structure. Headings follow the agenda, lists are lists, and tables have header rows.
  4. Check images and links. Every meaningful image has alt text, and every link says where it goes.
  5. Check the reading order on the first page and on any page with columns or sidebars.
  6. Fix the source, not the PDF, whenever the problem came from the template. Next week's agenda will then be right too.

Step 7: Post it well

  • Use clear link text on the web page, such as "Agenda, City Council, March 9, 2027 (PDF, 6 pages)".
  • Use descriptive file names, such as "2027-03-09-council-agenda.pdf", not "agenda-final-v3.pdf".
  • Re-export amended agendas from the source file and run the checks again. Don't patch the posted PDF by hand.
  • Offer accessible formats with a contact on the meetings page as well as in each agenda.

Step 8: Monitor and improve

  • Spot-check monthly. Pick a sample of posted documents, run them through a checker and note recurring problems.
  • Fix causes, not symptoms. If staff reports keep arriving without alt text, update the report template and remind authors.
  • Keep an inventory. Know what's posted, what's been checked, what's exempt and why. Our exceptions guide shows how to record decisions about older documents.
  • Train new staff. A 30-minute session on the template and export settings prevents most problems.

Fix it automatically

Includoc checks each agenda, attachment or packet in seconds and fixes the structure automatically: tags, reading order, headings, bookmarks, title, language, link tags and OCR for scanned pages. Our AI drafts alt text and table headers, and a person approves them on the review screen. Pro accounts can upload a batch of up to 50 files at once. Organization plans also scan your website for new or changed documents (weekly on Organization Standard, daily on Organization Plus) and flag the ones that need attention, so you can catch problems before residents run into them. Organization Standard is $3,600/yr.

Upload your PDF to fix this automatically

Free check in seconds. Files are deleted within 24 hours.

Check your PDF

Standards

Standards references: This PDF has no tags
Standard or toolReference
WCAG 2.1
PDF/UA-1 (ISO 14289-1)Clause 7.1
Acrobat ruleTagged PDF
Standards references: The document has no title
Standard or toolReference
WCAG 2.1
PDF/UA-1 (ISO 14289-1)Clause 7.1
Matterhorn ProtocolCheckpoint 06-003, Checkpoint 07-001, Checkpoint 07-002
Acrobat ruleTitle
Standards references: This PDF is a scan with no real text
Standard or toolReference
WCAG 2.1
PDF/UA-1 (ISO 14289-1)Clause 7.1
Matterhorn ProtocolCheckpoint 08-002
Acrobat ruleImage-only PDF

Sources

Related