Plan a pilot box
Menu

ADA Title II and digitized collections: deadlines and exceptions

Reader question: Does the Justice Department's ADA Title II web accessibility rule apply to our digitized historical collections, by when, and does the archived content exception cover them?

By Dastok Editorial TeamIssue: Published

Yes, if your institution is part of a state or local government. The Justice Department’s ADA Title II rule requires the web content you provide, including online collections delivered through a vendor, to meet WCAG 2.1 Level AA from April 26, 2027 for entities with a population of 50,000 or more and from April 26, 2028 for smaller entities and special district governments, as of November 22, 2026. The archived web content exception can cover scans of old originals, but only when all four of its conditions hold, and it generally does not reach the search pages, item pages, new descriptions or online exhibits built around those scans.

This article is not legal advice. It reads the rule text, the Department of Justice’s own explanation and its published guidance, and turns them into questions to work through with your counsel and your ADA coordinator. Every date and quotation below was checked on the primary source on November 22, 2026.

Who the rule covers, and who it does not

The rule covers public entities: state and local governments and their departments, agencies and other instrumentalities. For collections, that means county and municipal records offices, public libraries, public museums run by a city or county, and special collections at public universities. Private nonprofits, such as most historical societies, fall under a different part of the ADA.

Public entities and their vendors

Title II’s definition of a public entity includes “any State or local government” and “any department, agency, special purpose district, or other instrumentality” of one. ADA.gov’s fact sheet on the rule lists public libraries and “public schools, community colleges, and public universities” among its examples.

The rule reaches content you do not host yourself. Section 35.200 requires a public entity to make accessible the web content it “provides or makes available, directly or through contractual, licensing, or other arrangements.” The fact sheet adds that governments that contract with others to provide public services “also have to make sure that their contractors follow Title II.” A digital collections platform, a hosted viewer or a digitization vendor’s publishing service used by a county library sits inside that wording.

Private museums, libraries and historical societies

Privately run museums and libraries are generally covered by Title III, which applies to “public accommodations.” The Title III definition in 28 CFR 36.104 lists “a museum, library, gallery, or other place of public display or collection.” The 2024 web rule and its WCAG 2.1 requirement were written for Title II. ADA.gov’s 2022 guidance on web accessibility, which it notes does not reflect the 2024 rule, says businesses open to the public “have flexibility in how they comply” but must still make the goods and services they provide online accessible. A private historical society therefore has obligations, but not the Title II rule’s dates or exceptions, unless it is delivering a public entity’s content under an arrangement with that entity.

Example (fictional). Aster County has a population of 38,000 in the 2020 Census. The county clerk’s office, the county library and the county-run museum are public entities. The Aster County Historical Society is a private nonprofit. Under an agreement with the county, the society hosts scans of the county commissioners’ minutes from 1889 to 1920 on its own website. The society’s other collections fall under Title III, but the commissioners’ minutes are content the county “makes available” through an arrangement, so the county must make sure that part of the society’s site meets the rule.

The deadlines after the April 2026 extension

As of November 22, 2026, public entities with a total population of 50,000 or more must comply from April 26, 2027, and public entities with a population under 50,000 and all special district governments from April 26, 2028. Those dates come from an interim final rule published April 20, 2026, which moved each original date back by about a year.

Who Original date (2024 rule) Current date (2026 interim final rule)
Public entities with a total population of 50,000 or more April 24, 2026 April 26, 2027
Public entities under 50,000, and any special district government April 26, 2027 April 26, 2028

Some guidance still circulating gives the original dates. The current dates are in 28 CFR 35.200(b) and in the interim final rule itself.

Which date is yours

