An eBook can look perfect on a laptop and still be frustrating or unusable for someone reading it with a screen reader.
The chapter headings may only look like headings because they were made larger and bold. A photograph may have no alternative text. A table may be exported as an image. Navigation may force a reader to move through dozens of pages just to reach Chapter Five.
None of these problems is obvious from appearance alone.
Professional accessible ebook formatting is about structure as much as presentation. The file needs to communicate what each element is, how content is organized, which order it should be read in, and what information visual elements contribute.
The current stable W3C framework includes EPUB 3.3 and EPUB Accessibility 1.1. EPUB Accessibility 1.1 is a W3C Recommendation and defines requirements for accessibility conformance and discoverability. W3C is also actively developing EPUB Accessibility 1.2, but as of July 2026 it remains a Working Draft, not the stable Recommendation.
Good accessibility begins before anyone opens a screen reader.
It begins in the code.
Use Reflowable EPUB Whenever the Book Allows It
A reflowable EPUB allows text to respond to the reader’s:
- Screen size
- Font preferences
- Text size
- Orientation
- Reading application
This flexibility is important for readers with low vision, dyslexia, motor impairments, and other accessibility needs.
Fixed-layout eBooks can be appropriate when exact spatial arrangement is essential, such as certain children’s books, graphic works, or visual poetry. They also require more accessibility planning because positioning, reading order, and resizing can become more complicated.
For most novels, memoirs, business books, guides, and conventional nonfiction, reflowable EPUB is usually the stronger accessibility foundation.
A book should not be locked into a visual page simply because the print edition was designed that way.
Semantic Headings Give the Book a Structure
A sighted reader recognizes a chapter title because it is large, bold, and centered.
A screen reader cannot reliably infer meaning from appearance.
Use real heading elements.
Weak Markup
<p class=”big-bold”>Chapter 4</p>
<p class=”big-bold”>The Decision</p>
The text may look like a heading, but structurally it is still just two paragraphs.
Better Markup
<h1>Chapter 4: The Decision</h1>
Subsections can use an appropriate hierarchy:
<h1>Chapter 4: The Decision</h1>
<h2>What Changed</h2>
<h3>The First Warning Sign</h3>
Amazon’s current Kindle accessibility guidance specifically recommends hierarchical headings to organize chapters, sections, and subsections.
Do not choose heading levels according to how large you want the text to appear.
Use CSS for appearance.
Use HTML headings for meaning.
Keep Heading Levels Logical
Avoid a structure such as:
H1
H4
H2
H5
without a genuine structural reason.
A more logical hierarchy allows assistive technology users to understand the book’s organization quickly.
For example:
H1: Chapter title
H2: Main section
H3: Subsection
W3C’s current EPUB accessibility techniques emphasize publication titles, document titles, heading hierarchy, and headings that accurately describe their topic or purpose.
Screen-reader users often navigate by headings.
Well-structured headings can therefore function like signposts through the book.
Reading Order Must Match Meaning
Visual positioning does not guarantee reading order.
Consider a designed page containing:
- Pull quote
- Heading
- Main paragraph
- Caption
- Image
A sighted reader may understand the intended sequence from the page design.
Assistive technology normally follows the underlying document order.
If the code lists the caption first, the pull quote second, and the heading last, the reading experience may become confusing.
Amazon advises publishers to create meaningful sequential content and pay particular attention to reading order in fixed-format books.
Inspect the source order.
Do not judge accessibility only from what appears visually on screen.
Give Meaningful Images Useful Alt Text
Alternative text communicates essential visual information to readers who cannot see an image.
Suppose a business eBook contains a chart.
Weak Alt Text
<img src=”chart.jpg” alt=”chart”>
The reader learns almost nothing.
Better Alt Text
<img
src=”chart.jpg”
alt=”Bar chart showing customer retention rising from 62 percent in 2023 to 74 percent in 2025.”>
The description communicates the important information.
Amazon currently recommends alt text or equivalent surrounding description for meaningful images.
Good alt text depends on context.
A photograph of a lighthouse in a novel may require only a concise description.
A medical diagram may require substantially more explanation.
Ask:
What information would the reader lose if this image disappeared?
Describe that information.
Decorative Images Should Not Create Noise
Not every flourish needs to be announced.
A decorative divider between scenes does not need:
Decorative swirling floral divider with three leaves.
Screen readers repeating this information 40 times would make the book harder to read.
Decorative images can use an empty alt attribute where appropriate:
<img src=”divider.png” alt=””>
Meaningful imagery receives description.
Pure decoration stays out of the reader’s way.
Avoid Images of Text
Do not turn ordinary paragraphs, quotations, chapter titles, or tables into images simply to preserve typography.
WCAG 2.2 recommends using real text instead of images of text when the desired visual presentation can be achieved using available technology.
Live text can usually be:
- Resized
- Searched
- Selected
- Read aloud
- Adjusted by the reader
Image-based text loses many of those benefits.
This concern becomes especially important in poetry ebook formatting, where authors may be tempted to convert every poem into an image to preserve line arrangement.
Use image-based text only when the visual treatment itself is essential and provide an appropriate accessible alternative.
Descriptive Links Are Better Than “Click Here”
A screen reader user may navigate through links without hearing all surrounding paragraphs.
Compare:
To download the worksheet, click here.
with:
Download the weekly planning worksheet.
The second tells the reader where the link leads.
Amazon’s current accessibility guidance recommends self-describing link titles and discourages repetitive links with unclear purpose.
Avoid lists such as:
- Click here
- Click here
- Click here
when each link goes somewhere different.
Tables Need Real Table Structure
A sighted reader can visually associate a value with a row and column heading.
A screen reader needs structured relationships.
Do not paste a screenshot of a spreadsheet into the eBook.
Use real table markup when tabular information is necessary.
For example:
<table>
<caption>Quarterly Revenue</caption>
<thead>
<tr>
<th scope=”col”>Quarter</th>
<th scope=”col”>Revenue</th>
</tr>
</thead>
<tbody>
<tr>
<th scope=”row”>Q1</th>
<td>$420,000</td>
</tr>
</tbody>
</table>
Amazon recommends captions plus clearly identified row and column headings and advises against using images of tables.
Very complicated print tables may need redesigning for a small screen.
Accessibility and mobile readability often improve together.
Navigation Should Let Readers Move Through the Book
A long eBook should not force readers to move linearly from the title page to the final chapter.
EPUB navigation can provide:
- Table of contents
- Major section navigation
- Page list where appropriate
- Landmarks
EPUB 3.3 explicitly defines navigation structures including table-of-contents, page-list, and landmarks navigation elements.
Landmarks help identify important regions such as the beginning of the main content.
W3C’s current EPUB accessibility techniques also specifically recommend including EPUB landmarks.
Think of navigation as part of usability, not merely an automated contents page.
Mark the Language Correctly
Language information influences:
- Screen-reader pronunciation
- Text-to-speech behavior
- Braille
- Voice selection
The eBook’s primary language should be correctly identified in its metadata and content.
Amazon currently recommends that the language selected during KDP setup, the language in the book, and the language declared in the file metadata agree. It also advises marking language changes within multilingual content.
Suppose an English-language novel includes:
Buenas noches, señora.
Markup can identify the Spanish phrase:
He smiled. Buenas noches, señora.
A capable reading system can then pronounce the phrase more appropriately.
Language tagging is invisible to most sighted readers.
Its effect can be significant for assistive technology.
Color Cannot Carry Meaning Alone
Suppose an educational eBook says:
Items shown in red are incorrect.
A reader who cannot perceive the color difference may lose the distinction.
Add another cue:
Incorrect answers are marked “Incorrect” and shown in red.
Contrast also matters.
WCAG 2.2 specifies a minimum contrast ratio of 4.5:1 for ordinary text and 3:1 for qualifying large text at Level AA.
Amazon currently reflects the 4.5:1 recommendation in its eBook accessibility guidance and warns against thin, light-colored type.
A pale gray paragraph on a white background may fit a designer’s aesthetic.
It may not fit the reader’s needs.
Footnotes Need Navigable Relationships
Footnotes can become frustrating when readers are sent to the end of the book without a reliable way back.
A good EPUB workflow should provide:
- Clear footnote reference
- Destination note
- Logical relationship between them
- Return navigation where supported and appropriate
Avoid typing a superscript number that merely looks like a footnote marker without creating an actual link.
Footnote usability should be tested with both keyboard-style navigation and a screen reader.
Test the EPUB Automatically
Accessibility checking should not depend entirely on visual inspection.
DAISY’s Ace tool is designed specifically to test EPUB files for accessibility issues and generates reports identifying potential violations, metadata problems, document-outline issues, and image concerns. DAISY released Ace by DAISY 1.4.5 in April 2026 as a maintenance update aligned with current accessibility testing protocols.
Use EPUBCheck separately.
EPUBCheck tests EPUB technical conformance, while Ace focuses on accessibility issues. DAISY specifically notes that passing Ace does not prove complete WCAG conformance and that EPUBCheck is still required for EPUB validation.
A useful sequence is:
- EPUBCheck
- Ace by DAISY
- Manual accessibility review
- Screen-reader testing
Automated testing can find many problems.
It cannot judge everything.
Test With an Actual Screen Reader
Open the eBook using assistive technology.
Test:
- Book title
- Table of contents
- Heading navigation
- Chapter order
- Image descriptions
- Links
- Lists
- Tables
- Footnotes
- Language changes
- Reading order
Listen without watching the screen for part of the test.
Ask:
Could I understand this book if audio were my primary interface?
DAISY’s validation guidance explicitly combines automated tools with manual evaluation because automated accessibility checks cannot verify all requirements.
An EPUB with zero automated errors can still contain terrible alt text.
Human review matters.
Accessibility Should Enter the Workflow Early
Do not wait until the book is completely designed.
Accessibility decisions often begin during editorial development.
Developmental editing for ebooks may identify tables, complex structures, exercises, illustrations, or sidebars that need a more usable digital presentation.
Beta readers for ebooks can identify navigational or comprehension problems, although specialist accessibility testing remains separate.
A fiction character bible and romance tropes for writers belong to storytelling development, while nonfiction ebook fact checking verifies claims. Those processes should be completed without creating structures that later become unnecessarily difficult to convert.
Production should preserve the editorial work.
It should also make the content available to more readers.
Accessibility Must Continue Into Marketing Assets
Accessibility does not stop when the EPUB is finished.
Ebook description writing should produce readable retailer copy without excessive decorative symbols or unnecessary complexity.
KDP keyword research supports discoverability but should not lead to keyword-stuffed descriptions that become difficult to understand.
An ebook lead magnet should follow the same accessibility principles as the full book if it is delivered as EPUB, PDF, or another digital resource.
Readers should not receive an accessible commercial eBook and an inaccessible companion workbook.
Accessibility should be part of the publishing system.
Accessible eBook Checklist
Document Structure
- Reflowable EPUB used where appropriate
- Real HTML headings used
- Heading hierarchy is logical
- Reading order matches intended meaning
- Lists use proper list markup
Images
- Meaningful images have useful alt text
- Decorative images are ignored appropriately
- Important information is not trapped in images
- Images of text are avoided
Navigation
- Clickable table of contents works
- Landmarks are included where appropriate
- Links have descriptive wording
- Footnote navigation is usable
Tables
- Tables use real HTML structure
- Row and column headings are identified
- Captions are included where useful
- Screenshots of tables are avoided
Language and Visual Design
- Primary language is declared
- Language changes are marked
- Color is not the only information cue
- Text contrast is sufficient
- Text can resize without losing information
Testing
- EPUB passes EPUBCheck
- Ace by DAISY report reviewed
- Manual accessibility review completed
- Screen-reader navigation tested
- Font resizing tested
- Multiple device sizes checked
- Problems corrected and retested
Current W3C work continues to evolve. EPUB Accessibility 1.1 remains the stable Recommendation, while EPUB Accessibility 1.2 is under active development and its associated Techniques 1.2 were updated again in July 2026. Publishers should therefore verify the current W3C, DAISY, and retailer documentation when establishing a formal accessibility-conformance workflow.
An accessible eBook does not need to look visually different from a professionally designed one.
The difference is that its structure continues working when the reader experiences the book differently.
Frequently Asked Questions
Accessible eBook formatting creates digital book files that can be navigated, resized, interpreted, and understood by readers using screen readers, braille displays, text-to-speech, and other assistive technologies.
A well-structured reflowable EPUB is often better suited to adaptable reading because text and navigation can respond to reader settings and different screen sizes. Accessibility still depends on how the file is created.
No. Alt text is only one part of accessibility. Headings, reading order, navigation, tables, language metadata, links, contrast, and structural markup also need attention.
EPUB Accessibility 1.1 remains the current stable W3C Recommendation, used alongside EPUB 3.3 and applicable WCAG requirements. EPUB Accessibility 1.2 is being developed but remains a Working Draft as of July 2026.
EPUBCheck can validate technical EPUB conformance, while Ace by DAISY can identify many accessibility issues. Automated tools should be supplemented with manual review and assistive-technology testing.
Yes. Screen-reader testing can reveal problems with heading navigation, reading order, alt text, links, tables, footnotes, and language changes that may not be obvious through visual inspection or automated validation alone.
