ADA Title II Is Here: What Publishers Must Do BeforeApril 2026 (And Beyond)

For decades, accessibility in publishing was treated as a courtesy — a best practice that progressive publishers championed and others quietly deferred. That era is over.

On April 24, 2024, the U.S. Department of Justice (DOJ) finalized a landmark rule under Title II of the Americans with Disabilities Act (ADA), setting a firm, enforceable digital accessibility standard for public entities — and, critically, for every publisher that supplies content to them. The first major compliance deadline has arrived: April 24, 2026.

If your titles are sold to universities, public libraries, community colleges, or governmentaffiliated institutions, this regulation does not exist in the background. It sits squarely in your contract renewal conversations, your library procurement relationships, and your content production workflows. And the publishers who have already acted are pulling ahead — while those who have not are quietly accumulating risk.

This blog breaks down exactly what ADA Title II means for publishers, what the April 2026 deadline demands, and what “beyond” looks like for organizations that want to lead rather than catch up.

What Is ADA Title II — And Why Does It Reach Publishers?

Title II of the Americans with Disabilities Act prohibits discrimination on the basis of disability by state and local government entities. Since its passage in 1990, it has been interpreted through legal challenges, consent decrees, and informal guidance. What changed in April 2024 is that the DOJ finally gave it digital teeth.

The new rule formally adopts the Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA as the technical standard for all state and local government digital services — websites, mobile applications, digital documents, online course content, and more.

Here is where publishers need to pay close attention: public institutions are responsible for the accessibility of content provided to them through licensing or contractual arrangements. A university library cannot outsource its compliance by simply pointing to a publisher’s inaccessible EPUB. The obligation flows upstream. As a result, publishers who supply digital content to covered public entities are now at the center of their customers’ compliance obligations — whether they intended to be or not.

The compliance timeline is structured around population size:

• April 24, 2026 — Public entities serving populations of 50,000 or more

• April 26, 2027 — Smaller jurisdictions and special district governments

Most major academic publishers sell to institutions that fall under the April 2026 deadline. State universities, county library systems, and public community colleges are all covered, regardless of enrollment size, because compliance is based on the government body’s population — not the number of students or patrons served.

What WCAG 2.1 AA Requires: The Four Pillars

WCAG 2.1 Level AA compliance is built around four foundational principles — often referred to by the acronym POUR:

• Perceivable — Content must be presentable in ways all users can perceive. This means meaningful alternative text for images, captions and transcripts for multimedia, sufficient color contrast, and adaptable layouts that work with assistive technologies.

• Operable — Every feature must be fully navigable by keyboard, with no mouse dependency. This is critical for users with motor impairments who rely on keyboard navigation, switch controls, or eye-tracking devices.

• Understandable — Navigation must be consistent and predictable. Language must be identified. Error messages must be clear and helpful.

• Robust — Content must be reliably interpreted by current and future assistive technologies, including screen readers, voice recognition software, and text-to-speech tools.

For publishers, this translates into highly specific production decisions: how images are tagged, how tables are structured, how math and scientific notation is marked up, how reading order is encoded in EPUB files, and how PDFs are built from the ground up. None of this can be retrofitted with an overlay tool or a quick accessibility checker. It requires expertise embedded in the production process itself.

The Publisher’s Exposure: Three Ways Title II Reaches Your Business

1. Library and Institutional Procurement

Libraries and academic institutions are now requiring up-to-date Accessibility Conformance Reports (ACRs) — completed Voluntary Product Accessibility Templates (VPATs) — as a standard part of vendor evaluation. Publishers who cannot demonstrate WCAG 2.1 AA conformance are increasingly being passed over at the procurement stage, or are finding existing contracts at risk upon renewal. An ACR is not a certificate of perfect compliance. It is an honest, evidence-based documentation of where your content and platforms currently stand against each WCAG success criterion — what is supported, what is partially supported, what is not supported, and what your remediation timeline looks like. Procurement offices are becoming more sophisticated in reading these documents. A vague or unsubstantiated ACR that claims full conformance across the board is viewed with increasing skepticism by accessibility-literate reviewers.

2. Third-Party Vendor Accountability