Your date depends on the population of the government you belong to, not the number of people who use your collection. ADA.gov’s Small Entity Compliance Guide explains that a part of government without its own Census figure, “like a city police department or a city library,” uses “the population of the larger government they are part of,” which for most governments is a number from the 2020 Census. A county records office uses the county’s population. A state university library, as part of a state instrumentality without its own Census figure, generally uses the state’s, under the definition of total population in 28 CFR 35.104. Special district governments, defined in 28 CFR 35.104 as public entities other than a county, municipality, township or independent school district that provide “one function or a limited number of designated functions,” use the later date whatever their size.

What the extension changed, and what it did not

The interim final rule changed dates only. It says it “does not alter the substantive requirements adopted in the 2024 final rule” and that “no matter the deadline, the rule’s substantive requirements bind covered entities.” Its explanation is worth reading for anyone planning remediation of scanned collections: “Advanced technology, such as generative AI, does not yet reliably automate the remediation of inaccessible content at scale, and staff resources and availability continue to pose significant challenges.”

The Department invited comments on the new dates through June 22, 2026. Its entry in the federal Unified Agenda of regulatory actions for this rule (RIN 1190-AA82) says it is considering whether to “publish a Notice of Proposed Rulemaking (NPRM) to reconsider whether some of the regulatory provisions imposed by the April 24, 2024 rule could be made less burdensome,” with the timing of that notice listed as to be determined. No further change had been published in the Federal Register as of November 22, 2026. Check before relying on any date.

Obligations that apply before your date

The compliance date is when the WCAG requirement starts, not when your duties begin. The Small Entity Compliance Guide says the ADA “has always required state and local governments to provide individuals with disabilities with effective communication, reasonable modifications, and an equal opportunity to participate,” and that those requirements apply online before the rule’s start dates.

What WCAG 2.1 Level AA asks of a digitized collection

WCAG 2.1 Level AA is a set of testable success criteria published by the World Wide Web Consortium in June 2018; the rule adopts that 2018 version. For an online collection, a handful of criteria do most of the work: text alternatives for images, captions and alternatives for recordings, real structure in pages and documents, keyboard operation, contrast, link text and controls that assistive technology can identify.

Collection element WCAG 2.1 success criterion (level) What it means in practice
Scans of letters, ledgers, maps; photographs 1.1.1 Non-text Content (A) A text alternative “that serves the equivalent purpose”: transcription or OCR text for documents, a description for photographs
Page images of printed or handwritten text 1.4.5 Images of Text (AA) Real text is preferred to images of text, except where a particular presentation is “essential”
Oral histories and films with sound 1.2.2 Captions (Prerecorded) (A) Captions for prerecorded audio in video
Video with information only seen, not heard 1.2.3 Audio Description or Media Alternative (Prerecorded) (A) Audio description or a full text alternative
Item pages, finding aids, PDFs 1.3.1 Info and Relationships (A) Headings, lists, tables and reading order that software can determine; tagged structure in PDFs
Viewer controls: zoom, page turn, download 2.1.1 Keyboard (A); 4.1.2 Name, Role, Value (A) Every function works from a keyboard, and every control has a name and role a screen reader can announce
Interface text and captions 1.4.3 Contrast (Minimum) (AA) At least 4.5:1 contrast for normal text
Lists of items and download links 2.4.4 Link Purpose (In Context) (A) Link text that says what each link opens, not “click here” or a bare file name

Two of these need a word of interpretation for historical material. The WCAG 2.1 glossary defines “essential” as something that, “if removed, would fundamentally change the information or functionality of the content.” The appearance of a handwritten 1893 letter is arguably essential to the record in a way that a scanned flyer is not, which is our reading, not an official one. Even so, that exception concerns images of text, not text alternatives: a person who cannot see the scan still needs the words, which is what criterion 1.1.1 asks for.

The second is accuracy. A text alternative has to serve the equivalent purpose. Raw machine text with frequent errors in names, places and dates may not do that for a reader who depends on it, so the correction level you choose for OCR and handwriting recognition is an accessibility decision as well as a search decision.

The archived web content exception, condition by condition

