An eBook can look flawless on a tablet and still be nearly impossible to read with assistive technology.
The chapters appear in the right order visually, but a screen reader announces the sidebar before the paragraph that introduces it. An illustration contains important information but has no description. Every link is labeled “click here.” A table becomes a confusing stream of disconnected numbers.
These are not cosmetic problems.
Professional accessible ebook formatting determines whether readers can navigate, understand, enlarge, listen to, or otherwise adapt the book according to their needs.
The current W3C EPUB framework uses EPUB 3.3, whose Recommendation was updated in January 2026. EPUB Accessibility 1.1 remains the W3C Recommendation that defines accessibility and discoverability requirements for EPUB publications.
Accessibility therefore needs to be built into the structure of the file, not added as a final visual adjustment.
Reflowable EPUB Gives Readers More Control
For most text-heavy books, reflowable EPUB is the strongest starting point.
Unlike a print PDF, a reflowable eBook does not force every reader to view the same fixed page. Text can adapt to the size of the screen and, depending on the reading system, readers may be able to change:
- Font size
- Typeface
- Line spacing
- Margins
- Background color
- Text color
- Screen orientation
This flexibility is especially useful for readers with low vision, dyslexia, or other conditions that make a fixed presentation difficult.
Reflowable EPUB works particularly well for:
- Novels
- Memoirs
- Business books
- Self-help
- Biography
- History
- Narrative nonfiction
- Most practical guides
W3C defines EPUB as a format for structured and semantically enhanced web content, which allows the text and its meaning to remain separate from a single fixed visual presentation.
The digital edition should therefore be created from structured content, not from screenshots of the printed pages.
Image-Only Books Block Essential Reading Features
One of the poorest eBook conversion methods is turning each printed page into an image.
The result may look identical to the paperback, but the words are no longer ordinary electronic text.
Readers can lose the ability to:
- Resize text effectively
- Search for words
- Select text
- Navigate by headings
- Use dictionary tools
- Copy permitted passages
- Listen with text-to-speech
- Apply personal font settings
WCAG guidance recommends using actual text instead of images of text whenever the intended visual presentation can be achieved through normal text technologies.
Images containing essential text occasionally cannot be avoided, especially in diagrams or historical documents. In those situations, provide the information through an appropriate text alternative or surrounding description.
Fixed Layout Should Be Used Only When the Design Requires It
Fixed-layout EPUB preserves the position of content on a page.
It can be appropriate for:
- Picture books
- Comics
- Art books
- Highly visual cookbooks
- Educational books with complex diagrams
- Publications where text and imagery must maintain a precise relationship
The format creates additional accessibility challenges.
W3C’s current fixed-layout accessibility guidance notes that fixed-layout publications can be partially or completely inaccessible to people with disabilities, particularly readers who need text enlargement or customized visual presentation. Accessible fixed-layout EPUBs still require appropriate reading order, navigation, text alternatives, contrast, and accessibility metadata.
Do not choose fixed layout simply because it preserves the appearance of the paperback.
If the book can work as reflowable content, preserving reader flexibility is generally more useful.
Semantic Headings Tell Technology What the Page Means
A chapter title can look like a heading without actually being coded as one.
Imagine this markup:
CHAPTER FOUR
18-point bold text
A sighted reader recognizes the chapter instantly.
A screen reader only recognizes it as a heading if the underlying markup identifies it structurally.
Use a logical hierarchy such as:
- H1 for the primary content title where appropriate
- H2 for major sections
- H3 for subsections
- Lower levels only when the structure genuinely requires them
Do not choose heading levels according to how large you want the words to appear. Visual styling belongs in CSS. Heading markup describes structure.
WCAG 2.2 requires headings and labels to describe their topic or purpose. Correct structural markup also allows screen-reader users to navigate through a generated list of headings instead of moving through every paragraph sequentially.
The final book editing style sheet can record heading levels so editors, formatters, and accessibility specialists use the same hierarchy.
Reading Order Must Match Meaning
Visual placement does not guarantee logical reading order.
Consider a page containing:
- Introductory paragraph
- Photograph
- Caption
- Sidebar
- Main text continuation
If the underlying file is coded incorrectly, assistive technology might announce:
- Sidebar
- Caption
- Final paragraph
- Introductory paragraph
- Photograph
The reader receives all the content but in an order that no longer makes sense.
WCAG requires a programmatically determinable sequence whenever the order affects meaning. This is particularly important for EPUBs containing sidebars, notes, figures, tables, multi-column material, and complex layouts.
Test the logical order of:
- Front matter
- Chapters
- Section headings
- Images
- Captions
- Footnotes
- Endnotes
- Sidebars
- Tables
- Bibliography
- Index
Reading order deserves additional attention when converting a print-first design.
Alt Text Should Communicate the Purpose of an Image
Alternative text is not a caption copied into hidden code.
It should give a reader access to the information or function the image provides.
For example:
Weak alt text:
“Image of woman.”
Better alt text:
“Historian Maria Torres examining handwritten letters at an archive table.”
For a chart:
Useful short alternative:
“Line chart showing audiobook sales increasing from 2022 through 2025.”
A complex chart may need a longer description explaining the important data and relationships.
W3C distinguishes between informative, decorative, functional, and complex images. Informative images need alternatives that convey their essential information, while purely decorative images should normally use a null alternative so screen readers can skip them.
Complex diagrams, maps, and charts may require both a short identification and a longer textual explanation.
Alt text should not become:
- Keyword stuffing
- Marketing copy
- A duplicate of nearby text
- “Image”
- “Graphic”
- The file name
Describe what matters in the context of the book.
Links Should Explain Where They Go
Imagine listening to a screen reader announce:
“Click here.”
“Click here.”
“Read more.”
“Website.”
A reader navigating through links separately has little idea which one to select.
Use descriptive wording such as:
- Download the discussion guide
- View the author’s research sources
- Read the accessibility statement
- Visit the publisher’s book page
WCAG states that readers should be able to determine a link’s purpose from the link text or its programmatically associated context. Descriptive links are especially useful because assistive technologies can present all links as a separate list.
Avoid raw URLs as visible text when a meaningful link label can be provided.
Tables Need Real Row and Column Relationships
Tables should represent data, not be used simply to force content into a visual arrangement.
An accessible table generally needs:
- Clear table title or caption
- Header cells
- Correct association between headers and data
- Logical row and column structure
- Simple organization where possible
Avoid:
- Screenshots of tables
- Empty cells used for spacing
- Excessive merged cells
- Information communicated only through background colors
- Extremely wide tables that become unusable when text enlarges
A complicated table may work better when divided into smaller tables or accompanied by a prose explanation.
Accessibility is sometimes improved by changing the presentation instead of reproducing the print layout exactly.
Language Tagging Helps Screen Readers Pronounce Text Correctly
The eBook should identify its primary language programmatically.
An English-language book, for example, should declare English in the publication and content markup.
Language changes within the book may also need identification when pronunciation depends on them.
Examples include:
- French dialogue
- Spanish quotations
- Arabic phrases
- Latin terminology
- German titles
WCAG explains that identifying the language helps screen readers load the appropriate pronunciation rules and allows other technologies to render linguistic content more accurately.
This does not mean every borrowed word requires elaborate tagging. Focus on passages where a language change affects pronunciation or interpretation.
Navigation Should Work Without Continuous Swiping
Readers should be able to move directly to important parts of the publication.
Provide a properly structured EPUB navigation document containing a linked table of contents.
Depending on the book, navigation may also include:
- Parts
- Chapters
- Major subsections
- Notes
- Bibliography
- List of illustrations
- Page list
- Index
EPUB Accessibility Techniques 1.1 includes guidance for page navigation, reading order, descriptions, language, and distribution metadata as part of accessible EPUB production.
Authors researching how to index a book should also plan for the digital edition. A print index based entirely on page numbers may need linked entries or other digital navigation so readers can move directly to relevant content.
Color Contrast Still Matters in an Adaptable File
Readers may customize colors, but the publisher’s default design should still be readable.
WCAG 2.2 Level AA requires a minimum contrast ratio of 4.5:1 for ordinary text and 3:1 for qualifying large text.
Also avoid relying on color alone.
For example, a chart should not communicate:
- Profit only in green
- Loss only in red
Add:
- Labels
- Symbols
- Patterns
- Text descriptions
Test captions, headings, links, diagrams, and text placed over images as carefully as standard paragraphs.
Accessibility Metadata Helps Readers Choose the Right Book
An accessible file is more useful when readers can discover its accessibility features before purchasing or borrowing it.
EPUB Accessibility 1.1 requires accessibility metadata as part of discoverability. It allows publishers and distributors to communicate features and potential limitations to users.
Metadata can describe features such as:
- Alternative text
- Structural navigation
- Reading order
- Accessible math
- Sufficient contrast
- Accessibility hazards
The same information should remain accurate across:
- Retail listings
- Library distribution
- Amazon A+ Content for books
- author media kit
- book sell sheet
Do not claim that an eBook is “fully accessible” simply because one automated checker returned no errors.
Automated Testing Is Only the First Layer
Current EPUB quality control should use more than one test.
EPUBCheck Confirms Technical EPUB Conformance
EPUBCheck checks whether an EPUB conforms to the technical specification and identifies structural or packaging errors.
The current production-ready EPUBCheck release is version 5.3.0, released in September 2025, with complete EPUB 3.3 support.
Ace by DAISY Finds Automated Accessibility Problems
Ace by DAISY is a free accessibility checker specifically designed for EPUB publications.
It reports issues involving:
- Accessibility violations
- Metadata
- Heading outlines
- Images and alternative text
DAISY released Ace version 1.4.5 in April 2026.
Passing Ace does not prove complete accessibility because some accessibility decisions cannot be tested automatically.
Manual Testing Finds What Software Cannot Judge
Manual review is still necessary.
DAISY’s recommended validation process combines EPUBCheck, Ace, and manual evaluation because automated tools cannot judge issues such as whether an image description is genuinely useful.
Test representative chapters with screen-reading technology such as:
- NVDA
- VoiceOver
- TalkBack
Listen instead of only watching the screen.
Ask:
- Are headings announced correctly?
- Does the reading order make sense?
- Do image descriptions add meaningful information?
- Are tables understandable?
- Can users navigate the contents?
- Do links make sense out of context?
Testing with disabled readers is especially valuable when possible.
Accessibility Planning Should Begin Before Conversion
Several earlier publishing decisions affect the final eBook.
A nonfiction book proposal may identify complex tables, illustrations, or visual teaching material that will eventually need accessible treatment.
A literary agent submission package does not normally need technical accessibility specifications, but accessibility should enter the production discussion once the project progresses toward publication.
Complete book copyright permissions work before embedding third-party photographs, artwork, charts, and other protected content in the digital edition.
The workflow for fact checking a nonfiction book should also verify the words contained in charts, captions, tables, and linked resources.
Large print book publishing can provide an additional accessible print option, but large print and accessible EPUB solve different needs. One does not replace the other.
Marketing should accurately describe the available format instead of treating accessibility as a vague promotional claim.
Pre-Publication Accessibility Checklist
Before releasing the eBook, confirm that:
- Reflowable EPUB is used unless fixed layout is genuinely necessary.
- Important text has not been converted into images.
- Headings use semantic markup.
- Heading levels follow a logical hierarchy.
- Reading order matches the intended meaning.
- Informative images have useful alt text.
- Decorative images are marked appropriately.
- Complex graphics have sufficient descriptions.
- Links communicate their purpose.
- Tables contain proper headers and relationships.
- The publication language is identified.
- Meaningful language changes are tagged.
- Navigation reaches all major sections.
- Color is not the only way information is communicated.
- Default text contrast meets applicable requirements.
- Accessibility metadata is accurate.
- The EPUB passes current EPUBCheck validation.
- Ace accessibility issues have been reviewed.
- Manual screen-reader testing has been completed.
- The final distributed file is the tested version.
A screen reader does not need an eBook to look different. It needs the file to contain enough structure and meaning for the same book to work differently.
Frequently Asked Questions
Is Every EPUB Automatically Accessible?
No. EPUB supports accessible publishing, but a file may still have incorrect reading order, missing alt text, poor navigation, unstructured headings, or other barriers.
Is Reflowable EPUB Better Than Fixed Layout for Accessibility?
For most text-heavy books, reflowable EPUB provides greater flexibility because readers can often resize and customize the text. Fixed layout may still be necessary for publications whose visual arrangement is essential.
Does Every Image Need Alt Text?
Meaningful images need an appropriate text alternative. Purely decorative images should usually be marked so assistive technologies can ignore them.
Is Passing EPUBCheck Enough to Prove Accessibility?
No. EPUBCheck validates technical EPUB conformance. Accessibility also requires automated testing with tools such as Ace and manual evaluation of issues software cannot judge reliably.
Can an Accessible eBook Still Have Images and Complex Design?
Yes. Accessibility does not require removing visual content. Images, diagrams, tables, and design elements need to be structured and described so their important information remains available to readers using assistive technology.
Should Accessibility Be Added After the eBook Is Finished?
Accessibility is easier and more reliable when planned during editing and formatting. Fixing poor structure after conversion can require rebuilding headings, tables, navigation, image descriptions, and reading order.
