ADA Title II exceptions: what they cover and where they stop

The DOJ's Title II web rule requires state and local governments to make web content and mobile apps conform to WCAG 2.1 Level AA. Section 35.201 then lists five ADA Title II exceptions: categories of content that do not have to meet that standard. They are useful. They are also narrower than their names suggest, and each one has conditions that are easy to lose in summary.

This post goes through each exception using the regulation's own wording, then covers what none of them change. For the rule as a whole, see our explainer on the ADA Title II web rule.

The five exceptions at a glance

Exception	Main condition	Main limit
Archived web content	All four parts of the definition met	Content created after the compliance date does not qualify
Preexisting conventional electronic documents	PDF, word processor, presentation or spreadsheet file posted before the compliance date	Not if currently used to apply for, access or participate in a service
Content posted by a third party	Posted by someone not acting for the entity	Not if posted under a contract, license or other arrangement
Individualized, secured documents	Document file about a specific person, property or account, and password-protected or secured	Does not cover web pages or apps, only document files
Preexisting social media posts	Posted before the compliance date	Posts after the date are covered

"The compliance date" means the entity's own date: 26 April 2027 for entities of 50,000 or more, 26 April 2028 for smaller entities and special district governments. Our post on the 2027 and 2028 deadlines explains the extension.

1. Archived web content

The regulation defines archived web content in 35.104. All four conditions must be met. The content:

1. was created before the compliance date, or reproduces paper documents or other physical media created before it,
2. is retained exclusively for reference, research or recordkeeping,
3. is not altered or updated after the date of archiving, and
4. is organized and stored in a dedicated area or areas clearly identified as archived.

The DOJ's guidance gives examples of where this fails. Council minutes created after the compliance date do not qualify just because they sit in an "archive" folder. A spreadsheet that is edited and reposted loses the exception. A PDF with current information is not kept only for reference, wherever it is filed.

2. Preexisting conventional electronic documents

"Conventional electronic documents" are defined as PDFs, word processor files, presentation files and spreadsheet files. The exception covers such documents available on the entity's website or app before its compliance date, "unless such documents are currently used to apply for, gain access to, or participate in the public entity's services, programs, or activities."

That last clause carries most of the weight. A 2020 PDF business license application that people still use after the compliance date is not excepted. A 2018 parade flyer probably is. The DOJ's guidance also says a preexisting document that is updated after the compliance date no longer qualifies.

Note what the exception does not cover at all: HTML pages, web forms and apps. It is limited to the four document formats.

3. Content posted by a third party

The exception covers "content posted by a third party, unless the third party is posting due to contractual, licensing, or other arrangements with the public entity."

This is the exception most often misread in procurement conversations. The DOJ's fact sheet says it does not cover:

• third-party content the entity posts itself, including calendars, scheduling tools, maps, reservation systems and payment systems developed by an outside company,
• content posted by the entity's contractor or vendor, and
• the tools and platforms that let third parties post. A message board the entity adds to its site must meet the standard, even if the public's posts on it are excepted.

Put simply, a member of the public posting a comment is a third party. A vendor hosting your permit portal is not, because it is acting under a contract with you. This is why the conformance of vendor products matters as much as it does. Section 35.200 itself covers content provided "directly or through contractual, licensing, or other arrangements".

4. Individualized, password-protected or otherwise secured documents

This exception covers conventional electronic documents that are both:

1. about a specific individual, their property or their account, and
2. password-protected or otherwise secured.

All conditions must be met, and the document must be one of the four file formats. The DOJ's examples use a water bill:

• A PDF bill in a resident's secure account probably falls under the exception.
• The same bill shown as an HTML page in the account does not, because it is not a conventional electronic document.
• A PDF about a rate increase posted to every customer's account does not, because it is not about one account.
• The secure account portal itself is not excepted.

This matters for SaaS buying. Utility billing, tax and permitting systems often generate individual statements as PDFs. The exception may cover those files, but not the portal around them, and not general notices the system generates. Ask the vendor which outputs are PDFs and whether the report covers them.

5. Preexisting social media posts

A public entity's social media posts made before its compliance date are excepted. Posts after that date are not. The DOJ's guidance notes that an entity may still need to provide an older post in accessible form on request, for example by supplying a description of an image.

What the exceptions do not change

Three limits apply across all five.

Effective communication still applies. The DOJ's guidance repeats, for each exception, that the ADA still requires effective communication, reasonable modifications and an equal opportunity to participate. Excepted content may still need to be provided in an accessible form to a person who needs it. The guidance's examples include captioning an archived video on request and providing a large print version of a secured PDF bill.

The exceptions are not a schedule. Content that is excepted today can lose the exception: an archived document that gets edited, an old form still in use, a social media post made after the date.

They rarely reach procured systems. Archived content, old documents and social media posts are mostly about an entity's own publishing. The systems vendors build and host for you are, by the rule's own text, covered. The exceptions do not reduce the need to evaluate vendor conformance reports. See how to read a VPAT for that.

A practical sequence

For an entity working toward its date, a reasonable order is:

1. Inventory web content and apps, separating your own content from vendor-provided systems.
2. For your own content, identify what genuinely meets each exception's conditions, and record why. Remember that documents still used to apply for services do not qualify.
3. For vendor systems, set the exceptions aside. Ask each vendor for a current conformance report against WCAG 2.1 AA and review it.
4. Keep a process for accessible-format requests for excepted content.

State laws may impose additional requirements. Check our state accessibility laws pages.

---

Sources: 28 CFR 35.201 (exceptions) and the definitions of archived web content and conventional electronic documents in 28 CFR 35.104, part of the DOJ's 2024 Title II web rule as amended in April 2026; DOJ fact sheet on the rule at ada.gov. This is general guidance, not legal advice.

GOVvpat reviews the conformance reports for the vendor systems the exceptions do not reach, and keeps a dated record of what was raised. Request a quote.