EPUB Page Navigation: Why Page Lists and Page Breaks Matter for Accessibility

EPUB Page Navigation: Why Page Lists and Page Breaks Matter for Accessibility

A print reader can hear:

“Turn to page 127.”

and immediately find the location.

For someone reading a reflowable EPUB, the experience can be different.

Change the screen size, font size, line spacing, margins or reading application, and the amount of content displayed on each screen can change. A passage shown on one screen for one reader may appear several screens later for another.

This creates an important accessibility and usability question:

How can an EPUB reader find the same location as someone using the print edition?

One answer is EPUB page navigation.

Page navigation can preserve stable locations from a statically paginated publication and give readers—including people using assistive technology—a way to navigate to those locations in a reflowable EPUB.

This is especially valuable for academic books, textbooks, educational materials, reference works and publications where print and digital editions are used together.

Quick Answer: What Is EPUB Page Navigation?

EPUB page navigation is a mechanism for representing stable page locations and allowing readers to navigate to them inside an EPUB.

A typical implementation combines three elements:

• Page-break markers identify where static page boundaries occur within the EPUB content.
• A page list provides navigation links to those page locations.
• Pagination-source information identifies the statically paginated publication from which those locations were derived when applicable.

The basic relationship is:

Static source page → Page-break marker → Page list → Reader navigation

This allows a reader to navigate to a reference such as page 127 even though the EPUB itself dynamically reflows.

W3C's EPUB Accessibility specifications and techniques address page navigation as an important mechanism for maintaining useful static references in reflowable publications.

Why Are EPUB Page Numbers Different From Print Page Numbers?

Printed books have fixed pagination.

Once a particular print edition is produced, its page boundaries remain fixed.

Page 127 remains page 127.

Reflowable EPUBs behave differently.

Imagine two readers opening the same EPUB.

Reader A

Reader A uses a tablet with standard text size and spacing.

Reader B

Reader B uses a smartphone with enlarged text, wider line spacing and accessibility settings.

The same paragraph may appear on different displayed screens for each reader.

This means device-generated or screen-based page numbers are not necessarily stable references to the publication.

W3C's accessibility guidance discusses this difference between dynamic pagination and static page references, particularly where readers need to coordinate locations across formats.

Why Is EPUB Page Navigation Important for Accessibility?

Consider a university class.

The lecturer says:

“Please read the second paragraph on page 84.”

A student using the printed textbook can turn directly to page 84.

A blind student reading an accessible EPUB with a screen reader should also have an efficient way to reach the corresponding location.

Without usable page navigation, the student might have to search for nearby text, navigate through headings or move paragraph by paragraph until the passage is found.

Page navigation can provide a more direct route.

This is particularly useful for:

• Academic publishing where page references appear in research and citations.
• Educational publishing where teachers frequently assign specific pages.
• Textbooks used simultaneously in print and digital formats.
• Reference publications where readers need predictable locations.
• Scholarly works containing citations, quotations and cross-references.
• Backlist conversion where established print pagination needs to remain useful digitally.

Page navigation is therefore not merely about reproducing print conventions.

It can help provide equivalent location information across different ways of reading the same publication.

The Three Main Parts of EPUB Page Navigation

Publishers and EPUB production teams should understand three related concepts.

These components are related, but they perform different functions.

1. What Is an EPUB Page-Break Marker?

A page-break marker identifies where a page boundary from a statically paginated source occurs inside EPUB content.

Suppose a printed book changes from page 126 to page 127 in the middle of a paragraph.

The reflowable EPUB does not need to visually reproduce that print page.

Instead, the location of the original boundary can be represented semantically within the EPUB.

This allows the digital publication to retain information equivalent to:

“Page 127 begins here.”

W3C EPUB accessibility techniques explain how page-break semantics can provide page-location information for readers and assistive technologies.

2. What Is an EPUB Page List?

Knowing when a new source page begins is useful.

However, readers may also need to navigate directly to a particular page.

That's where the page list becomes important.

A page list is a specialized EPUB navigation structure containing links to static page locations.

Conceptually, it could contain:

Page 1 → Page 2 → Page 3 → … → Page 126 → Page 127

Each entry links to the corresponding page location inside the publication.

In EPUB, the page list is represented in the navigation document and provides navigation to static page boundaries.

Page List vs Page-Break Marker

The two features work together but should not be confused.

An easy way to remember the difference is:

The page-break marker identifies where the page is. The page list helps the reader get there.

3. What Is a Pagination Source?

Page numbers become more useful when readers know which edition they correspond to.

Imagine one book is available as:

• hardcover;
• paperback;
• EPUB.

The hardcover might place a paragraph on page 102.

The paperback might place the same paragraph on page 109.

If the EPUB simply identifies:

Page 102

a reader may need to know which static edition supplied that page reference.

This is where the pagination source becomes important.

When static page locations correspond to another statically paginated publication, EPUB accessibility requirements address identifying the source of those page locations.

