What the ADA Title II web rule means for your PDFs

The short version

In April 2024 the U.S. Department of Justice issued a rule under Title II of the Americans with Disabilities Act that requires state and local governments to make their web content and mobile apps meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Documents posted on a government website, such as PDFs, Word files, slide decks and spreadsheets, are part of that web content (ADA.gov fact sheet).

On April 20, 2026, the Department published an interim final rule (Federal Register document 2026-07663, 91 FR 20902) that moved the compliance dates back by a year. It took effect the day it was published, and the technical standard did not change (Federal Register).

For a clerk, the practical meaning is simple: agendas, minutes, packets and other documents you post after your date need to be accessible when you post them.

Which meeting documents are covered

The rule applies to content a public entity provides through its website or apps, whether it is a web page or a downloadable file. For meeting documents that includes agendas, packets and their attachments, minutes, public hearing notices, ordinances and resolutions, budgets, requests for proposals, and fillable forms.

Attachments written by someone else deserve special attention. The fact sheet describes an exception for content that third parties post themselves, but explains that the exception does not cover third-party content that the government posts; that content would usually need to meet WCAG 2.1 AA (ADA.gov fact sheet). A developer's site plan, an auditor's report or a contractor's bid that the clerk adds to the packet is posted by the government, so plan for it to be in scope.

Exceptions that matter for clerks

The rule has five exceptions. Three are relevant to meeting records (ADA.gov fact sheet):

• Archived web content. All four conditions must hold: it was created before your compliance date, it is kept only for reference, research or recordkeeping, it is kept in a special area for archived content, and it has not changed since it was archived.
• Preexisting conventional electronic documents. Word processing, presentation, PDF and spreadsheet files that were on your site before your compliance date. The fact sheet's example is a PDF parade flyer posted in 2018. This exception does not apply to documents people currently use to apply for, access or take part in your services, programs or activities.
• Individualized, password-protected documents about a specific person, property or account, such as a utility bill.

The other two cover content posted by third parties and social media posts made before the compliance date.

An exception is not permission to turn people away. The ADA still requires effective communication and reasonable modifications, so if a resident asks for an accessible version of an archived packet, you need to provide one.

What an accessible PDF means in practice

WCAG was written for web pages, and the W3C publishes a set of PDF techniques showing how its success criteria apply to PDFs. For a typical meeting document, meeting WCAG 2.1 AA usually comes down to:

• Real text rather than scanned images of text, with text recognition (OCR) where a scan cannot be avoided.
• Tags that describe the structure: headings, paragraphs, lists, tables with header cells, and a logical reading order.
• Alternate text for meaningful images such as maps, site plans and charts, and decorative images marked as artifacts.
• A document title and a document language.
• Sufficient color contrast, and no information conveyed by color alone.
• Labels for fillable form fields, and no security settings that block assistive technology.

PDF/UA (ISO 14289) is the technical standard for accessible PDF, and the PDF Association's Matterhorn Protocol lists the ways a file can fail it. The two overlap heavily but are not the same checklist; the DOJ rule points to WCAG 2.1 AA.

What is still uncertain

• Possible changes to the rule itself. In the interim final rule, the Department said that during the extension period it "will consider issuing an NPRM providing members of the public with an opportunity to comment on the substance of the 2024 final rule and any changes proposed by the Department" (Federal Register). We had not seen such a proposal as of this page's review date.
• Litigation over the delay. On May 21, 2026, the National Federation of the Blind announced a lawsuit against the Department of Justice and the Department of Health and Human Services asking a court to block the delays and restore the original deadlines, arguing that the delays skipped required notice-and-comment procedures (NFB press release). We had not found a ruling as of this page's review date. If the original dates were restored, the date for larger entities would already have passed.
• Health and human services programs. Recipients of HHS funding fall under a separate Section 504 rule. HHS announced on May 7, 2026 a one-year extension of its web and app dates: May 11, 2027 for larger recipients and May 10, 2028 for recipients with fewer than 15 employees (HHS fact sheet).

Plan for the current dates. Work done now is not wasted if the dates move again, and requests from residents for accessible documents can arrive at any time.

A realistic plan for a clerk's office

1. Inventory what you post. List document types, roughly how many pages a month, and where each comes from: your own templates, scanned paper, or outside parties.
2. Fix the templates first. Agenda and minutes templates with real heading styles, lists and tables prevent most problems every week. See the packet workflow guide.
3. Set export settings once so every PDF keeps its tags.
4. Decide how to handle outside documents. Ask for accessible digital originals in submission instructions and contracts, and budget time for the rest.
5. Check every packet before posting with an automated checker and a short manual review.
6. Say how to request an accessible version on your meetings page, and respond quickly when asked.
7. Separate the archive. Move old records into a clearly labeled archive section that meets the archive conditions.

Check your own files

Related guides: Accessible board packets · How to check a PDF

Sources

1. Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (interim final rule, April 20, 2026). Federal Register document 2026-07663
2. Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments. ADA.gov, U.S. Department of Justice
3. Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation
4. PDF Techniques for WCAG 2.1. W3C
5. The Matterhorn Protocol. PDF Association
6. National Federation of the Blind Sues Government over Delay of Accessibility Rules (May 21, 2026)
7. Section 504 detailed fact sheet (HHS Office for Civil Rights)