Structure and navigation
Heading hierarchy, paragraphs, lists, bookmarks, document title, language, and a clean tag tree.
PDF accessibility for public agencies
Accessible public records. Documented by hand.
We repair the structure inside public PDFs so screen-reader and keyboard users can actually use them—then provide the QA record behind every delivery.
- Method
- Manual + automated
- Reference
- WCAG 2.1 AA / PDF
- Delivery
- Remediated file + QA notes
Remediation record
CPW / 24-017
PDF
Public record
Public-meeting-notice.pdf
Manual review completed
- Document structure
- Headings and lists
- Reading experience
- Logical order
- Visual content
- Alt text reviewed
- Keyboard use
- Tab order checked
Reading order
- H1
- P
- H2
- L
Built for lean public-sector teams
- Municipalities
- School districts
- Community colleges
- Public libraries
01 / Remediation scope
More than a checker score.
Automated tools can flag missing tags. They cannot reliably decide whether a heading is meaningful, a table makes sense, or the spoken reading order matches the page.
Reading and tab order
Content is arranged so screen-reader output and keyboard movement follow the intended sequence.
Images and visual meaning
Informative images receive contextual alternatives; decorative material is kept out of the reading experience.
Tables and forms
Header relationships, table structure, field labels, instructions, required states, and keyboard behavior.
Scans and OCR
Image-only documents receive searchable text and a review for recognition errors before structural work begins.
Documented QA
Each delivery includes what we checked, what changed, and any source limitations your team should know about.
02 / Working method
From backlog to usable document.
Start with one important document or a defined batch. We review complexity before quoting and keep exceptions visible rather than hiding them behind a pass/fail badge.
Start with a sample review-
1
Review and prioritize
We examine representative pages, source-file availability, document use, and deadline.
-
2
Scope and quote
You receive a written page range, complexity assumptions, turnaround, revision limit, and price.
-
3
Remediate
We correct document semantics and interaction details, asking for context when meaning belongs to your team.
-
4
Verify and deliver
Automated checks are followed by manual reading-order, keyboard, and screen-reader review.
03 / Procurement-ready starts
Begin small. Scale when the workflow works.
Final quotes reflect document complexity. These starting points cover native digital PDFs with ordinary text, lists, and modest visual content.
Pilot
Priority Document
From $225
Up to 25 simple pages
- Representative preflight review
- Manual remediation
- QA summary at delivery
- One consolidated revision round
Archive sprint
Defined Backlog
From $1,200
Around 200 simple pages
- Inventory and complexity sampling
- Prioritized batch schedule
- Consistent manual QA
- Batch-level delivery record
Ongoing care
Monthly Documents
From $350/month
Up to 40 simple pages
- Reserved monthly capacity
- New-document remediation
- Consistent QA records
- Quoted overage before work
What changes a quote? Complex tables, fillable forms, scans, maps, math, source quality, multilingual content, and accelerated deadlines. We identify these before work begins.
04 / Evidence, not promises
A small document, fully explained.
Our sample public-meeting notice shows how visual formatting becomes meaningful structure, including headings, list semantics, reading order, link purpose, document metadata, and QA notes.
05 / Standards without scare tactics
Accurate scope matters.
The Department of Justice's Title II web rule generally uses WCAG 2.1 Level AA for state and local government web content. Current general compliance dates are April 26, 2027 for entities serving populations of 50,000 or more and April 26, 2028 for smaller entities and special district governments.
Exceptions can apply to qualifying archived content and some preexisting documents. A file does not qualify simply because it sits in an “archive” folder, and documents currently used to access a public service, program, or activity may be treated differently.
We help teams remediate documents within an agreed scope. We do not provide legal advice, certify ADA compliance, or claim every historical PDF must be converted.
06 / Before you ask
Common questions
Can you guarantee that a PDF is legally compliant?
No. Legal compliance depends on context and cannot be guaranteed by a vendor or checker badge. We remediate against an agreed technical scope, test the result, and document limitations.
Do you need the original Word, InDesign, or PowerPoint file?
Not always, but an editable source often produces a better and more maintainable result. We will tell you when PDF-only remediation is practical and when source correction is the better path.
Can you work with scanned documents?
Yes, subject to scan quality. OCR and recognition review are quoted separately because a clean 20-page digital PDF is very different from a faint 20-page scan.
How do we send non-public files?
Do not attach confidential files to the first inquiry. After scope approval, we use a transfer method approved by your organization. The public website does not accept uploads.
Can you support purchase orders and vendor onboarding?
Yes. We work by written quote and invoice and can provide the appropriate foreign-vendor documentation for the seller's legal status when requested.
07 / Free 3-page review
Start with one representative document.
Share a public PDF link and a little context. We will respond with a concise accessibility snapshot, likely complexity, and a practical next step—usually within two business days.
Please do not send confidential files.
Use this form for public links only. Secure transfer is arranged after scope approval.
Prefer email? hello@barozelabs.com