Agenda Packet Accessibility Checker

Status: coming soon. The checker is built and tested on example data only. It cannot fetch real sites yet, is not published on Apify and is not for sale, and no price is set.

Technical evidence of observed behavior on the date tested. Not legal advice and not a certification of compliance.

Know which meeting files changed, and which pages are just pictures of paper.

Public bodies post an agenda packet before every meeting, replace it, and sometimes have it rebuilt by their platform. This checker watches an agenda page, tells you which files are new or truly revised, and flags the pages that look like scanned images.

What you will get for each meeting

  • A list of the new and revised files (agenda, packet, minutes, attachments), with the ones that need the most attention first.
  • For each file, which pages look like scanned images, and whether it has a title and structure tags.
  • A short plain-language summary, a list of anything it could not check and why, and a stated list of limits.
  • A report you can keep: JSON, a plain-text e-mail, or a PDF, each with a fingerprint so you can show it was not edited.

How it works

  1. You give it the address of the body's agenda page. A reader for Legistar and one for any page of PDF links are built; readers for Granicus, CivicClerk and CivicPlus exist but are unverified against real pages, and BoardDocs is not supported yet.
  2. It reads the page politely: one request at a time, a pause between requests, following the site's robots.txt.
  3. It downloads each new or changed PDF and runs fixed, automated checks. No AI reads your files.
  4. It compares files by their text, so a packet rebuilt with the same text is not reported as a change.

Honest limits

  • Automated checks only. A clean result means the checks found nothing to report; it is not evidence a document is accessible.
  • It does not fix files or run text recognition. It tells you where to look, and it does not decide whether a legal requirement or exception applies.
  • If a page changes layout and it cannot read it, it says the source is unreadable. It never says "nothing new" when it could not look.
  • Scanned-page detection is not good enough yet. On a synthetic set of 144 test documents made by the same people who wrote the detector, about 94% of the files it flagged were scanned and about 84% of the scanned files were found. That misses our own target of 95% and has not been tested on real agendas, so treat both numbers as a rough guide only.
  • It cannot yet read a real site at all: that is switched off until our scanner is cleared to fetch real sites.

Use it on pages you are allowed to check

You confirm, with a tick box, that you are the public body, work for it, or have its permission. Findings are returned to you only; we do not publish findings about named bodies.

How you will be able to use it

  • An Apify Actor, in development: Apify listing: coming soon
  • A monthly monitor for one public body with e-mailed reports before each meeting is planned and not built into a product yet. See the waitlist.

How it identifies itself

User agent AgentHarbor-AgendaPackets/<version> (+https://agentharbor.agency/agenda-packets). It follows robots.txt, makes one request at a time per site with a pause between requests, and does not work around blocks. To opt a site out, see our scanner's page.

Waitlist

Paid monitoring and the paid plans for this product do not exist yet, and nothing is for sale. If you want to hear when it opens, e-mail brian@agentharbor.agency with the subject "Waitlist: Agenda Packet Accessibility Checker". We use your address only to tell you about this product and delete it if you ask.

Read the privacy page and the support page.

How this was made: the code and the descriptions were written with an AI assistant (Claude, by Anthropic) and reviewed by Agent Harbor LLC. The checking itself uses no AI.