Archived web content is excepted from the WCAG requirement only if it meets all four parts of the definition in 28 CFR 35.104. Scans of historical originals usually pass the first part easily, even when they are digitized after your compliance date. The other three parts, especially “exclusively for reference, research, or recordkeeping” and “not altered or updated,” are where most online collections run into trouble.

The definition reads in full: archived web content is web content that “(1) Was created before the date the public entity is required to comply with subpart H of this part, reproduces paper documents created before the date the public entity is required to comply with subpart H, or reproduces the contents of other physical media created before the date the public entity is required to comply with subpart H; (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 being archived.”

1. Created before your compliance date, or a copy of paper or other media made before it? 2. Kept only for reference, research or record- keeping, not as an exhibit or a current service? 3. Not altered or updated since it was placed in the archive? 4. Stored in a dedicated area clearly identified as archived? Yes to all four: likely excepted. Still provide an accessible version when asked. Any answer no generally must meet WCAG 2.1 Level AA, unless another exception applies yes yes yes yes no
The four conditions of the archived web content exception. Diagram by the Dastok Editorial Team from 28 CFR 35.104 and 35.201(a) and the Department of Justice's ADA.gov fact sheet, checked November 22, 2026. Not legal advice.

Condition 1: when the content, or the original, was created

This is the condition historical collections pass most easily. The Department’s explanation of the 2024 rule, published with it in the Federal Register, says paper documents “include various records that may have been printed, typed, handwritten, drawn, painted, or otherwise marked on paper,” and names “videotapes, audiotapes, film negatives, CD-ROMs, and DVDs” as physical media. Its example is a state agency that finds a box of 1975 files and negatives after its compliance date and posts scans of them: the scans “would meet the first part of the definition” because the originals were created in 1975.

Minor adjustments do not break this condition. The Department gives redacting personally identifying information as an example of a change that is allowed. Substantial edits, “such as by adding, updating, or rearranging content,” may mean the result is “no longer a reproduction of the historic content.”

Condition 2: exclusively for reference, research or recordkeeping

The word “exclusively” does a lot of work. The Department says that “if an entity maintains content for any purpose other than reference, research, or recordkeeping, then that content would not fall within the exception regardless of the date it was created.” It gives an example that fits many libraries and museums: a city research library that curates an online exhibition about the history of a park, using historic material that otherwise meets the definition. In that case, “all content used to deliver the online exhibition likely would not be used exclusively for reference, research, or recordkeeping, as the library is using the materials to create and provide a new educational program.” A scanned record that a department still relies on for a current service is in the same position.

Condition 3: not altered or updated after archiving

Collections are rarely static. Catalogers correct records, transcriptions arrive from volunteers, machine-suggested fields are reviewed. The rule says only that archived content “is not altered or updated after the date of archiving,” and the Department adds that if content is altered after it is posted in an archive, it “would generally need to conform to WCAG 2.1 Level AA.” The rule does not say how this applies to catalog records and transcriptions that sit beside an unchanged scan. Ask your counsel, and design the archive so that the excepted scans and the living records are separate pieces of content.

Condition 4: a dedicated area clearly identified as archived

The archived content has to be organized and stored in one or more areas “clearly identified as being archived.” The Department warns that entities “may not circumvent their accessibility obligations by merely labeling their web content as ‘archived’ or by refusing to make accessible any content that is old.” A digital collections site presented as a current public service is not, by its name alone, an archive in this sense.

What the exception does not cover in an online collection

An online collection is several kinds of content at once, and the exception applies piece by piece. In the Department’s words, web content “that is not archived, but instead notifies users about the existence of archived web content and provides users access to archived web content, generally must still conform to WCAG 2.1 Level AA.” The search, the browse pages and the viewer are that kind of content.

The table below is our reading of the rule and the Department’s explanation, offered as a starting point for your counsel, not a determination.

Part of an online collection Likely status under the exception Why
Page images of pre-deadline originals, in a labeled archive area, unchanged May qualify All four conditions can be met
Search page, browse lists, item pages, navigation Generally must conform They give access to archived content; the Department says such content generally must conform
Viewer and its controls Generally must conform Part of the interface people use to reach the content
New descriptions, finding aids and transcriptions written after your date Likely must conform Newly created content does not reproduce a pre-deadline original
Online exhibits and lesson pages using archived scans Likely must conform The Department’s park exhibition example: not exclusively for reference or research
Scans still used for a current service, such as records consulted in a live process Likely must conform Not kept exclusively for reference, research or recordkeeping
Archived items later edited or replaced Generally must conform Fails the “not altered or updated” condition

Example (fictional). The Aster County library publishes scans of the commissioners’ minutes, 1889 to 1920, and of the Wren Gulch Mercantile day book on loan from the historical society, in a section headed “Historical Records Archive.” The page images reproduce originals from the 1880s and 1890s, are kept for research and are not edited after posting, so they may qualify. The search page, the item pages and the viewer are the library’s interface and must conform by April 26, 2028. The library plans to add volunteer transcriptions of the minutes in 2029; those are new content and must conform when they go up, which is convenient, because they are also the text alternative for the scans. For its exhibit “Wren Gulch at 130,” the library uses six day book pages, and those exhibit pages are treated as needing to conform in full.

The other exceptions and limits that matter for collections

Five other provisions can affect a digitized collection: the exceptions for preexisting conventional electronic documents and for content posted by third parties, the limit on conforming alternate versions, the defenses of fundamental alteration and undue burden, and the rule on noncompliance with minimal impact on access. None is a general exemption for historical material.

Preexisting conventional electronic documents

Section 35.201(b) excepts conventional electronic documents available on your site before your 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.” The definition of conventional electronic documents is narrow: “portable document formats (‘PDF’), word processor file formats, presentation file formats, and spreadsheet file formats.” Scanned PDFs posted before your date may fall here. Image files, item pages and viewers do not, because they are not in those formats. Documents posted after your date are not covered by this exception at all.

Content posted by a third party

Section 35.201(c) excepts “content posted by a third party, unless the third party is posting due to contractual, licensing, or other arrangements with the public entity.” Comments left by visitors on an item page are the obvious case. Crowdsourced transcription is less clear. The American Library Association’s guidance on applying the rule to library content reads the exception as intended for situations where “members of the public post content to a website you host,” and says you would be responsible for their content if “you contracted with or solicited them to do so.” That is a professional body’s reading, not the Department’s, but it suggests that a transcription project you organize and publish should plan for accessible output rather than rely on this exception.

Conforming alternate versions

A separate accessible version of inaccessible content is allowed only in narrow cases. Section 35.202 permits conforming alternate versions “only where it is not possible to make web content directly accessible due to technical or legal limitations.” A text-only page beside an inaccessible viewer is therefore not a general solution.

Fundamental alteration and undue burden

Section 35.204 lets a public entity comply only to the extent that compliance would not cause “a fundamental alteration” or “undue financial and administrative burdens.” The decision must be made by “the head of a public entity or their designee,” after considering all resources available, and “accompanied by a written statement of the reasons.” The entity must still take other action to give people with disabilities the benefits of the service “to the maximum extent possible.” In its explanation of the 2024 rule, the Department described a small town whose website archive holds a large volume of material gathered by the town’s historical society, “such as old photographs and handwritten journal entries from town elders,” and said it “might be an undue burden” to make all of it accessible “in a short period of time in response to a request,” depending on the town’s budget and the cost, which “will also vary over time.”

Noncompliance with minimal impact

Section 35.205 deems an entity compliant where it can show that a failure to meet WCAG “has such a minimal impact on access” that people with disabilities can still get the same information, interactions and transactions with “substantially equivalent timeliness, privacy, independence, and ease of use.” The Small Entity Compliance Guide is blunt about its limits: “You cannot use this part of the rule to avoid trying to meet WCAG 2.1, Level AA.”

Excepted content still needs a way in

An exception from WCAG does not end the duty to serve people with disabilities. The ADA.gov fact sheet says that even when content does not have to meet WCAG 2.1 Level AA, a government “would likely still need to provide the content to a person with a disability who needs it in a format that is accessible to them.” For a digitized collection, that means a visible, working way to ask for an accessible version, and a plan for answering.

The Small Entity Compliance Guide suggests written policies that “explain the steps staff will take if a person with a disability asks them to make accessible content that falls under an exception,” with timing for urgent requests, and notices “in prominent places” on the website telling people how to ask. In its explanation of the 2024 rule, the Department also called it “a best practice” to replace an inaccessible archived file with the accessible version made in response to a request, so the next reader benefits too.

For a collection, a workable request process names a contact, lists the kinds of help available (a transcription, a description of a photograph, a captioned copy of a recording, a reading of a ledger page), sets a target turnaround, and records each request so that frequently requested items are remediated first.

Example (fictional). A researcher who uses a screen reader asks the Aster County library for the commissioners’ minutes of March 1894, which sit in its labeled archive as page images. The library’s notice on every archive page gives an email address and a phone number. Staff log the request, send a corrected transcription of the six pages within the target turnaround, and then post that transcription beside the scans, so the next reader does not have to ask. At the end of the year the log shows that the 1893 to 1895 minutes were requested most often, and the library moves them to the top of its transcription plan.

Colorado public entities: the state law runs alongside

Colorado state agencies and local governments also have state duties. Colorado’s Office of Information Technology summarizes them on its digital accessibility law page: House Bill 21-1110 and Senate Bill 23-244, with rules that OIT amended in May 2025. OIT says an entity can be considered compliant with the state rules if it publishes a technology accessibility statement giving “two (2) methods of contact to request assistance” and meets at least one of five options, which include meeting the technical standards, providing an alternate version, providing reasonable accommodations, or publishing a plan showing progress. OIT also advises that public entities “should not remove inaccessible documents and resources from their websites.” Enforcement is through the courts, with a fine of $3,500 per violation or actual damages, according to the same page. The federal rule applies on its own terms and dates; ask your counsel how the two fit together for your office.

Where to start with a large backlog

No public institution will make every scanned page accessible by its compliance date, and the rule does not ask for that where the archived content exception genuinely applies. What it does ask is that the interface and new content conform, and that people can get what they need on request. A sensible order of work follows from that.

The American Library Association’s guidance on applying the rule suggests that “priority should be given to content that is currently used in courses, current subscribed content, and newly digitized content.” For a collection, that translates into three tiers:

Tier What goes in it Why it comes first
1 Search, browse, item pages, viewer; anything newly created or newly digitized from now on Generally not excepted; easier to build accessible than to fix later
2 Items used in exhibits, teaching, publications and frequent reference requests Likely outside the exception, and the most used
3 The rest of the archive, series by series, in order of demand Possibly excepted, but requests will come, and accessible text also improves search

Two habits make the backlog shrink rather than grow. First, build accessibility into each new digitization batch: text, descriptions and captions are produced with the images, not afterward. Second, keep the request log and let it reorder tier 3.

The practical work: text, descriptions, viewers and contracts

Most of the work of making a digitized collection accessible is the same work that makes it findable: accurate text for documents, good descriptions for images, captions and transcripts for recordings, structured pages and a viewer that works without a mouse. Plan it alongside digitization rather than after publication.

Text for scanned documents

For printed and typed material, OCR gives a text layer that screen readers can read, provided it is accurate enough and exposed as real text on the page or in a tagged PDF. A PDF with an invisible OCR layer but no tags may let a screen reader read the words while losing headings, columns and reading order, which criterion 1.3.1 asks you to preserve. For multi-column newspapers and tabular ledgers, text on an HTML page beside the image is often easier to make usable than a long PDF. For handwriting, handwritten text recognition followed by human correction, or a volunteer transcription, provides the same. Decide a correction level per kind of record, measure the error rate, and label uncorrected machine text as such so readers know what they are getting. Our text recognition page describes how we measure and correct, and the OCR accuracy calculator turns error counts into rates and correction hours.

Descriptions for photographs and objects

Photographs, maps and objects need text alternatives that convey what a sighted visitor gets from the image. The Cooper Hewitt’s Guidelines for Image Description are a widely shared museum reference. They describe alt text as a short description of “approximately fifteen words,” recommend starting “with the element(s) that are critical to understanding the image,” and say that “text within the image should be completely transcribed and shown within quotation marks.” Complex images, such as a crowded street scene or an annotated map, may need a longer description as well.

Machine-written descriptions can speed this up, but the Justice Department’s own finding in the 2026 interim final rule is that generative AI “does not yet reliably automate the remediation of inaccessible content at scale.” Treat machine descriptions as drafts, review them, and label any that remain unreviewed. Our AI policy explains how we label machine output.

Recordings

Oral histories, films and recorded talks need captions for video with sound under criterion 1.2.2, and either audio description or a full text alternative for information shown only visually under criterion 1.2.3. A transcript is the starting point for both and also makes the recording searchable.

Viewers and platforms

Test the viewer you publish with: zoom, page turning, downloads and search inside an item, all from a keyboard, with a screen reader announcing each control. If you use IIIF, the viewer is a separate piece of software from the image server, and you can choose or change it; our article Does a small museum or archive need IIIF? covers how the parts fit. Our collection search service publishes text alongside page images so that both readers and search engines get the words.

Contracts

Because the rule covers content provided “through contractual, licensing, or other arrangements,” write WCAG 2.1 Level AA conformance into contracts for digitization deliverables, hosted platforms and viewers. Ask vendors to document how their product conforms, test it yourself before renewal, and require accessible formats for delivered files, such as tagged PDFs and text in a standard format alongside images.

A plan for the months before your date

With your compliance date in April 2027 or April 2028, a public institution with an online collection can take these steps now, in roughly this order. They work whether you rely on the archived content exception or not.

  1. Confirm your status and date. Are you part of a state or local government, which population figure applies, and are you a special district? Write the answer and its source into your plan.
  2. Inventory what you publish. List the interface pages, item records, images, PDFs, recordings, exhibits and any content hosted for you by others.
  3. Fix the interface first. Search, browse, item pages and the viewer are used by everyone and are generally not excepted.
  4. Decide what goes in a labeled archive. For scans of historical originals kept for reference and research, set up a clearly identified archive area and a rule that archived files are not edited in place.
  5. Plan text and descriptions for new content. Anything newly written or newly built after your date, including transcriptions and exhibits, should be accessible when it goes up.
  6. Publish a request process. A visible contact, a turnaround target and a log of requests, plus Colorado’s two-contact-method statement if you are a Colorado public entity.
  7. Prioritize remediation by use. Start with the items people ask for and the series used in teaching, exhibits and research.
  8. Put accessibility in contracts. Require WCAG 2.1 Level AA for platforms, viewers and delivered files.
  9. Recheck the rule. The Department has signaled a possible proposal to revise parts of it, so confirm the dates and text on ADA.gov and the Federal Register before each budget cycle.

Our pages for local government records and for libraries and special collections describe how we deliver text, descriptions and records with accessibility in mind, and our own accessibility statement shows the kind of notice the rule’s guidance encourages. None of this is legal advice; for decisions about your collection, talk to your counsel and your ADA coordinator.

Working through this with a real collection?

If this article describes a decision you are facing, tell us about the collection. A pilot box answers most questions with your own material.

Plan a pilot box

Studio and contacts

24 South Weber Street, Suite 225
Colorado Springs, CO 80903
(719) 244-8450sales@dastok.com