State & local guide
State and local PDF accessibility laws: how state rules fit with ADA Title II
Federal ADA Title II sets a nationwide floor for public-sector web content, including PDFs. State statutes and administrative rules can add earlier deadlines, specific technical standards, reporting duties or enforcement mechanisms. This guide compares the rules that most often affect counties, cities, school districts and state agencies, and shows how to plan one remediation programme that satisfies both layers.
The federal floor: ADA Title II
Title II of the Americans with Disabilities Act applies to state and local government services, programmes and activities. The DOJ’s 2024 final rule (28 CFR Part 35) makes WCAG 2.1 Level AA the technical standard for web content and mobile applications. A PDF linked from a public page is web content, whether it is a budget, an agenda packet, a permit form or a notice.
The compliance dates are April 26, 2027 for public entities with a total population of 50,000 or more, and April 26, 2028 for smaller public entities and special district governments. DOJ extended both dates by one year in an interim final rule published April 20, 2026. The underlying WCAG 2.1 AA obligation did not change.
State law does not replace the federal rule. A state can require an earlier date, a different technical standard, a procurement review, a published accessibility statement, or a private right of action. In practice, the stricter requirement controls the project schedule.
State digital and document accessibility laws at a glance
| State | Primary rule | What it means for public documents |
|---|---|---|
| Colorado | HB 21-1110 and HB 24-1454; 8 CCR 1501-11 | State and local public entities must make information technology, including documents, accessible. Colorado’s rules use WCAG 2.1 AA and include an accessibility statement and complaint process. |
| Texas | 1 TAC § 206.70; Tex. Gov’t Code Chapter 2054, Subchapter M; SB 707 | State agencies and institutions of higher education follow accessibility standards aligned with WCAG 2.1 AA. Open-meeting and public-document duties also apply to published records. |
| California | Gov. Code § 7405 and § 11135; AB 434 | State entities and state-funded programmes must provide accessible electronic information and post accessibility certifications. WCAG 2.0/2.1 AA is the common technical benchmark. |
| New York | State Technology Law § 103-d; NYS-P08-005 | State agencies must follow the statewide accessibility policy for information and communication technology, with WCAG 2.1 AA as the practical document standard. |
| Illinois | Illinois Information Technology Accessibility Act (IITAA 2.1) | State agencies and covered entities must meet IITAA standards, which align with WCAG 2.1 AA and include document accessibility requirements. |
| Florida & Minnesota | Fla. Stat. § 282.601–606; Minn. Stat. § 16E.03 | Florida aligns state procurement and technology accessibility with Section 508. Minnesota uses WCAG 2.1 AA as its state technology accessibility standard. |
This table is a planning aid, not legal advice. Statutes and implementing rules change, and local ordinances or university policies can be stricter. Confirm the current text with counsel or the state accessibility office before setting a deadline.
What counties, cities, school districts and agencies should do
A single accessibility programme can satisfy both federal and state requirements if the work is organised around the document, not the statute:
- Inventory the public archive. Record every linked PDF, its owner, page count, whether it has a text layer, and whether it is used to apply, pay, appeal or participate.
- Set the strictest applicable date. Compare the ADA Title II date with the state rule, procurement policy and any local resolution. Plan to the earliest one.
- Prioritise service documents. Budgets, agendas, minutes, RFPs, permits, tax forms, benefit applications, notices and complaint forms come before historical newsletters.
- Use a consistent publication pattern. Keep the original PDF as the record copy and publish an accessible transcript or remediated version from the same page. Link the two clearly.
- Record decisions. Keep the checker output, screen-reader notes, reviewer, date and any exception decision. A documented process is easier to defend than an undocumented one.
For high-volume records, a hosted transcript layer can cover the long tail while file-level remediation is reserved for forms, charts and documents that need a corrected PDF. The PDF remediation guide explains the trade-offs.
Which documents carry the most risk
State and federal rules both focus on equal access to services. The documents that matter most are the ones a person must use to:
- apply for or renew a benefit, licence or permit;
- pay a tax, fee, fine or utility bill;
- find out what a council, board or commission decided;
- respond to an RFP or participate in a procurement;
- understand a public-health, safety or emergency notice;
- file a complaint, appeal or public comment.
A scanned budget or a flattened agenda packet is not automatically excused because it is old or large. The ADA’s effective-communication duty and the state’s accessibility rule can both apply when someone needs the document to use a service. Where an exception is claimed, document the basis and provide an accessible alternative on request.
Document, publish and maintain the result
Accessibility is a publishing process, not a one-time project. A practical annual cycle looks like this:
- Re-crawl the public site and compare the inventory with last year’s list.
- Re-check documents that changed, plus any new high-traffic forms or reports.
- Re-test a sample with NVDA or JAWS and VoiceOver, and run a PDF/UA checker.
- Update the accessibility statement with the date, scope, known limitations and a feedback route.
- Keep a record of requests for accommodation and how they were resolved.
Remediate provides the accessible transcript, reading aids, translation and cited answers; the original PDF remains the record copy. That model lets a county publish a usable version now while it schedules file-level remediation for the documents that need it most.
Primary sources and standards
- ADA Title II Final Rule — 28 CFR Part 35, Subpart H
- ADA Title II Web and Mobile App Fact Sheet — U.S. Department of Justice
- Colorado HB 21-1110 — Colorado Revised Statutes, accessibility of state and local government information technology
- Texas accessibility standards for electronic and information resources — 1 Texas Administrative Code § 206.70
- California Government Code § 7405 — California Government Code § 7405
- New York State accessibility policy — New York State Technology Law § 103-d; NYS-P08-005
- Illinois Information Technology Accessibility Act — IITAA 2.1
- Web Content Accessibility Guidelines (WCAG) 2.1 — W3C Recommendation
- ISO 14289-1: PDF/UA-1 — ISO 14289-1
Frequently asked questions
Do state accessibility laws replace ADA Title II?
No. ADA Title II is the federal floor. A state law can add an earlier deadline, a different technical standard, a procurement review, a complaint process or stronger enforcement. The stricter requirement usually controls the schedule.
Which states have specific public-sector document accessibility rules?
Colorado, Texas, California, New York and Illinois all have published standards or policies that reach public-sector documents, and Florida and Minnesota have state technology accessibility requirements. The exact scope and remedies vary, so confirm the current rule with counsel.
Does WCAG 2.1 AA apply to PDFs?
Yes when the PDF is web content covered by the applicable rule. WCAG 2.1 AA is the technical standard in the ADA Title II rule and is the common benchmark in state policies. PDF/UA (ISO 14289) is the complementary PDF structure standard.
Can we publish an accessible transcript instead of remediating every PDF?
A transcript can provide an equally effective accessible version for many documents, especially long archives. Forms and documents that must function as PDFs may still need file-level remediation. The right mix depends on the document and the applicable rule.
How should a county document its remediation work?
Keep an inventory, the standard and deadline applied, checker output, screen-reader test notes, the reviewer and date, any exception decision, and the accessibility statement and feedback route. Review the inventory at least annually.
This guide is general information, not legal advice. Confirm your obligations with counsel and your accessibility office.