Library Website Accessibility Guide 2026 | DOJ Title II, ADA, WCAG 2.1 AA

Last updated: 2026-05-01

Public, academic, and school libraries entered a new regulatory environment in April 2026: the Department of Justice's 2024 Title II Final Rule formally requires every state and local government website—and every web content and mobile app a covered entity makes available to the public—to conform to WCAG 2.1 AA. The compliance deadline is April 24, 2026 for large public entities (population 50,000 and above) and April 24, 2027 for small public entities. Libraries sit squarely inside this rule because they are administered by municipalities, counties, school districts, public universities, and special-purpose library districts—every one of which is a public entity under Title II. The Title II rule does not stop at the library's marketing pages: it extends to the online public access catalog (OPAC), the e-book and audiobook lending platforms (OverDrive/Libby, hoopla, CloudLibrary, Axis 360), the digital reference databases (EBSCO, ProQuest, Gale), the room-reservation system, the museum-pass reservation system, the summer-reading registration form, the children's programming calendar, the public-PC reservation kiosk, and any third-party digital service the library authenticates patrons into. Academic libraries operating in federally-funded universities face the same WCAG 2.1 AA bar under Section 504 of the Rehabilitation Act and—when serving federal-government users—under Section 508. Library directors and IT staff also face a procurement question that did not previously exist: every vendor contract signed or renewed since April 2026 should require a current VPAT, a documented WCAG 2.1 AA conformance claim, and a remediation timeline for any known defects. This guide covers the Title II framework, the specific failure modes that recur in library-platform audits, and a concrete compliance checklist for public, academic, and school libraries.

Legal Requirements

Law / Standard Effective Date Summary Penalty
DOJ Title II Final Rule (28 CFR Part 35, Subpart H) 2026-04-24 The DOJ's 2024 Title II Final Rule requires every state and local government's web content and mobile applications to conform to WCAG 2.1 Level AA. The rule applies to the library's own site, every third-party platform the library makes available to the public (OverDrive/Libby, hoopla, OPAC, research databases, room-reservation systems), and every PDF, video, and document the library posts. The compliance deadline is April 24, 2026 for public entities serving populations of 50,000 or more, and April 24, 2027 for smaller public entities and special-purpose districts. DOJ enforcement actions, injunctive relief, and—for federally-funded libraries—loss of Library Services and Technology Act (LSTA) and IMLS grant eligibility. Private litigation under Title II is also available, with attorneys'-fee shifting under 42 U.S.C. § 12205.
Americans with Disabilities Act (ADA) Title II In effect Beyond the 2024 Final Rule, ADA Title II's general anti-discrimination provisions have applied to library websites since 2010. Title II requires that public entities provide effective communication and equal access to programs, services, and activities, including those delivered through websites and digital platforms. Injunctive relief, attorneys' fees, and—when discrimination is intentional—compensatory damages.
Section 504 of the Rehabilitation Act In effect Section 504 applies to any library receiving federal financial assistance, including LSTA grants from IMLS, federal documents depository status, and academic libraries inside federally-funded universities. WCAG 2.1 AA is the operative conformance standard under the Department of Education's interpretive guidance and recent OCR resolution agreements with university libraries. Loss of federal funding eligibility; OCR-imposed corrective-action plans; private right of action with attorneys' fees.
Section 508 of the Rehabilitation Act In effect Federal libraries (Library of Congress, federal-agency libraries, NIH library, etc.) and any library system serving federal employees through a federally-procured platform must conform to the Section 508 Refresh, which incorporates WCAG 2.0 Level AA and additional functional performance criteria. Procurement of digital library platforms by federal agencies must include Section 508 conformance language and VPAT review. Federal procurement bid disqualification; GAO and Access Board complaint adjudication; civil-service complaints under 29 U.S.C. § 794d.
State digital-accessibility statutes In effect Several states (California AB 434, Colorado HB 21-1110, Texas TGC §2054.451, Minnesota Stat. §16E.03 Subd. 9) impose digital-accessibility obligations on state and local government entities, including libraries, that are independent of and sometimes stricter than the federal Title II baseline. Colorado in particular permits private lawsuits with statutory damages. Varies by state. Colorado allows civil penalties up to $3,500 per violation per day plus attorneys' fees; California Unruh Act exposure ($4,000 per visit) attaches to public-entity sites in some circuits.

