Section 508 and ADA Title II: Converting PDFs to Accessible EPUB3 for Agencies and Universities

ADA Title II compliance deadline is April 26, 2027 for larger state and local government entities (50,000+ population), and April 2028 for smaller entities. The DOJ extended these deadlines to give organizations more time to prepare — but with EAA enforcement already active in the EU, the window to build accessible document workflows is now. Section 508 has applied to federal agencies and contractors for decades. Both laws reference WCAG 2.x as their technical standard — and PDFs, in virtually every real-world deployment, fail that standard.

EPUB3 passes it by design.

This guide explains what Section 508 and ADA Title II require for documents, why PDF/UA falls short, and how converting PDF to EPUB3 using toolkit.bot/pdf2epub satisfies US accessibility law in under a minute.

What Section 508 and ADA Title II Require for Documents

Section 508 (29 U.S.C. § 794d) applies to federal agencies and contractors that develop, procure, maintain, or use electronic and information technology. The 2017 Refresh aligned Section 508 with WCAG 2.0 AA as the minimum technical standard for web content and electronic documents.

ADA Title II applies to state and local governments. The DOJ's April 2024 final rule requires WCAG 2.1 AA conformance for web content and mobile apps — and documents posted to government websites are explicitly in scope. The compliance deadline is April 26, 2027 for entities with 50,000+ population or service area; smaller entities have an April 2028 deadline. The DOJ extended these deadlines due to compliance resource constraints.

The key WCAG criteria that most PDFs fail:

• 1.1.1 Non-text Content: Images must have text alternatives. Scanned PDFs — images of pages — have none.
• 1.3.1 Info and Relationships: Document structure (headings, lists, tables) must be programmatically determinable. A PDF's visual layout is not.
• 1.3.2 Meaningful Sequence: Reading order must be correct when linearized. PDFs with multi-column layouts or sidebars almost always fail this.
• 1.4.10 Reflow: Content must reflow at 400% zoom without horizontal scrolling. Fixed-page PDFs cannot do this.
• 2.4.2 Page Titled: Documents must have descriptive titles. Most PDFs lack proper metadata.
• 3.1.1 Language of Page: The document language must be programmatically identified.

Tagged PDF (PDF/UA) was designed to address some of these gaps — but it falls short in practice.

ADA Title II, April 2027: What Public Entities Must Cover

For IT accessibility coordinators, disability services officers and legal teams at universities, municipal agencies and public libraries, the deadline means auditing document libraries that have accumulated over decades. Most are well prepared for web accessibility; documents are where the gap emerges. Under the rule, every document a public entity distributes must meet all applicable WCAG 2.1 AA criteria, including 1.4.10. That covers:

• PDFs on the website and intranet
• Documents emailed to students, residents or service recipients
• Scanned documents made available for download
• Course materials distributed through LMS platforms
• Publicly posted meeting agendas and minutes
• Applications, forms and notices, accessibility reports, grant applications and ADA transition plans

Reflow is the criterion remediation cannot reach, and it matters for users who set large device text sizes, screen-magnification users at 400%, mobile readers, braille display users, and anyone who cannot scroll horizontally because of motor limitations. Two-column papers, formatted reports, newsletters and multi-field forms all fail it as PDF. Providing an accessible alternative in another format (EPUB3 or HTML) with equivalent content is an accepted compliance path; documents still publicly linked are in scope, while unlinked archives have more flexibility (confirm with counsel).

A phased programme that fits the timeline:

1. Now – October 2026: audit. Inventory all publicly accessible PDFs; prioritize by use frequency and risk; flag anything with a multi-column or non-standard layout as a 1.4.10 failure.
2. November 2026 – February 2027: remediate. PDF remediation for simple documents; EPUB3 conversion for anything that cannot satisfy 1.4.10 as PDF, offered alongside the existing PDF.
3. March – April 2027: verify. ACE by DAISY reports on the EPUB3 output, VPAT documentation where required, and published accessibility statements for the document libraries.

Why PDF/UA Still Falls Short