Title II explicitly prohibits discrimination “carried out through contractual or other arrangements.” This means that if a university library subscribes to your platform and that platform is inaccessible to a student using a screen reader, the institution bears legal exposure — and will look to its contract with you for relief. Publishers who cannot demonstrate accessibility may find themselves in breach of warranty clauses that libraries are now routinely inserting into licensing agreements.

Major research library consortia are already embedding specific language requiring WCAG 2.1 AA conformance, ongoing accessibility statements, and obligations to remediate identified issues within defined timeframes. If you are not reviewing your current licensing agreements through this lens, now is the time to start.

3. Course Adoption and Educational Content

For publishers whose titles are adopted into university curricula — textbooks, supplemental readings, journal access — accessibility is no longer a differentiator. It is a prerequisite. Faculty accessibility coordinators and disability services offices are actively involved in content procurement decisions. An inaccessible eTextbook can block a student with a visual impairment from completing coursework, triggering ADA complaints that lead directly back to the institution’s content supplier.

The Backlist Problem: Your Biggest Hidden

Liability Most publishers have a manageable grip on frontlist accessibility — new titles can be built to standard from the first keystroke if the workflow is designed correctly. The real complexity lies in the backlist.

Thousands of PDFs, EPUBs, and legacy digital files produced under older standards now represent a compliance risk that grows with every new institutional contract. The question is not whether these titles need remediation — they do — but how to approach that remediation without paralyzing production schedules or destroying budget.

A practical approach involves three stages:

• Audit and triage.

  Before remediating anything, understand what you have. Automated scanning tools like ACE by DAISY for EPUBs or Acrobat’s accessibility checker for PDFs can surface issues quickly, but it is important to know that automated tools typically catch only 30–40% of WCAG issues. Manual testing with actual assistive technologies is essential for a complete picture.

• Prioritize by demand and risk.

  Not every backlist title carries equal exposure. Titles actively used in course adoptions, licensed to major university systems, or featured in library discovery platforms should be prioritized for remediation. High-demand, high-traffic titles represent both the greatest compliance risk and the greatest commercial benefit from being made accessible.

• Build a documented roadmap.

  Libraries and institutions do not expect overnight perfection. What they increasingly require is transparency: a clear, credible plan that documents current status, identifies gaps, and commits to timelines. An ACR with honest “Partially Supports” entries and a concrete remediation schedule carries more credibility — and more legal defensibility — than one that overstates conformance.

VPAT and ACR: The Documents That Now Drive Procurement

The VPAT (Voluntary Product Accessibility Template), maintained by the Information Technology Industry Council, is the standardized format publishers use to document accessibility conformance. When completed based on actual testing, the filled document becomes an ACR — the Accessibility Conformance Report.

For most academic publishers, the VPAT 2.5Rev WCAG or International (INT) edition is the appropriate choice. The current versions, updated in April 2025, should be used for all new documentation.

A few principles for producing credible ACR documentation:

• Base it on real testing, not scanner output alone.

  Automated scans catch a fraction of WCAG issues. Dynamic content, custom form controls, modal dialogs, tables, and embedded multimedia all require manual testing with screen readers such as NVDA, JAWS, or VoiceOver to assess accurately. ACRs built solely on automated output are recognizable to procurement reviewers and damage credibility.

• Be specific about gaps.

  An entry that reads “Does Not Support — missing alt text on figures in Chapter 4, remediation planned Q3 2026” is more valuable than one that vaguely claims partial conformance. Specificity builds trust and creates a defensible paper trail.

• Third-party audits carry more weight.

  Self-authored ACRs are permissible, but independently audited ACRs are treated with considerably more confidence in procurement contexts. The investment in third-party validation often pays for itself in contract velocity.

• Update regularly.

  An ACR is not a one-time document. It should be updated with every major product release and reviewed at least every 12–16 months. Outdated ACRs can create liability if they claim conformance that no longer reflects the product’s actual state.

Born Accessible vs. Remediation: Why the Production Workflow Is the Real Answer

The publishers who will face the least friction going forward are not those doing the most remediation — they are those who have redesigned their production workflows to produce accessible content from the start.

