Are PDFs covered by ADA Title II?

Short answer

This was the most common scope question during the rule's notice-and-comment period and remains the most common compliance question for state and local entities. The answer is unambiguous in both the rule text and DOJ guidance.

What the rule covers

28 CFR § 35.200 requires that "web content and mobile apps" provided or made available by a public entity conform to WCAG 2.1 Level AA (Source: 28 CFR § 35.200 ) . The rule defines "web content" by reference to its plain meaning: the information and sensory experience delivered to a user via a web browser, including text, images, sounds, videos, controls, animations, and conventional electronic documents such as PDFs.

The DOJ's accompanying fact sheet and preamble are explicit that "conventional electronic documents" include PDF, Word, Excel, and PowerPoint files. The rule covers these documents whether they were authored for web publication or merely posted online after being created in another context.

Why website PDFs count as web content

The mechanism is straightforward: when a public entity posts a PDF on its website (or has it posted by a third party on the entity's behalf), the PDF is part of the digital experience the entity is providing to the public. The same accessibility logic that applies to an HTML page applies to a document the entity links to from an HTML page.

The rule covers content "the public entity provides or makes available, directly or through contractual, licensing, or other arrangements." That language is intentionally broad. It does not matter whether:

• The PDF lives on the entity's own server or on a third-party service
• The PDF was authored by an employee or by an outside contractor
• The PDF is hosted behind a login (the rule applies regardless of authentication)
• The document was originally a paper document and was scanned to PDF for posting

All of those scenarios are "web content provided or made available" by the public entity.

CCCCO memo and California context

For California community college districts, the question is even more explicit at the state level. CCCCO Memo ESS 26-17 (February 27, 2026) names "digital documents (PDF, Word, Excel)" alongside websites, learning management systems, SharePoint, email, HR portals, mobile apps, and social media as in scope for WCAG 2.1 AA conformance (Source: CCCCO Memo ESS 26-17, February 27, 2026 ) .

The CCCCO directive operates independently of the federal rule. Even in the scenario where the DOJ rule is delayed or modified, the CCCCO directive continues to apply to all 73 California community college districts. The applicable state law floor (Government Code §§ 11135 and 7405) further reinforces this.

Common scope misconceptions

The following claims surface frequently and are incorrect:

"Internal documents are not covered."

The rule applies to web content the entity provides or makes available. Documents on an employee-only intranet, HR portal, or staff-facing SharePoint are still web content provided by the entity. Coverage does not turn on public-vs-private; it turns on whether the entity is making the content available digitally.

"PDFs behind a login are not covered."

Authentication does not affect coverage. Student portals, parent portals, applicant portals, and similar logged-in environments are explicitly within scope.

"We just need to provide an accessible version on request."

The CCCCO directive states this plainly: separate is not equal. The rule and the directive both require the published content itself to conform, not an alternative accessible version available on request. Accommodation-on-request was the pre-rule model and is no longer sufficient.

"Vendor documents are the vendor's problem."

The rule applies to content provided through "contractual, licensing, or other arrangements." Documents from a vendor that the entity posts publicly are the entity's responsibility for accessibility purposes, regardless of contractual language.

"Old documents are grandfathered."

There is no general grandfathering. There is a narrow "archived web content" exception (28 CFR § 35.201) and a narrow "preexisting conventional electronic documents" exception (28 CFR § 35.202). Both are narrower than the colloquial use of "archived" or "old." A document that is still linked from current pages, still used in current programs, or still distributed in current operations does not qualify. See the exceptions cluster (Phase 2) for the detailed analysis.