Key Accessibility Issues in Public & Academic Libraries

OPAC Search Interfaces That Fail Keyboard Navigation and Screen-Reader Use

The online public access catalog is the single most-used surface on a library's digital footprint, and it is the surface most likely to fail an accessibility audit. The dominant OPAC vendors—SirsiDynix Enterprise/BLUEcloud, Innovative Polaris and Sierra, Ex Libris Primo, OCLC WorldCat Discovery, EBSCO EDS, Koha, and Evergreen—each ship discovery layers built on heavy JavaScript with custom-styled facet menus, modal hold-placement dialogs, infinite-scroll search results, and result-detail pages that re-render without announcing changes to assistive technology. Common failures include facet checkboxes that cannot be reached with the Tab key, hold-placement modals that trap focus and intercept the Escape key, search-result pagination that requires a mouse hover, and call-number / shelf-location data displayed as visual-only icons without programmatically-determinable text.

How to fix:

Request a current VPAT from your discovery-layer vendor and review it against the actual catalog—VPATs are sometimes aspirational. Test the OPAC with NVDA, JAWS, and VoiceOver while operating keyboard-only. Document every failure and open a formal vendor support ticket citing WCAG 2.1 AA and the contract's accessibility-warranty clause. If the vendor's discovery layer cannot be remediated, many libraries are now deploying a Bento-style accessible-front-end (often Blacklight or VuFind) that queries the catalog API and renders results in a layer the library controls. Maintain a documented alternative: a phone, email, or chat reference channel staffed by a librarian who can search the catalog on behalf of patrons who cannot use the OPAC.

OverDrive / Libby, Hoopla, and CloudLibrary E-Book Platforms

Patron-facing e-book and audiobook lending platforms are deployed by the library, branded with the library's logo, and authenticated through the library's patron database—and are consistently treated by DOJ and OCR as a service the library provides. Unfortunately the apps and websites have a long and documented history of accessibility defects, including Libby's swipe-only navigation gestures on mobile that have no keyboard alternative on the web client, hoopla's video-player controls that cannot be tabbed to, CloudLibrary's borrow-confirmation modal that traps focus, and the EPUB readers' inconsistent support for screen-reader text-to-speech across formats. Libraries cannot fix vendor code, but Title II makes the library responsible for the user experience of services it offers.

How to fix:

Add accessibility-conformance language to every renewal of the OverDrive, hoopla, CloudLibrary, and Axis 360 contract, citing WCAG 2.1 AA and the DOJ Title II rule. Require a VPAT at each renewal and compare it year over year. Publish a Library Digital Accessibility Statement that names each third-party platform, links to the vendor's accessibility statement, and provides a library staff contact who can help a patron access content the patron cannot independently retrieve. For audiobooks specifically, BARD (Braille and Audio Reading Download) from the National Library Service is a fully-accessible alternative for eligible patrons—document referral procedures.

Programming Calendars, Room Reservations, and Museum-Pass Booking

Most public libraries use one of LibCal (Springshare), Communico, Burlington English, or a custom integration to manage programming registration, study-room reservations, museum-pass checkout, and tutor scheduling. These systems frequently ship calendar widgets that fail focus-order requirements, use color alone to indicate availability, present time-slot grids without screen-reader-accessible table headers, and trigger date-picker modals that cannot be operated with arrow keys. Children's programming registration in particular tends to be a high-stakes flow—story-time and STEAM-program slots fill within minutes of release—and an inaccessible registration system effectively excludes patrons who use assistive technology.

How to fix:

Audit the programming-calendar widget against WCAG 2.1 AA Success Criteria 1.3.1, 1.4.1, 2.1.1, 2.4.7, 2.5.7, and 4.1.2. Require the vendor to address documented defects through the support channel, citing the Title II compliance deadline. For high-demand registration events, offer a documented telephone-registration window opening at the same time as online registration so patrons blocked by the calendar widget have an equal opportunity to register.

