ACCESSIBILITY NOTE · AGENDA PACKETS ·
You tagged the attachment.
Is it still tagged in the agenda packet?
If your office pays to make a staff report or a contract accessible and then posts the agenda packet, check the packet itself. In compiled packets that public bodies had posted, we found tagged attachments that came out with no tags at all.
What we found
We downloaded agenda packets and their separate attachments from public meeting pages, logged out. The packets were dated 2 to 27 October 2026. We then compared each attachment that was tagged on its own with the same pages inside the packet.
- On one agenda platform (2 packets from 2 bodies), 13 of 13 tagged attachments we could find in the packet had no tagged pages there. The packets had no tags at all.
- On a second platform (1 packet, 78 pages), the result was the same: 12 of 12.
- On a third platform (6 packets from 6 bodies), 11 of 12 tagged attachments kept their tags in the packet. One did not: a 29-page report, fully tagged on its own, had no tagged pages in the packet. That packet still reported itself as tagged, because its agenda and item cover pages were.
Each of those attachments, opened from its own link, was tagged. A resident who opened the packet got the untagged copy instead. Without tags, a screen reader user has no marked headings to jump between and no marked table headers, and the reading order is left to the software's guess.
We found no help page from an agenda platform that says whether a packet keeps the tags of the files inside it.
Check your own packet
Use the copy residents get. Open your public meeting page in a private browser window and download the packet from there, not from your staff screen.
Step 1, about a minute. Open the packet in the free Adobe Acrobat Reader. Choose Document Properties from the menu (the ☰ menu on Windows, the File menu on a Mac). On the Description tab, look at "Tagged PDF" in the Advanced section.
- No: the packet is not marked as tagged. Treat it as untagged, including any attachment you paid to fix.
- Yes: the packet is marked as tagged, but often only some pages are, such as the agenda. Go to step 2.
In a Mac or Linux terminal with the free Poppler tools (package poppler-utils on Debian or Ubuntu, poppler in Homebrew), this gives the same answer:
pdfinfo packet.pdf | grep Tagged
Step 2, a few minutes, in a Mac or Linux terminal. This needs Poppler 0.42 or later; we tested version 26.01. Choose a tagged attachment that is in the packet and copy a short heading from inside the body of it, a few words that sit on one line. Do not use its title or subject: the packet's cover pages and agenda often repeat those words, and those pages can be tagged even when the attachment's pages are not. Then run:
pdfinfo -struct-text attachment.pdf | grep -c "Program Overview"
pdftotext packet.pdf - | grep -c "Program Overview"
pdfinfo -struct-text packet.pdf | grep -c "Program Overview"
Replace "Program Overview" with your heading, and attachment.pdf with the attachment's own file. Ignore any lines that start with "Syntax Warning". The first command counts the lines where the words appear in the attachment's own tags. If it prints 0, choose another heading: some text, such as page headers, is left out of tags on purpose. The second counts the lines where they appear on the packet's pages, and the third the lines where they appear in the packet's tags.
If the first two numbers are 1 or more and the third is smaller than the first, that attachment most likely lost some or all of its tags in the packet. If the third is as large as the first or larger, its tags most likely survived. If the second number is 0, the heading may wrap onto two lines in the packet's text: choose a shorter one.
The fix
Post each tagged file as its own file or attachment, and link it beside the packet. Some agenda systems combine attachments into one packet PDF, and the combined packet can lose the tags. Then run step 1 on the standalone link as well, to check that the posted copy still has its tags.
What this does not show
- These checks show only whether tags are there. They are not an accessibility audit, and passing them does not mean a file or packet meets the ADA Title II rule or WCAG 2.1 AA.
- We read three agenda platforms, and a small number of bodies on each: two bodies on the first, one on the second. Your system, or its settings, may behave differently. On two other platforms we could not compare a packet with its attachments, so we do not know what they do.
- We did not find the cause of the one loss on the third platform. Other files from the same kind of authoring tool kept their tags in the same kind of packet.
- "Tagged" means some tags are present on a page. It does not mean the tags are correct. A remediated file can be tagged and still read out of order. See how to check a remediated PDF before you post it.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. Corrections: hello@cybernative.ai.