Agendas, packets, minutes 101 documents tested

Agenda packet and meeting minutes accessibility for local government

Your ACFR is published once a year. Agendas, packets, and minutes go up every week. Under the ADA Title II rule, each of those PDFs has to meet WCAG 2.1 AA, so the weekly stream is where staying compliant is won or lost. Here is what our testing found and what actually fixes it.

By Wesley Black, founder of PairedUp · Published October 22, 2026

What we found

97 of 101 agendas and minutes failed. The passes came from agenda systems.

In summer 2026 we tested 481 public documents from 101 Florida cities and counties. 101 were agendas or minutes. They failed less badly than financial reports (a median of 1,779 machine-check failures each, against 52,548 for ACFRs), but 97 still failed. Only two documents in the whole study passed, and both were agendas produced by an agenda management system.

The benchmark
0 failures

Orange County's Board of County Commissioners agenda of June 16, 2026, from its self-hosted eAgenda system, passed both check suites we run.

Close behind
0 PDF/UA

The City of Melbourne's council agenda, published through CivicClerk, passed every PDF/UA machine check with 6 Acrobat-rule flags remaining.

Three weeks later
7 failures

An agenda from the same benchmark system. Passing is a fact about one file, not a setting you turn on once.

The platform isn't the problem. The configuration is.

The documents in the study came through 9 widely used publishing platforms. For every one of them, we found the same software producing tagged output for one government and untagged output for another. The difference was how each government had it set up and what went into the packet, which means most governments can improve their agendas without replacing anything.

Why packets are harder than agendas

The agenda is one document. The packet is everyone's documents.

An agenda system can generate a clean agenda page. The packet behind it is usually assembled from attachments that departments upload: staff reports, contracts, site plans, presentations, and scanned letters. Each one arrives with whatever structure its author's software gave it, which is often none.

Scanned pages

A scanned letter is a picture of text. A screen reader finds nothing to read until the page is converted to real text and tagged.

Merged files

Combining attachments into one packet can strip or scramble the tags each file had. A packet can fail even when its parts passed.

Deadlines

Packets go up days before a meeting, often late in the day. Any fix that depends on someone remembering to run a checker will get skipped.

How to fix it

Keep your agenda system. Close the gaps around it.

Agenda platform PDFs are generated by the system, so you usually can't swap in a fixed file at the same address the way you can on your main website. The work happens at three points instead.

01

Check the configuration

Find out whether your platform's tagged or accessible output is turned on and set up correctly. The same software passes for one government and fails for the next.

02

Fix attachments at the source

Give departments accessible templates for staff reports and presentations, and remediate the attachments that can't be rebuilt, like scans and outside contracts, before they go into the packet.

03

Verify every file as it publishes

Run the same automated checks on each new agenda, packet, and set of minutes the day it appears, so a failing file is caught before a resident finds it.

PairedUp does all three as an ongoing service, alongside remediating your flagship financial documents. See how the service works or a real before and after.

Questions

Agenda and minutes accessibility, answered.

Does our agenda management software make agendas accessible automatically?

Sometimes. Several platforms can produce tagged, accessible PDFs, but in our testing the same platform passed for one government and failed for another. It depends on configuration and on what goes into each packet, so the output has to be checked file by file.

Do meeting minutes have to be accessible under ADA Title II?

Yes. Minutes posted on your website are web content, and the rule requires them to meet WCAG 2.1 AA once your compliance date arrives. The exception for archived content is narrow and doesn't cover minutes that are still posted for current use.

Do the attachments in an agenda packet need to be accessible?

If they are posted on your website as part of the packet, yes. The rule covers conventional electronic documents a government makes available online, which includes staff reports, contracts, and presentations attached to an agenda.

Can we post an HTML agenda and leave the PDF packet as it is?

An HTML agenda helps, but it doesn't excuse the PDF. Under the rule, a separate accessible version is allowed only when the original can't be made accessible for technical or legal reasons. If the packet is posted, it needs to be accessible too.

What about scanned documents in a packet?

A scanned page has no real text, so it fails for screen readers until it is converted with optical character recognition, checked for accuracy, and tagged. Scans are one of the most common reasons an otherwise clean packet fails.

How do we know if this week's packet passes?

Only by testing the file. Free tools like veraPDF run PDF/UA machine checks, and Acrobat's full check covers some of the same ground. We automate both on every new document, because the people publishing packets on deadline rarely have time to.

Next step

Find out how your last month of packets scores.

We'll test the agendas, packets, and minutes your government published in the last 30 days and walk you through the results in 30 minutes. Your team sends nothing.

Book 30 Minutes

Pick a time. That's it.