The Five ADA Title II Exceptions — and Why Your Old PDFs Probably Don't Qualify

Every public entity that reads the ADA Title II web rule arrives at the same hopeful question: we have eleven thousand PDFs going back to 2009 — surely we don't have to fix all of those? It is a fair question, and the rule does answer it. There are exceptions. There are exactly five of them, they live in one short regulatory section, and they are considerably narrower than the phrase “archived content” makes them sound.

Where the exceptions actually live

The general obligation is in § 35.200 — web content and mobile apps must conform to WCAG 2.1 Level AA. Everything carved out of that obligation is in the section immediately after it, § 35.201, in five subsections lettered (a) through (e). Two of the key terms are defined separately, back in § 35.104. If a vendor or a consultant describes a sixth exception, or an exception for “low-traffic pages,” or one for “content we can’t afford to fix,” it is not in the rule.

1. Archived web content — a four-part test, not a folder name

This is the exception people misuse most, because it sounds like it applies to anything you move into a directory named /archive. It does not. Section 35.104 defines archived web content as content that meets all four of these conditions:

• It was created before your compliance date — or it reproduces paper documents or other physical media created before that date;
• It is retained exclusively for reference, research, or recordkeeping;
• It is not altered or updated after the date of archiving; and
• It is organized and stored in a dedicated area clearly identified as being archived.

Fail any one condition and the exception evaporates. The word doing the heavy lifting is exclusively. Meeting minutes kept purely as a historical record can qualify. A five-year-old fee schedule that residents still consult to find out what a permit costs cannot — it is in current use, whatever folder it sits in. Note too that the fourth condition is a real design requirement: you have to actually build and label an archive, not simply declare one.

2. Preexisting conventional electronic documents

Subsection (b) is the one that matters most to document-heavy agencies, and it carries the sharpest limit in the rule. “Conventional electronic documents” is a closed list of four formats — PDF, word processor, presentation, and spreadsheet files. That is the entire definition, not a set of examples. Video, images, and ordinary HTML pages are not in it and get no benefit from this exception at all.

Documents in those four formats that were already posted before your compliance date are excepted — unless they are currently used to apply for, gain access to, or participate in your services, programs, or activities. Read that exclusion carefully, because it is where the hopeful answer usually collapses. Application forms, enrollment packets, benefit notices, fee schedules, bid solicitations, the agenda someone needs in order to attend a meeting: all of those are in current use by definition. Age is irrelevant. A 2011 form that someone downloads and submits today is a live part of your program.

What genuinely clears this bar is inert material — a 2013 annual report, a superseded master plan, a decade of past minutes. Worth keeping, and not something anyone uses to obtain a service.

3. Content posted by a third party

Subsection (c) excepts content posted by a third party — unless that third party is posting due to contractual, licensing, or other arrangements with you. The distinction is control, not authorship. A resident's comment on your open message board is third-party content. A payment portal, job-application system, or agenda-management platform that a vendor runs for you under contract is not: you procured it, so its accessibility is your obligation. In practice this exception is far smaller than agencies expect, because most of the third-party content on a government site arrived through a purchase order.

The practical takeaway is a procurement one. Put WCAG 2.1 AA conformance in the contract, ask for a current, tested Accessibility Conformance Report before you sign, and do not accept a vendor's assurance that their platform “is accessible” without evidence behind it.

4. Individualized, password-protected or otherwise secured documents

Subsection (d) covers conventional electronic documents that are both about a specific individual, their property, or their account and password-protected or otherwise secured. Both halves are required. A single resident's utility bill or tax statement behind a login qualifies. A general notice sent to every account holder does not become individualized just because it is delivered through a portal, and an individualized document sitting on an open URL is not secured. The exception recognizes that you cannot pre-remediate a document generated for one person — but if that person needs it in an accessible format, your ordinary effective-communication duty still applies.

5. Preexisting social media posts

Subsection (e) is the simplest: posts published before your compliance date are excepted. There is no obligation to go back and caption years of old video or add alt text to old images. Everything you post after that date is fully in scope — captions, alt text, sufficient contrast, and readable text in graphics. Since social output is continuous, this exception stops mattering almost immediately in practice; treat it as permission to stop looking backward, not as ongoing relief.

The trap: an exception is not an exemption from the ADA

This is the part that catches entities that lean hard on the exceptions. Section 35.201 only relieves you of the obligation to make that content conform to WCAG 2.1 AA. It does not touch the rest of Title II. Your duties to provide effective communication, to make reasonable modifications, and to give people an equal opportunity to participate all survive intact. So when a resident with a disability requests an excepted archival document in an accessible format, “that one's archived” is not an answer — you still have to deliver it in a usable form, on request, without undue delay. An entity that excepts most of its library and builds no process for handling those requests has simply traded a scheduled project for an unscheduled emergency.

What to do with this

Use the exceptions the way they are written: as a triage tool that shrinks a frightening number into a fundable one, not as a reason to do nothing.

1. Inventory before you classify. You cannot apply a “currently used” test to a library you have never counted. Crawl it and get a real file list with formats, dates, and traffic.
2. Sort by use, not by age. Anything that helps someone apply for, access, or participate in a service goes in the remediation queue regardless of when it was posted.
3. Build the archive properly. If you intend to rely on subsection (a), create a clearly labeled archive area and freeze what goes into it. An unlabeled folder is not a legal argument.
4. Fix the intake path first. Forms, applications, and notices are what convert into complaints when they fail. Start there — our PDF remediation guide covers the six failures behind most of them.
5. Write down your reasoning. For each excepted batch, record which subsection applies and why. Documented judgment is defensible; an undocumented assumption is not.
6. Stand up a request process. One published contact, one owner, one target turnaround — because the effective-communication duty never went away.

The deadlines are still ahead of you, not behind: April 26, 2027 for larger public entities, April 26, 2028 for smaller ones and special districts. That is enough runway to do this deliberately — and the entities that finish comfortably will be the ones that spent this year counting and sorting, rather than debating whether the archive folder might save them.