ADA Title II and PDFs: which local government documents to fix first

Under ADA Title II, PDFs on a local government website have to meet the same standard as the web pages around them: WCAG 2.1 AA. The rule gives older files some room, though. A PDF posted before the compliance date can stay as it is unless people currently use it to apply for, access or take part in a service. So fix forms, current meeting documents and notices first, archive what qualifies, and make new files accessible from the day they're posted.

The deadlines (opens in a new tab) are April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller governments and special districts. DOJ set those dates in an April 2026 interim final rule (opens in a new tab) and said it may propose further changes, so confirm them before budgeting around them. Our Accessibility page tracks the rule.

What does ADA Title II say about PDFs?

The ADA Title II web rule treats PDFs as web content, so they must meet WCAG 2.1 AA once the deadline arrives. DOJ's term for these files is "conventional electronic documents." Five exceptions can apply to some of them, and two matter most for a backlog of old files: preexisting documents and archived content.

A conventional electronic document is any PDF, word processor, presentation or spreadsheet file that a government posts on its website or in a mobile app. That's the definition in 28 CFR 35.104 (opens in a new tab), and DOJ called the list of formats exhaustive in the 2024 final rule (opens in a new tab). Word files, PowerPoint decks and Excel sheets count the same as PDFs.

DOJ admitted that some WCAG success criteria don't map neatly onto a downloadable file. Its answer was that governments must meet them "to the extent those criteria can be applied," and it pointed to W3C's guidance on applying WCAG to non-web documents.

Which old PDFs are exempt under ADA Title II?

A PDF posted before the compliance date is exempt unless it is "currently used to apply for, gain access to, or participate in" a service, program or activity (28 CFR 35.201(b) (opens in a new tab)). Both conditions have to hold. An old application that people still download is covered, and so are the instructions that go with it.

The final rule's discussion of this exception goes further than most summaries:

• Instructions count. If a business license application must be accessible, so must the "application instructions, manuals, sample knowledge tests, and guides" someone needs to use it (final rule (opens in a new tab)).
• Information can count too. DOJ said a PDF describing a park's accessibility features would likely stay covered, because a visitor who reads it first is using it to get into the park.
• "Currently used" keeps applying. DOJ meant documents used "at any given point in the future," not only on the day the rule was published.

ADA.gov gives the other side of the line: a 2018 PDF flyer for a past parade is likely exempt (ADA.gov fact sheet (opens in a new tab)).

When does archived content count as exempt?

Archived content is exempt only if it meets four conditions (28 CFR 35.104 (opens in a new tab)): it was created before the compliance date (or reproduces older paper or media), it's kept only for reference, research or recordkeeping, it hasn't changed since archiving, and it sits in a clearly labeled archive area. Miss one and it isn't exempt.

DOJ was direct about meeting records. Agendas and minutes for meetings held after the compliance date "would likely not meet" the definition, and moving them into an archive folder later doesn't change that (final rule (opens in a new tab)). They need to be accessible when first posted and stay accessible after they're archived.

Older records are different. Untouched 2019 minutes, stored in a section labeled "Archive," can fit all four conditions. A label alone isn't enough, and DOJ said governments can't escape the rule "by merely labeling their web content as 'archived.'"

Do third-party and password-protected documents count?

Usually not, with limits. Content posted by a third party is exempt unless that party posts it under a contract, license or other arrangement with the government (28 CFR 35.201(c) (opens in a new tab)). A PDF about one person, property or account that sits behind a password, such as an individual tax bill, is also exempt.

Both are narrow. ADA.gov says a vendor posting on the government's behalf isn't a third party, and a PDF about a rate increase sent to every customer isn't individualized (ADA.gov fact sheet (opens in a new tab)). The duty to communicate effectively still applies to exempt files. If a resident asks for an accessible version of a utility bill, ADA.gov's example is to provide one, such as large print.

Which PDFs should local governments fix first?

Fix the PDFs people use to do something: forms and applications, current agendas and packets, public notices, and anything people download often. ADA.gov's small entity compliance guide (opens in a new tab) says the exceptions exist so governments can prioritize "the most important content," such as current or commonly used information.