This makes the references more meaningful and reduces ambiguity across editions.

A Simple EPUB Page-Navigation Example

Imagine an academic textbook.

The print edition contains:

Page 45 — Photosynthesis

During EPUB production, the corresponding page boundary is preserved.

The EPUB contains a page-break marker for:

45

The page list then contains an entry:

45

that links to the corresponding marker.

The relationship becomes:

Print Page 45 → EPUB Page-Break Marker → Page-List Entry 45 → Reader Selects Page 45 → Correct Content Location

The EPUB remains reflowable.

The reader can still enlarge text or change the display.

But the reference location remains available.

EPUB Page Navigation vs Table of Contents

A page list is not the same as the EPUB table of contents.

Both provide navigation, but they solve different problems.

A reader might use the table of contents to navigate to:

Chapter 7 — Digital Publishing

and then use page navigation to reach:

Page 183

within that section.

Both navigation mechanisms can therefore contribute to a more usable digital publication.

Why Page Navigation Matters in Academic Publishing

Academic books frequently rely on stable references.

Students, lecturers and researchers may refer to:

• page numbers;
• quotations;
• citations;
• exercises;
• figures;
• footnotes;
• tables;
• discussion questions;
• reading assignments.

Consider a research paper that says:

“See the discussion on page 217.”

A reader using the corresponding EPUB should have an efficient method of finding that location.

Without stable references, users of different reading environments may have difficulty locating the same passage.

For academic publishers, page navigation therefore supports both accessibility and scholarly usability.

Why Page Navigation Matters in Education

Consider a teacher telling a class:

“Read pages 61–64 before tomorrow.”

Students may be using:

• printed textbooks;
• tablets;
• smartphones;
• enlarged text;
• screen readers;
• other assistive technologies.

If the EPUB preserves useful static page references, readers can reach corresponding content even though the digital presentation itself reflows.

W3C accessibility guidance specifically discusses educational and mixed-format reading situations as important contexts for page navigation.

Does Every EPUB Need Print Page Numbers?

Not necessarily.

The decision depends on the publication and how it will be used.

When a Corresponding Print Edition Exists

Preserving useful page locations should be evaluated as part of EPUB production.

When Print and EPUB Are Used Together

Page navigation can become especially valuable because users need to coordinate locations across formats.

For Academic and Educational Publications

Stable references can provide significant practical benefits for teaching, citation and collaborative reading.

For Digital-Only Publications

Publishers should evaluate whether static page locations provide a meaningful navigation benefit rather than automatically creating print-style pagination.

The objective is not to force print behaviour into every digital publication.

The objective is to provide useful navigation when static references have real value.

EPUB Accessibility 1.2 and Page Navigation

This topic is particularly relevant in 2026.

W3C published EPUB Accessibility 1.2 in August 2026.

The specification addresses circumstances where page navigation should be included, such as when a reflowable EPUB corresponds to a statically paginated publication or where static and reflowable versions are expected to be used together.

For publishers producing print and EPUB simultaneously, this creates an important production consideration:

Page navigation should be planned upstream rather than treated only as a final accessibility fix.

If page locations can be preserved during content production, the resulting EPUB workflow can be much more controlled.

Common EPUB Page-Navigation Problems

Page List Exists, but Links Point to the Wrong Locations

Technical presence alone is not enough.

A link labelled 127 should lead to the correct source-page boundary.

This requires source comparison as well as technical validation.

Page Markers Exist, but There Is No Usable Page List

Readers may receive information when crossing page boundaries but still lack an efficient way to navigate directly to a requested page.

Page Numbers Do Not Match the Source Edition

This can cause problems in:

• classrooms;
• academic citations;
• print/EPUB coordination;
• reference workflows.

Pagination Source Is Unclear

If several static editions exist, readers may not know which edition the EPUB's page references correspond to.

Roman Numerals Are Mishandled

Many books use:

i, ii, iii, iv...

for front matter, followed by:

1, 2, 3, 4...

for the main body.

These sequences need careful handling.

Page Locations Are Reconstructed Too Late

Trying to recover page boundaries after source information has already been discarded can create unnecessary manual work and increase the risk of errors.

EPUB Page Navigation QA Checklist

Before delivery, publishers and production teams should verify the following.

• Correct pagination source — Identify the static edition associated with the page references.
• Page locations preserved — Confirm relevant source-page boundaries have been retained.
• Page-break markers encoded — Ensure required static page boundaries are represented correctly.
• Page labels verified — Check that labels match the corresponding source pages.
• Roman numerals reviewed — Verify front-matter numbering such as i, ii, iii and iv.
• Page list created — Provide navigation to the relevant page locations.
• Page-list links verified — Confirm each entry reaches the correct destination.
• Page sequence reviewed — Check that page references appear in the expected order.
• Chapter transitions tested — Pay particular attention to page locations around chapter boundaries.
• Mid-paragraph page breaks reviewed — Verify boundaries that occur within paragraphs.
• Duplicate identifiers checked — Detect duplicate IDs or page references.
• Technical validation completed — Run appropriate EPUB validation.
• Source comparison performed — Compare representative EPUB page locations with the source edition.
• Reading-system testing performed — Test navigation in representative EPUB reading environments.
• Assistive-technology QA completed — Verify that page navigation is usable with applicable assistive technologies.
• Corrections retested — Recheck modified markers and links before final delivery.

