Nobody Else Is Doing This: The Law Behind the Job
Trust note
This article was written by a person and reviewed against accessibility.chat editorial standards. Treat it as research and education rather than legal advice. We prioritize primary sources and correct material errors.
Two libraries in the same county can have compliance deadlines a year apart. The difference isn't collection size. It's corporate form.
There isn't an official role for this, which is probably why you're reading it. A director or branch manager absorbed digital accessibility the way small institutions absorb everything — by default, without a title change, without a budget line. This piece is sized for that reality.
Your first legal question is an org-chart question
Libraries are public entities under Title II of the ADA, and the web rule's WCAG 2.1 AA standard (opens in new window) applies. Which compliance tier is yours, though, depends on what your library actually is, corporately — not how big it feels day to day, and the answer surprises people in both directions.
A municipal or county library — a department or instrumentality of a city or county — takes its parent government's deadline. The web rule says an entity without its own Census population uses the population of the government it belongs to, so a city library in a large city lands in the earlier compliance tier along with the city, whatever the library's own budget looks like. An independent library district — a single-purpose entity created under state law — is a special district government, and the rule's text puts every special district in the later tier regardless of population served; the earlier tier expressly excludes them. A joint city-county library authority combines both parent populations.
Your establishing statute or intergovernmental agreement answers this in a paragraph. Find it before you assume anything about your timeline.
Licensed platforms are your content, not your vendor's problem to solve alone
The web rule covers content you provide "directly or through contractual, licensing, or other arrangements" — which is a precise description of a library's entire digital collection. Ebook and audiobook apps, research databases, the discovery layer, the events platform, the PC-booking system: all covered content, every one, because you arranged for patrons to have it. The rule's third-party exception protects genuinely unarranged content — a patron's comment on your Facebook post — not the platforms you license. Federal guidance says it plainly: outsourcing the work does not outsource the responsibility.
At one-librarian scale, that doesn't mean "remediate the vendors" — you can't. It means three cheaper things, covered in the rest of this series: demand the documentation, use renewal leverage, and document the bridge for what you can't fix yet.
The archive exception does real work, with two edges
The exception for archived content (opens in new window) was written for exactly the local-history scans, digitized newspaper morgues, and oral-history collections many libraries hold — and it works, if the material is kept in a clearly identified archive area, retained for reference and research, and unaltered. Two edges matter. The exception is lost the moment archived material gets pulled into a program, exhibit, or course — a finding-aid page you build for a heritage month display is current content, not archived content. And the accessible-on-request duty survives regardless: when a patron needs specific pages for their research, you provide them accessibly, which at this scale usually means OCR-and-structure just the requested pages, logged, while the rest of the archive stays exactly where it is.
What actually happens to small libraries
Nobody is making an example of small libraries, and that's genuinely not the risk here. The risk is the patron complaint that goes unanswered, the state statute that already applies — at least one state's accessibility law reaches library districts explicitly, with a grace period that's already ended and per-violation money damages on the table, years ahead of any federal date — and the renewal signed without asking a single accessibility question. Meanwhile the general effective-communication duty has bound every public library the whole time, deadline or no deadline.
None of this is legal advice, and it doesn't substitute for your own counsel confirming your library's corporate form and which deadlines actually apply. If you want a fast read on how a specific page measures up against WCAG 2.1 AA (opens in new window), ask Luke to check it. Our WCAG reference and methodology cover how we verify claims like these.
Next: your first ninety days — what to actually do with all of this, in stolen hours.
Sources: 28 CFR Part 35, Subpart H — Web and Mobile Accessibility (opens in new window) · 28 CFR 35.201 — Exceptions (opens in new window) · DOJ guidance on web accessibility and the ADA (opens in new window) · Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window)
About Jeff Fryer
Jeff Fryer spent years working kitchens before moving into ADA compliance work for local government. He writes from that experience -- direct, plainspoken, allergic to compliance theater. Contributing writer at accessibility.chat.
Jeff Fryer is a person, not one of the AI analyst lenses this site also publishes under. A named human is accountable for this article.
Specialization: Local government ADA compliance, contributed from direct field experience
Authorship and Editorial Process
Jeff Fryer wrote this article. AI was not used to draft it. It went through the same editorial checks as everything else published here.