PDF/UA (ISO 14289) is the PDF accessibility standard. It requires tags, reading order, language, and alt text. In theory, a fully compliant PDF/UA file should satisfy Section 508. In practice:

• Reflow is not reflowable: PDF/UA does not fix WCAG 1.4.10. Tagged PDFs still present fixed-dimension pages. At 400% zoom, multi-column content overflows. WCAG 1.4.10 requires content to reflow to a single column without loss of information — tagged PDFs cannot do this for complex layouts.
• Multi-column reading order: Even correctly tagged PDFs frequently present two-column content out of sequence to screen readers. The PDF tagging model was designed for visual order — not logical linearization of complex layouts.
• Authoring friction: Producing a genuine PDF/UA file requires specialist tooling (Adobe Acrobat Pro with accessibility checking, axesPDF, or CommonLook) and manual remediation. Most agencies' existing PDF libraries were never produced to this standard.
• Remediation cost: Retroactively tagging a large PDF library is a multi-year project costing thousands of dollars per document for complex layouts.

EPUB3 avoids all of these problems.

Why EPUB3 Satisfies Section 508 and ADA Title II Requirements

EPUB3 is built on HTML5 and CSS — the same technologies that power accessible web pages. WCAG 2.x applies directly to EPUB3 content. The EPUB Accessibility 1.1 specification (a W3C standard) formalizes how to produce and declare conformant EPUB3 files.

• Reflow is inherent: EPUB3 is reflowable by design. Text wraps at any viewport width or zoom level. WCAG 1.4.10 passes by default on every device.
• Semantic structure is enforced: HTML heading tags (h1–h6), list elements, and table markup map directly to WCAG 1.3.1. There is no separate "tagging" layer — the structure is the format.
• Reading order is explicit: HTML source order defines reading order. A correctly structured EPUB3 always presents content in the right sequence to NVDA, JAWS, and VoiceOver — regardless of layout complexity.
• Navigation is built in: EPUB3 requires a navigation document (nav.xhtml) with a table of contents. This maps directly to ARIA landmark navigation and WCAG 2.4.1.
• Language is required: EPUB3 package metadata must include a language declaration. WCAG 3.1.1 is satisfied structurally.
• EPUB Accessibility 1.1 metadata: Conformance metadata embedded in the EPUB package allows procurement tools, screen readers, and automated checkers to verify accessibility claims before distribution.

How toolkit.bot Produces Section 508-Compliant EPUB3 Output

toolkit.bot converts any PDF to EPUB3 with EPUB Accessibility 1.1 metadata in approximately 30 seconds. The conversion pipeline:

1. Text extraction and OCR: For native PDFs, text is extracted with layout analysis. For scanned PDFs (images of pages), OCR runs automatically — producing searchable, screen-reader-readable text where the PDF had none.
2. Heading detection: Font size, weight, and position are analyzed to infer heading hierarchy. The output uses H1–H6 tags in correct semantic order.
3. Multi-column layout handling: Two-column and sidebar content is linearized into correct reading order. Academic papers, government reports, and legal documents — which are almost always multi-column — are handled explicitly.
4. Table structure: Tables are extracted as HTML table elements with proper thead/tbody/th markup — not as text blocks or images.
5. Language metadata: Language is detected and written to the EPUB package metadata automatically.
6. EPUB Accessibility 1.1 metadata: Each output file includes accessibility metadata targeting EPUB Accessibility 1.1.

The result is an EPUB3 file that passes ACE by DAISY automated checking and is readable by NVDA, JAWS, and VoiceOver in correct reading order.

PDF/UA vs EPUB3: Accessibility Comparison

Workflow for Government Agencies with Large PDF Libraries

ADA Title II compliance does not require converting every document on day one. The DOJ rule includes a prioritization principle: agencies should prioritize frequently accessed content, content posted after the compliance date, and content specifically requested by people with disabilities.

A practical phased approach:

1. Audit your library: Identify the 20% of documents that receive 80% of traffic. These are your conversion priority.
2. Convert high-priority documents: Use toolkit.bot/pdf2epub for individual documents (free, no account required) or the toolkit.bot API for batch conversion of your priority list.
3. Validate: Run each converted EPUB through ACE by DAISY (free, open source). Address any flagged issues — typically missing alt text on charts and images.
4. Post EPUB alongside or instead of PDF: For web distribution, EPUB3 files are supported natively on iOS (Apple Books), Android, and via browser extensions. For procurement and internal distribution, EPUB3 is accepted by all major reading systems.
5. Establish a new-document policy: All documents posted after your compliance date should be converted to EPUB3 before publication. The toolkit.bot API supports integration into document management workflows.

For agencies with thousands of legacy documents, the toolkit.bot premium plan provides higher API rate limits and priority processing for bulk conversion projects. See the accessibility teams page for procurement details.

Who Is Covered

Section 508: Federal agencies, programs that receive federal financial assistance, and federal contractors that develop, procure, maintain, or use electronic and information technology. This includes documents published on agency websites, documents sent to the public as part of agency services, and documents procured from vendors.

ADA Title II: All state and local government entities — cities, counties, state agencies, public schools, public universities, court systems, and transit agencies. The April 26, 2027 deadline applies to entities with 50,000+ population or service area; smaller entities have an April 2028 deadline.

If your agency publishes PDFs to the web — policy documents, forms, reports, meeting minutes, permits, or any other public-facing document — those are in scope.

Higher Education: Course Materials Are the Primary Gap

Public universities, community colleges and state-run institutions fall under Title II, and their most common gap is not the website but the documents: syllabi, lecture notes, textbook excerpts, assigned journal articles, policy handbooks and academic reports, almost all distributed as PDF. Documents posted to university sites are in scope, PDFs uploaded to Blackboard, Canvas or Moodle are in scope, and materials a student with a disability requests must be provided in an accessible format. The DOJ rule permits prioritizing recently posted, frequently accessed and specifically requested content, so institutions can phase the work.

Four structural reasons the backlog is hard: volume (thousands of PDFs per semester across hundreds of courses); authorship (faculty create the materials with no accessibility training or tooling); legacy reuse (a 2015 syllabus is often unchanged in 2026); and multi-column journal articles, typeset for print, which are nearly impossible to remediate in PDF without rebuilding the document. PDF/UA does not rescue this: Reflow still fails, specialist per-document tagging does not scale to 5,000 files, and two-column articles cannot be reliably linearized in the PDF tag tree.

A workable programme for a course-material library:

1. Current-semester materials first. Anything actively assigned is the highest-risk item; convert immediately.
2. Individual documents through toolkit.bot/pdf2epub. A 30-page paper converts in under a minute; no account or install.
3. LMS and repository volumes through the API. Upload a PDF, receive an EPUB3, integrated ahead of the LMS upload step.
4. Validate with ACE by DAISY and keep the HTML reports as the audit trail.
5. Post EPUB3 alongside or instead of PDF. EPUB3 opens natively on iOS and Android and in Canvas and other modern reading systems.
6. Set a policy for new materials: faculty submit PDFs, conversion runs before upload, every post-deadline document ships with an EPUB3.

The multi-column case. A two-column article from Nature, the American Journal of Public Health or IEEE Transactions interleaves headers, footnotes, captions and tables across columns. In PDF, a screen reader typically reads across the full page width, mixing the columns or jumping from mid-column to a footnote and back. Rebuilding the reading-order tag tree in Acrobat Pro takes an experienced specialist roughly 30–90 minutes per paper. Conversion detects the columns and linearizes them before generating the EPUB3, in under a minute per paper, so a student on NVDA or VoiceOver hears the text in sequence. For a course with 15 assigned readings, that is 15 hours of specialist remediation replaced by about 15 minutes of conversion.

Related guides

• How PDF-to-EPUB3 satisfies the European Accessibility Act (2026)
• PDF to accessible EPUB: guide for libraries and accessibility teams
• EPUB accessibility checker: ACE vs Pagina vs EPUBCheck
• Best PDF to EPUB converter for screen readers
• EAA 2026: what publishers must do about PDFs