Michigan notes. Michigan FOIA requires a public body with a website to post its FOIA procedures and written public summary there (MCL 15.234(4) (opens in a new tab)). Residents use those files to request records, so they belong near the top (more in our Michigan FOIA guide). The Open Meetings Act requires meeting notices on the website when it's updated with agendas or minutes at least monthly (MCL 15.265 (opens in a new tab)), and proposed minutes must be available within eight business days (MCL 15.269 (opens in a new tab)). Both are Michigan-only rules.

To find the files, start with the pages residents visit most. The free ADA website checker counts the PDFs linked from any page, though it doesn't open them.

How much work is a PDF backlog?

More than most offices expect, which is why sorting matters. The National League of Cities cited one-time PDF remediation costs of $5,000 to $10,000 for small communities, plus ongoing costs of about $70,000 a year, in its 2026 push for relief (Route Fifty (opens in a new tab)).

The federal government has hit the same wall. In a 2016 assessment (opens in a new tab) of a records-posting pilot, DOJ's Office of Information Policy said the barrier agencies named most often was the time and resources needed to make documents accessible before posting them.

Both point the same way. Remediating every old file is expensive, and the rule doesn't ask for it. Spend the effort on documents people use now, and stop adding inaccessible files to the pile.

Should we fix the PDF or turn it into a web page?

For anything people read on screen, a web page is often the better fix. Nielsen Norman Group's research advises using PDF only for documents users will print (opens in a new tab). Federal agencies are told to prioritize HTML and use PDFs only when necessary (opens in a new tab).

That's a federal policy. The reasoning still carries over to local government sites, where a resident usually wants one answer from the file and would rather not download anything to get it.

Forms are the easy call. An online form works on a phone, needs no download and sends the answers straight to staff. For meetings, Agendas & Minutes turns agenda PDFs into accessible web pages, so the posted agenda is readable even when the original file came from somewhere else.

What makes a PDF accessible?

An accessible PDF is a tagged PDF with real text, a logical reading order and labels a screen reader can announce. WebAIM notes that an untagged PDF wouldn't be considered accessible (opens in a new tab). W3C's PDF techniques for WCAG (opens in a new tab) list what that means in practice.

The main pieces:

• Tags for headings, lists, tables and links, so assistive technology knows the structure.
• Reading order that matches the visual order, including multi-column pages.
• Alt text on meaningful images and charts. Decorative images get marked as artifacts.
• Real text. W3C says a scanned document is "inherently inaccessible because the content of the document is images, not searchable text." Running OCR adds real text, but it can misread words, so check the result (PDF7 (opens in a new tab)).
• A document title and language set in the file properties.
• Form fields with labels, required fields marked and a clear way to submit.

PDF/UA (ISO 14289) is the technical standard for accessible PDF files. DOJ considered commenters who suggested relying on it and kept WCAG 2.1 AA as the rule's standard (final rule (opens in a new tab)). PDF/UA is still a useful target for whoever builds the file.

Automated checkers only catch part of this. Acrobat's own checker marks some items "Needs Manual Check" (opens in a new tab), and a person still has to judge whether alt text makes sense or tables read in order.

How do we make new PDFs accessible from the start?

Build accessibility into the source file, then export a tagged PDF and check it before upload. WebAIM says most PDF repair work can be avoided (opens in a new tab) by starting from a document that converts cleanly. Fixing a finished PDF in Acrobat takes longer and needs Acrobat Pro.

1. Write in Word or Google Docs with built-in heading styles, not bold text made bigger (WebAIM on Word (opens in a new tab)).
2. Add alt text to images and charts, and use real lists and tables with header rows.
3. Run the app's accessibility checker before exporting.
4. Export a tagged PDF. In Word, use Save As PDF with "Document structure tags for accessibility" checked. Don't print to PDF, which strips the tags. Google Docs exports can miss tags, so check them (Boise State (opens in a new tab)).
5. Check the PDF before it goes up, then do a quick manual pass on reading order and alt text.
6. Ask whoever sends PDFs for the agenda packet, such as engineers, consultants and other agencies, for tagged files.

Document Center checks each upload for accessibility problems before it goes live, and it has an archive flag for older records. It won't replace a manual review, but it stops new problems from piling up.