Does Section 508 apply to PDF documents?

Yes. Section 508 requires electronic documents distributed by federal agencies and contractors to meet WCAG 2.0 AA. This includes PDFs posted to websites and sent to the public. Most PDFs fail WCAG 1.4.10 (reflow) and 1.3.2 (meaningful sequence) — EPUB3 satisfies both by design.

Does ADA Title II require government PDFs to be accessible?

Yes. The DOJ's 2024 final rule under ADA Title II requires state and local governments to make web content and digital documents WCAG 2.1 AA compliant. Documents posted to government websites — reports, forms, permits, meeting minutes — are explicitly in scope. The compliance deadline for jurisdictions with 50,000+ population is April 26, 2027; smaller entities have an April 2028 deadline.

What is the difference between PDF/UA and EPUB3 for accessibility?

PDF/UA (ISO 14289) is the PDF accessibility standard. It addresses structure tags, reading order, and alt text but does not fix reflow (WCAG 1.4.10) — tagged PDFs still present fixed-dimension pages that fail at 400% zoom. EPUB3 is reflowable by design, uses native HTML semantics, and consistently delivers correct reading order to NVDA, JAWS, and VoiceOver. EPUB3 is easier to produce, easier to validate (ACE by DAISY is free), and cheaper to maintain at scale.

How do I batch-convert a government PDF library to EPUB3?

Use the toolkit.bot API (toolkit.bot/docs) to convert PDFs programmatically. The API accepts PDF uploads and returns EPUB3 files with EPUB Accessibility 1.1 metadata. For large-volume projects, the premium plan provides higher rate limits. A typical workflow: identify high-priority documents → batch convert via API → validate with ACE by DAISY → post EPUB3 files alongside or instead of PDFs.

Does converting to EPUB3 fully satisfy Section 508?

Converting to EPUB3 addresses the format-level accessibility failures that prevent PDF from satisfying WCAG 2.x. For full compliance, also validate with ACE by DAISY, add alt text for charts and diagrams that lack descriptions in the source PDF, and test with a screen reader (NVDA + Firefox on Windows, VoiceOver on Mac) for your highest-priority documents. Automated tools catch approximately 30–40% of accessibility issues; manual testing covers the rest.

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

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.

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:

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.
Heading detection: Font size, weight, and position are analyzed to infer heading hierarchy. The output uses H1–H6 tags in correct semantic order.
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.
Table structure: Tables are extracted as HTML table elements with proper thead/tbody/th markup — not as text blocks or images.
Language metadata: Language is detected and written to the EPUB package metadata automatically.
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

Criterion	PDF/UA	EPUB3
WCAG 1.4.10 Reflow	Fails for complex layouts	Passes by design
WCAG 1.3.2 Reading order	Requires manual tagging	Enforced by HTML source order
WCAG 1.3.1 Structure	Requires PDF/UA tagging	Native HTML semantics
Screen reader support	Inconsistent across readers	Consistent on NVDA/JAWS/VoiceOver
Automated validation	PAC 2024, axesPDF	ACE by DAISY (free, open source)
Authoring cost	High (specialist tooling required)	Low (convert from existing PDF)
Retrofitting large libraries	Expensive and slow	Batch API available

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:

Audit your library: Identify the 20% of documents that receive 80% of traffic. These are your conversion priority.
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.
Validate: Run each converted EPUB through ACE by DAISY (free, open source). Address any flagged issues — typically missing alt text on charts and images.
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.
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.

Convert a PDF to Section 508-compliant EPUB3 — free, no account, no install.

Convert a PDF → Accessibility teams →