Guides

How to make meeting agendas and minutes more accessible

Agendas, minutes and meeting packets are often the files a town posts every week. When they are portable document format (PDF) or word-processor files on your website, the Title II web rule treats them as "conventional electronic documents." (28 CFR 35.104)

This page is a starting list of structure checks, tied to Web Content Accessibility Guidelines (WCAG) 2.1 success criteria. It is not a complete WCAG 2.1 Level A and AA checklist, and following it does not make a file "Americans with Disabilities Act (ADA) compliant."

Not legal advice.

First: which agendas and minutes does the rule aim at?

Under Title II of the ADA, the U.S. Department of Justice (DOJ) rule requires state and local government web content, including these documents, to meet WCAG 2.1 Level A and Level AA success criteria beginning on your entity's date.

These are the current dates in 28 CFR 35.200.

DOJ's small-entity compliance guide gives a direct example: city council meeting minutes created after the date the city must meet the rule would not fall under the archived-content exception, even if they are posted in an "archive" section of the website.

By contrast, DOJ's first-steps resource says that PDF minutes from past city council meetings, announcements of past events, and scans of old records "would probably qualify" for the pre-existing conventional-electronic-documents exception, so long as they were posted before the compliance date and are not currently used to apply for, gain access to, or participate in services, programs, or activities. They might also meet the archived-web-content exception if all four parts of that definition are met. Current applications and current ordinances, in the same example, probably would need to meet WCAG 2.1.

So a practical triage, which you should confirm with counsel, is:

  1. New agendas and minutes you will post after your date — plan to post them with accessible structure.
  2. In-use forms and current fee schedules — usually treated as still used for a service.
  3. Older minutes already posted — often in an exception, if the conditions in 28 CFR 35.201 are met.

Even when an exception applies, the ADA requires effective communication, reasonable modifications and equal opportunity. DOJ's small-entity compliance guide includes an archived-video example: if a person with a hearing disability requests access to an archived video, one way to provide effective communication is by adding captions and sharing a copy of the captioned file with the person.

A starting checklist for a new agenda or set of minutes

These items map to WCAG 2.1 success criteria in the June 5, 2018 W3C Recommendation that the rule incorporates. They are a starting list, not the full standard.

  1. Give the file a descriptive title (Success Criterion 2.4.2 Page Titled, Level A) — for example, "Town Council minutes, March 10, 2026," not "scan001.pdf."
  2. Set the document language (3.1.1 Language of Page, Level A).
  3. Use real headings for sections such as Call to Order, Public Comment, and Adjournment, not just bold or larger text (1.3.1 Info and Relationships, Level A; 2.4.6 Headings and Labels, Level AA).
  4. Check reading order. If someone moves through the file without looking at the layout, the sequence should still make sense (1.3.2 Meaningful Sequence, Level A).
  5. Add text alternatives for images, maps, seals and scanned signatures that convey information (1.1.1 Non-text Content, Level A).
  6. Mark data tables with headers, so a vote tally or budget line is not just a picture of a grid (1.3.1).
  7. Prefer real, searchable text over a photograph of a page. Scans are "images of text" unless you convert them (1.4.5 Images of Text, Level AA). Optical character recognition (OCR) is the usual first step.
  8. Check color contrast of live text against the background (1.4.3 Contrast (Minimum), Level AA, generally a contrast ratio of at least 4.5:1).
  9. If the packet includes a fillable form, every field needs a label or instructions and a programmatic name (3.3.2 Labels or Instructions, Level A; 4.1.2 Name, Role, Value, Level A).

Passing a software check is not the same as a person with a screen reader confirming the file works. We do not claim that a file that passes these checks "conforms" to WCAG 2.1.

What a first batch looked like in our desk test

We tested the approach on 6 public PDFs from small-city websites (42 pages), including meeting minutes, newsletters, a scanned fee table and a fillable building-permit form.

These are automated test results only. No person with a screen reader has tested these files yet. Passing automated checks does not by itself mean a document works for every user.

Where it helps, we can also deliver an accessible HyperText Markup Language (HTML, a web-page) version alongside the PDF — for example, for agendas and minutes.

What Agendalight does with a batch

Agents fix tags, headings, reading order, tables, form field names, document title and language, and alternative text. Scanned pages get real, searchable text. Each file comes with a machine validation report, a color-contrast report, a text-fidelity check, a screen-reader simulation transcript (labeled as a simulation, not a human test), and a plain-English summary.

We do not sell an overlay. We fix the document itself. A human screen-reader check is not available yet.

Frequently asked questions

If we put last year's minutes in an "Archives" folder, are we done? Not necessarily. DOJ's guide says minutes created after your compliance date do not fall under the archived-content exception just because they sit in an "archive" section. The definition in 28 CFR 35.104 has four parts, and all four must be met. Not legal advice.

Do we have to remediate every historical packet on the site? DOJ's first-steps "old PDFs" example says past council minutes posted before your date, and not currently used for a service, would probably qualify for the pre-existing-documents exception. Confirm with your counsel. Back-catalog work is optional in our planned service.

Can we post an accessible web page instead of a PDF? Where that makes sense, an accessible HTML version can be delivered alongside the PDF. Whether that meets your needs is a decision for you and your counsel.

Will this make our minutes "ADA compliant"? No. We report which listed automated checks each file passed and on what date. We do not certify ADA compliance. Not legal advice.

Get in touch

Contact is coming soon. See the contact page for updates.

No checkout, no obligation.

Not legal advice. We report automated test results; we do not certify ADA compliance. Learn more: DOJ small-entity compliance guide and DOJ first steps.