Library-Hosted PDFs, Local-History Documents, and Government-Document Scans

Libraries are large publishers of PDF content: agendas and minutes for the library board, local-history pamphlets, genealogy guides, scanned newspaper archives, depository-collection government documents, and downloadable program flyers. The 2024 Title II Final Rule explicitly covers PDFs and other documents posted to library websites. Audits routinely find that the great majority of these PDFs are scanned images with no OCR text layer, lack tagged structure, lack alt text on embedded images, lack document language declaration, lack a defined reading order, and lack form-field labels where the PDF includes interactive forms. Local-history collections and scanned newspapers are particularly problematic because they are large, old, and image-only by nature.

How to fix:

Establish a PDF accessibility policy that distinguishes between (a) born-digital PDFs the library creates—every one of which must be tagged, OCR'd, alt-text'd, and conform to PDF/UA at the time of posting—and (b) historical scanned content where the library should provide an OCR text layer at minimum and a documented request channel to obtain a fully-accessible alternative format on demand. For new documents, train staff on Adobe Acrobat Pro's accessibility checker and the Microsoft Word accessibility checker. Replace PDFs with HTML pages where possible (board minutes, program calendars, policy documents) since HTML is structurally easier to make accessible than PDF. The DOJ Title II rule allows a narrow archived-content exception for PDFs posted before April 2026 and not currently in active use, but documents in active use must conform.

Children's and Teen Section Pages With Decorative Animation, Color-Coded Reading Lists, and Image-Only Reading Logs

Children's and youth-services pages on library sites are often the visually richest sections of the site and the least audited. Common defects include summer-reading reading-log forms built as image maps of bingo cards with no text alternative, reading-level recommendations conveyed by color-coded category dots without text labels, animated decorative SVGs without prefers-reduced-motion handling, video booktalks without captions, and teen-services discussion-board widgets embedded from third parties without accessibility review. Children with disabilities are an explicit protected class under both Title II and IDEA, and inaccessible programming pages can produce parallel OCR complaints if the library is administered by a school district.

How to fix:

Apply the same accessibility bar to youth-services content as to adult-services content. Replace color-only categorization with text labels plus color. Provide a downloadable plain-text or HTML alternative for every summer-reading bingo card and reading log. Caption every booktalk video and every story-time recording. Honor prefers-reduced-motion in CSS for animated decorative elements. If the library is part of a school district, coordinate accessibility policy with the district Section 504 coordinator.

Compliance Checklist

  • Library website meets WCAG 2.1 AA in time for the April 2026 (large entities) or April 2027 (small entities) DOJ Title II deadline
  • Discovery-layer / OPAC vendor (SirsiDynix, Innovative, Ex Libris, OCLC, EBSCO, Koha, Evergreen) has provided a current VPAT and the library has independently verified its accuracy with a keyboard + screen-reader audit
  • OverDrive/Libby, hoopla, CloudLibrary, Axis 360, and any other patron-facing lending platform has WCAG 2.1 AA conformance language in the current contract
  • Research-database vendors (EBSCO, ProQuest, Gale, JSTOR, etc.) have provided VPATs and have a documented remediation roadmap for any known defects
  • Programming-calendar, room-reservation, and museum-pass platforms (LibCal, Communico, etc.) have been audited and a phone-registration alternative is documented
  • Library Digital Accessibility Statement is published, names each third-party platform, links to vendor accessibility statements, and provides a staff contact
  • PDF accessibility policy distinguishes born-digital documents (must be tagged at posting) from historical scanned content (OCR layer + alternative-format request channel)
  • All board agendas, minutes, and policy documents posted since April 2026 are tagged PDFs or HTML
  • Online forms (library card application, reference question, ILL request, summer-reading registration) have visible labels, programmatic associations, and accessible error handling
  • Public-PC reservation kiosk and self-checkout interfaces meet ADA Title II accessible-kiosk requirements (audio output jack, keyboard input, screen-reader software)
  • Staff training on accessibility has been documented within the past 12 months for IT, web-services, public-services, and youth-services teams

Further Reading

Other Industry Guides