“Born accessible” content is WCAG-conformant from the point of creation. This means structured tagging is applied at the authoring stage, not added later. It means alt text is written by subject-matter-aware editors before a file is exported to PDF or EPUB. It means reading order, heading hierarchies, and table structure are verified as part of the standard production checklist — not as an afterthought.

The economic case for born-accessible production is straightforward. Retrofitting an inaccessible EPUB can cost many times more than building it correctly the first time, particularly for complex content — STEM titles with equations, medical textbooks with dense imagery, or journals with complex data tables. When remediation is the fallback strategy, that cost is paid repeatedly, at scale, against a growing backlist that never stops growing.

The more compelling argument for a born-accessible workflow is institutional: it positions the publisher as a partner in compliance, not a source of compliance risk. That distinction is increasingly visible in procurement scoring.

What “Beyond April 2026” Looks Like

The April 2026 deadline is not an end state — it is a baseline. Several developments on the horizon will continue raising the bar:

• WCAG 2.2 is already the smarter target.

  While Title II mandates WCAG 2.1 AA, WCAG 2.2 adds nine new success criteria — particularly around mobile navigation and cognitive accessibility — and is the direction the industry is moving. Publishers who build to 2.2 now will not need to revisit their workflows when the standard inevitably becomes the legal benchmark.

• The European Accessibility Act (EAA) is already in force.

  Publishers with EU market exposure have been operating under EAA requirements since June 2025, with backlist remediation deadlines extending to 2030. For publishers operating across both markets, the EAA and ADA Title II effectively converge on the same technical standard: WCAG 2.1 AA. A single, well-executed accessibility program can address both.

• AI-assisted accessibility tools are maturing rapidly.

  From automated alt-text generation to AI-driven PDF remediation and EPUB conversion, technology is beginning to make highvolume accessibility compliance economically viable even for large backlists. The key distinction is between tools that automate accuracy and tools that simply automate speed. Quality outcomes still require human expertise applied at critical checkpoints — particularly for scientific, mathematical, or highly visual content where AI-generated descriptions need domain knowledge to be genuinely useful.

• Accessibility metadata will become a commercial asset.

  Publishers who embed accessibility metadata correctly into their EPUB files — flagging screen-reader compatibility, structural navigation, alt-text coverage, and reading order — will gain discoverability advantages in library and institutional platforms that surface this information to buyers. Accessibility is increasingly a filter in academic content procurement, not just a compliance requirement.

How S4Carlisle Supports Publishers on This Journey

S4Carlisle brings over 50 years of publishing expertise and a Benetech Global Certified Accessible™ (GCA) vendor designation to the specific challenges that ADA Title II creates for publishers.

Our NINJA AI Ecosystem is built for exactly this landscape — automating the validation of PDF and EPUB accessibility against WCAG standards, generating procurement-ready VPAT and ACR documentation, and identifying compliance gaps at scale before they become institutional liability. With over 10 million pages processed through our conversion and accessibility workflows, we have the operational depth to handle both frontlist production and high-volume backlist remediation.

Our approach is not simply to produce conformant files — it is to build the kind of transparent, documented, auditable accessibility programs that survive library procurement scrutiny, hold up in vendor certification reviews, and position publishers as trusted partners in their customers’ compliance journeys.

The Bottom Line

ADA Title II has transformed digital accessibility from a recommended practice into a legal and commercial imperative. For publishers supplying content to public academic and library institutions, the question is no longer whether to invest in accessibility — it is how quickly you can build a program that is systematic, documented, and defensible.

The publishers that move now will find that accessibility compliance is not a cost center. It is a competitive position: a prerequisite for library procurement, a differentiator in course adoption, and a foundation for sustainable growth in the institutional market.

The deadline is April 24, 2026. Beyond it lies a publishing landscape where accessibility is simply the standard — and where your documentation, your workflows, and your partnerships will determine whether you lead it or chase it.

S4Carlisle Publishing Services is a Benetech Global Certified Accessible™ vendor with over 50 years of publishing expertise. Our NINJA AI Ecosystem helps publishers audit, remediate, and document accessibility conformance at scale — from individual titles to enterprise-wide programs. Contact sales@s4carlisle.com to learn how we can support your accessibility compliance journey.