April 26, 2027
ADA Title II Compliance Timeline
Let us help you remediate your PDFs before the deadlines arrive.
Under 28 CFR §§ 35.200–205, state and local governments must meet WCAG 2.1 Level AA — digital documents, including PDFs, are included. Procurement and remediation cycles run months, so the runway is shorter than the calendar suggests.
April 26, 2028
661 days remain for Smaller entities & special districts
Our PDF Remediation for Accessibility Process.
We remove the ADA Title II panic so you can properly work accessiblity into your own systems and processes. The right way. We can do all phases or just the ones you need help with.
Phase 1
PDF Backlog
We work with you to build a customized pipeline and run it on your backlog to produce PDFs designed to conform to PDF/UA-1 and WCAG 2.1 AA standards.
Phase 2
Current PDFs
Integrate the remediation pipeline into your existing systems to ensure ongoing compliance and accessibility as new documents are published.
Phase 3
Accessible-by-Design
Your team learns and adopts accessible-by-design practices. When your upstream systems produce accessible documents natively, we step back to a validation-and-QA role — or out entirely.
Standards We Build To
Click each card to read more in our PDF Accessibility 101 page.
A Bridge to Accessible-By-Design.
We clear your backlog, put a live remediation pipeline in place for future documents, and give your team breathing room to implement accessible design upstream — on your own schedule, not under deadline panic. CurbEffect is a bridge to accessible-by-design, not a permanent dependency.
Documents We Work On
Click a category that matches your entity to see the document types we work on for it.
- Bills and Amendments
- Court Documents
- Fiscal Notes
- Financial Aid Letters
- Tuition Invoices
- Policy Handbooks
- Utility Bills
- Tax Notices
- Permit Renewals
- Boil Water Advisories
- Public Notices
- Benefits Letters
- Meeting Agendas
- Board Minutes
- Resolutions
- Committee Reports
- Public Hearing Notices
- Council Packets
Examples
We took three public documents and ran a veraPDF compliance report on them before and after remediation. The results speak for themselves.
Legislative Amendment
veraPDF compliance report:
Before
221After
0accessibility failures
See full comparison →Utility Bill
veraPDF compliance report:
Before
1,712After
0accessibility failures
See full comparison →Meeting Agenda
veraPDF compliance report:
Before
440After
0accessibility failures
See full comparison →What Sets CurbEffect Apart
How CurbEffect compares with other approaches to PDF accessibility. Many vendors bank on the fact that their clients may not know the full scope of accessibility requirements. Just having tags in a PDF does not equate to accessibility, meaning the legal liability is still there.
| What Genuine PDF Accessibility Requires | AI | Remediate End PDF Only | Alternate Accessible Format (HTML) | Overlay vendors | Autotag |
CurbEffect
|
|---|---|---|---|---|---|---|
| Meets PDF/UA Standards | ||||||
| Addresses both PDF and the Source Document (Word, Google Docs, etc.) | ||||||
| Independent, open-standard validation (like VeraPDF or PAC) compliance reports are not proprietary |
||||||
| Remediates the Original PDF doesn't offer an HTML alternative |
||||||
| Creates Semantically Appropriate Tags lists are tagged as lists, headings are tagged as headings, tables are tagged as tables, etc. |
||||||
| Works with your team to implement accessibility at the begginning of the process follows best practices and guidelines stating accessibility should be considered at the beginning |
meets requirement · varies by vendor · does not meet
Ready to move toward accessible-by-design?
Schedule a free 20-minute call to scope your engagement — or take a tour of real before-and-after examples first.