ADA Title II Exceptions: What Content Is Exempt and When It Isn't

Somewhere on most city websites there’s a folder of meeting agendas from 2014, a parade flyer from 2018, and a permit application nobody has touched in the last year. With the first Americans with Disabilities Act (ADA) Title II compliance deadline approaching in 2027, ADA coordinators are asking the same question about it all: does this have to be fixed?

Often it doesn’t. The DOJ’s 2024 Title II final rule includes five exceptions to its Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, but each comes with conditions, and missing one means the content is covered after all. (That permit application, for instance, likely doesn’t qualify if residents still use it.)

Here’s what each exception covers, and the everyday situations where it stops applying.

Archived Web Content

Archived web content is exempt only if it was created before the compliance date, is kept only for reference, research, or record keeping, sits in a dedicated archive area, and hasn't been changed since it was archived. A 1998 water quality report stored unchanged in the archive would likely qualify, for example. 

The archive folder alone doesn't do the work. New council minutes filed under "Archive" don't qualify, an edited spreadsheet loses the exception, and a PDF with current information isn't exempt just because of where it's stored.

Preexisting Conventional Electronic Documents

PDFs, Word documents, presentations, and spreadsheet files posted before the compliance date are exempt unless people still use them to apply for, access, or participate in a service. An old parade flyer would likely qualify; a 2020 business license application residents still submit would not.

The exception also ends when a document changes. Updating an old file after the compliance date or posting a new agenda or report means it must meet WCAG 2.1 Level AA. 

For public colleges and universities, see our guide to Title II requirements for higher education.

Content Posted by Third Parties

Only content posted by members of the public or others not acting on behalf of the government is exempt; content from vendors, contractors, and embedded tools such as calendars, maps, and payment systems must meet WCAG 2.1 Level AA. A resident’s comment on a town message board would likely qualify, but the message board itself would not.

Content doesn’t become exempt because someone else built it, which makes accessibility a procurement issue too. 

Our guide for government entities covers how to update vendor requirements.

Individualized Password-Protected Documents

Word, PDF, presentation, and spreadsheet files about a specific person, property, or account that are password-protected are exempt, but the portal itself and HTML content are not. A PDF water bill in a resident’s secure account would likely qualify. 

The same bill shown as an HTML page wouldn’t, and neither would a PDF rate notice sent to every customer, since it isn’t about one account.

Preexisting Social Media Posts

Social media posts a state or local government made before its compliance date are exempt; posts made after the compliance date must meet WCAG 2.1 Level AA. That means alt text, captions, and accessible formatting on every new post. 

Stylized web browser on a large computer screen sitting on a table; the accessibility symbol is on a shield above the computer.

Does Exempt Content Ever Need to Be Accessible?

Yes: even exempt content must be provided in an accessible format when a person with a disability needs it, under ADA Title II’s effective communication requirement. The exceptions remove the obligation to meet WCAG 2.1 Level AA proactively. They don’t remove the broader duty to provide effective communication, reasonable modifications, and equal access to government services. 

In practice, that means having a way to respond when someone asks. If a resident who is deaf requests an archived city council video, the city could add captions and share the captioned file. If a resident with low vision can’t read their password-protected PDF water bill, the utility could send a large-print version. A clear request process and an accessibility statement that explains it matter just as much for exempt content as for anything else.

Other Limits on the WCAG 2.1 Level AA Requirement

Outside the five exceptions, the rule offers three narrow forms of relief: when compliance would be an undue burden, when a deviation is too minor to affect access, and when a technical or legal limit requires an accessible alternate version. None of them is a way around the standard.

Undue burden or fundamental alteration. A government doesn’t have to make changes that would fundamentally alter a service or cost more than it can reasonably bear. What counts depends on the entity’s resources and can change over time.

Minimal-impact noncompliance. A small deviation that doesn’t affect anyone’s access isn’t a violation, such as text with a 4.45:1 contrast ratio when WCAG requires 4.5:1. The government has to prove the impact is minimal. It can’t use that to skip meeting the standard.

Conforming alternate versions. A separate accessible version is allowed only when a technical or legal limit keeps the original from being made accessible. It isn’t a shortcut for anything else.

How AudioEye Helps Governments Use the Exceptions Correctly

The exceptions narrow the work ahead of April 2027. They don’t eliminate it. Getting the scope right starts with knowing what’s on your site, which documents are still in use, and what’s been posted or changed since your compliance date.

AudioEye gives governments that picture. By combining AI-powered automation with Expert Audits, our approach covers both scale and judgment. Real Time Monitoring constantly scans your site, alerting you to new issues as your site changes. AudioEye’s automation finds and fixes issues at scale while certified experts verify those fixes actually worked. 

And because exceptions end the moment content changes, AudioEye’s Agentic Audits let you test any updated or newly published page on demand, with findings and fix recommendations delivered in 1 hour. 

Know what’s exempt, fix what isn’t, and keep it that way with AudioEye. Scan your site for free, or talk to an expert to get started.