Automated Validation vs Human QA

Automated tools are important, but they cannot answer every page-navigation question.

For example, a link labelled:

Page 127

can be technically valid while pointing to content that actually belongs to page 126.

The markup passes.

The publication experience is still wrong.

That is why:

Technical validity does not automatically mean navigational accuracy.

A Better EPUB Page-Navigation Workflow

Step 1 — Identify the Source Edition

Determine which statically paginated edition provides the page references.

Step 2 — Preserve Page Locations

Retain source-page boundaries during conversion whenever possible.

Step 3 — Encode Page-Break Markers

Represent the required static boundaries appropriately inside the EPUB.

Step 4 — Build the Page List

Create direct navigation links to those locations.

Step 5 — Add Pagination-Source Information

Identify the source of the static pagination where applicable.

Step 6 — Validate the EPUB

Run appropriate technical EPUB validation.

Step 7 — Compare Against the Source

Check representative locations throughout the publication.

For example:

Page 12 → Page 48 → Page 103 → Page 217 → Page 304

Sampling across the book can reveal offset, sequencing or mapping problems that might otherwise be missed.

Step 8 — Perform Accessibility QA

Evaluate whether the page-navigation experience works effectively for applicable assistive-technology users.

Step 9 — Correct and Retest

After defects are corrected, verify the affected page locations again.

A scalable workflow can therefore be summarized as:

Preserve → Encode → Link → Validate → Human QA → Correct → Retest

Why Page Navigation Should Begin Upstream

One of the most useful production lessons is simple:

Preserving page locations during conversion is usually easier than reconstructing them later.

Consider a structured publishing workflow:

XML → Print + EPUB

When relevant page-location information is retained during production, relationships between outputs can be managed systematically.

Now consider a backlist workflow:

Printed book → Scan → OCR → Structured content → EPUB

Page locations may need to be reconstructed and carefully checked against the original pages.

The later page-navigation requirements are introduced, the more difficult this process can become.

For that reason, publishers should consider page navigation part of the production specification, rather than treating it solely as a final accessibility QA task.

Page Navigation and Backlist Conversion

Backlist conversion presents a particularly interesting challenge.

Older publications may exist only as:

• print copies;
• scanned images;
• PDFs;
• OCR text;
• legacy digital files.

A successful workflow may need to preserve relationships between:

Original pages → OCR text → structured content → EPUB locations

If the final EPUB needs to retain print references, page-boundary information should be captured as early as practical.

This becomes especially important when digitizing large academic or educational catalogues.

Page Navigation and Accessible EPUB Production

Page navigation is only one part of accessible EPUB production.

A broader accessibility workflow can also involve:

• semantic heading structure;
• logical reading order;
• meaningful image alternatives;
• accessible tables;
• appropriate language identification;
• usable navigation;
• accessibility metadata;
• screen-reader testing;
• human accessibility QA.

A technically correct page list cannot compensate for poor semantic structure elsewhere in the publication.

Likewise, an otherwise accessible EPUB can become harder to use in academic environments when useful source-page references are lost.

Publishers therefore benefit from considering these requirements together rather than treating them as isolated technical tasks.

How Gentize Supports Accessible EPUB Production

Gentize supports publishing workflows including:

• Accessible EPUB/EPUB3
• EPUB2/EPUB3 conversion
• XML and structured conversion
• Backlist conversion
• OCR and post-scan processing
• Screen-reader testing
• Keyboard testing
• Human accessibility QA

A relevant verified Gentize proof point is:

35,000+ title large-scale academic digitization project, delivering scanning, OCR, EPUB, POD, and accessible PDF.

Gentize also has a Strong production team and 50+ A11Y-certified testers with visual impairments.

These capabilities are particularly relevant to workflows connecting:

source material → digitization → structured conversion → EPUB → accessibility → human QA

Internal verification note: Do not state that every Gentize-produced EPUB automatically conforms to EPUB Accessibility 1.2 or automatically includes page navigation. Requirements and conformance claims should reflect the specification and QA scope agreed for the individual project.

Final Takeaway

EPUB page navigation addresses a simple but important question:

“How can I find the same page as someone reading another edition?”

The answer involves more than displaying page numbers.

A robust implementation connects:

Static pagination source → Page-break markers → Page list → Reading system → Reader

For academic, educational and mixed print/digital publishing, these stable references can support accessibility, teaching, research and cross-format navigation.

And the most efficient time to preserve those relationships is usually during production—not after the EPUB has already been completed.