About
Why PacketAccess exists.
Public entities are about to face a hard deadline for something almost none of them are staffed to handle. We built a service to close that gap without asking anyone to change how they publish.
The problem we saw
A deadline is coming for documents nobody was staffed to fix.
The DOJ's ADA Title II rule sets hard deadlines — April 26, 2027 for public entities serving 50,000 or more residents, and April 26, 2028 for smaller entities and special districts — requiring web content and PDFs to meet WCAG 2.1 AA. Most cities, counties, school districts, and special districts publish hundreds or thousands of pages of agenda packets, minutes, forms, and reports every year, produced by clerks and staff who were never trained in accessible-document authoring and don't have a compliance budget line for it.
That's not a software problem you can fix with a plugin. It's a production problem: someone has to actually process every document, and someone has to be able to prove it happened.
Our approach
Fit into your workflow. Don't replace it.
We didn't want to ask clerks and communications staff to learn a new publishing platform, migrate a document archive, or change how they work with their council or board. So PacketAccess sits downstream of whatever you already use: you publish exactly as you do today, we pick up every new document automatically, and we return a remediated, visually identical file within our SLA.
Repairing the existing file in place — rather than regenerating it from scratch — is deliberate. Public records and exhibits need to look exactly as published; visual fidelity isn't optional for a legal record.
Accuracy over automation
AI drafts. A person signs off.
Automation gets us speed on the mechanical parts of remediation: OCR text layers, structure inference, first-pass alt text drafts. But every document is validated by machine (PDF/UA rule checks) and reviewed by a human before it goes back to you — alt text especially is never auto-shipped. That balance is how we hit a 24–48 hour turnaround without guessing on what a screen reader user actually needs to understand a zoning map or a budget table.
Every document we touch is logged: what was fixed, when, and validated against which standard — so the answer to "can you prove it" is always a records request away, not a scramble.
Data & security posture
We only ever touch what's already public.
- Public documents onlyWe accept documents that are published or intended for publication — nothing confidential or CUI.
- US-region storageDocuments are stored in US-region cloud infrastructure for the duration of processing.
- Deletion on requestAsk us to remove a document or a customer's data and we will.
- No training on customer documentsYour packets are never used to train any model.
- Access loggingEvery access to a stored document is logged.
Want to see it on your own packet?
Send us a real agenda packet and we'll remediate it free, so you can see exactly what we mean.
Get a Free Packet Review