Accessible Footnotes and Endnotes in EPUB: Publisher Guide

Accessible Footnotes and Endnotes in EPUB: How Publishers Can Improve Note Navigation

Footnotes and endnotes seem simple in print.

A reader sees a small reference number, looks to the bottom of the page or the end of the chapter, reads the note, and continues.

In a reflowable EPUB, that same interaction is different.

There may be no fixed page bottom.

A note may live in another part of the chapter or even another content file.

A reader using assistive technology may follow a note reference and then need a reliable way to return to the exact sentence they were reading.

That makes footnotes and endnotes more than a formatting problem.

They are a navigation, structure, and reading-experience problem.

Accessible notes should let readers move from the main text to supporting information—and back again—without losing their place.

Quick Answer: What Makes EPUB Footnotes and Endnotes Accessible?

A strong EPUB note workflow should:

• Identify the note reference as an actual link
• Connect each reference to the correct note
• Give the note meaningful structural identification
• Keep notes from unnecessarily disrupting the main reading flow
• Provide a clear route back to the source reference when appropriate
• Group endnotes logically
• Preserve consistent numbering
• Test the navigation after conversion or remediation

Current accessible-publishing guidance specifically recommends linking note references to their notes, grouping endnotes logically, and providing backlinks where they improve navigation.

A practical workflow is:

Reference → Note → Read → Return → Continue

Why Notes Become More Complicated in EPUB

Printed notes rely heavily on physical location.

A footnote might be:

at the bottom of page 42

An endnote might be:

note 14 at the end of Chapter 3

A reflowable EPUB does not behave like a fixed printed page.

Readers may change:

• Font size
• Screen size
• Margins
• Line spacing
• Reading orientation
• Display preferences

That means the digital reading experience cannot depend solely on where the note appears visually.

The EPUB needs explicit relationships.

Print Notes vs EPUB Notes

The digital version therefore needs to preserve the relationship, not merely copy the printed appearance.

1. Every Note Reference Should Be a Real Link

Consider this sentence:

Publishing workflows continue to evolve.¹

Visually, the superscript “1” suggests a footnote.

But if it is only styled text, a reader may need to search manually for note 1.

A stronger EPUB implementation makes the reference an actual link to the note.

The relationship becomes:

Reference 1 → Footnote 1

Accessible-publishing guidance recommends using linked note references so readers do not have to visually locate the corresponding note.

Publisher QA question

Do not ask only:

“Does the superscript look correct?”

Ask:

“Can the reader activate the reference and reach the correct note?”

2. Notes Need Semantic Identification

A paragraph that visually looks like a footnote is not necessarily programmatically identified as one.

EPUB provides publishing semantics for notes, while accessibility roles can communicate note purpose to assistive technologies.

One important technical distinction is that EPUB publishing semantics can help reading systems provide special behaviours, but they do not by themselves provide the same assistive-technology meaning as accessibility roles. EPUB 3.4 explicitly distinguishes these functions. W3C

For production teams, the practical lesson is:

Do not rely on visual styling alone.

A note should be represented structurally as a note.

3. Make Returning to the Main Text Easy

Following a note is only half the journey.

The reader also needs to continue reading.

Imagine someone is halfway through a long paragraph.

They activate note 17.

They read the explanation.

Now they are somewhere else in the EPUB.

If there is no useful way back, they may need to:

• Search for the sentence
• Navigate through headings
• Move through paragraphs
• Reopen reading history

Current guidance recommends backlinks from notes to their references when they help users restore context.

The reading pattern should feel like:

Main text → Note → Return → Same reading position

not:

Main text → Note → Find your own way back

4. Return Links Need Useful Context

Suppose every note contains a link labelled:

“Back”

That may work visually.

But if a user reviews a list of links independently, multiple identical “Back” links can become ambiguous.

A clearer return mechanism should communicate where the reader is returning.

For example:

• Return to note reference 3
• Return to Chapter 4 note reference 8

Current guidance warns against repetitive backlink text that loses meaning when links are presented outside their surrounding context.

Key Principle

A navigation link should still make sense when heard without the surrounding paragraph.

5. Footnotes Should Not Interrupt the Main Narrative

Another EPUB problem occurs when footnote text is inserted directly into the main reading sequence.

A sighted reader may visually ignore the footnote.

A screen reader may encounter:

Main sentence → entire footnote → next sentence

even when the reader never asked to open the note.

This can make a chapter difficult to follow—particularly in academic books containing dozens of notes.

Current accessible-publishing guidance recommends identifying notes clearly and placing them at logical breaks to minimize disruption to the primary narrative.

This allows reading environments to treat secondary information more intelligently.

6. Group Endnotes Logically

Large academic books may contain hundreds of notes.

Dumping all notes into an undifferentiated block creates poor navigation.

A better structure might be:

Notes

• Chapter 1
• • Note 1
  • Note 2
  • Note 3
• Chapter 2
• • Note 1
  • Note 2
• Chapter 3
• • Note 1

Current guidance recommends grouping endnotes in an identifiable endnotes section and using ordinary list structure where appropriate.

This gives readers useful hierarchy.

7. Avoid an Outdated Individual-Endnote Pattern

This is an important current technical point for production teams.

The role historically used to identify an individual endnote is now deprecated in current accessible-publishing guidance because of incompatibility with modern list semantics.

Instead, the recommended direction is to:

• Identify the overall endnotes section
• Use normal ordered-list or list-item structure for the individual notes

For publishers maintaining old conversion specifications, this is worth reviewing.

A production rule written several years ago may no longer reflect current best practice.

8. Footnotes and Endnotes Are Not the Same Production Pattern

The content may be similar, but the reading behaviour differs.

Footnotes

Typically associated closely with a specific passage.

They may be stored near the relevant content or grouped logically depending on the publication strategy.

Endnotes

Typically collected:

• At the end of a chapter
• At the end of a section
• At the end of the book

For long note collections, endnotes benefit strongly from:

• Section headings
• Lists
• Direct reference links
• Return links
• Clear numbering

The correct production approach should reflect the publication structure.

9. Notes Inside Tables Need Extra Care

Academic tables often use note markers such as an asterisk (*), dagger (†), double dagger (‡), or numbered references (1, 2) to connect specific cells or values with explanatory notes.

Those notes should remain clearly associated with the table rather than being treated as ordinary document footnotes.

A good EPUB structure should make the relationship clear:

Table content → Note reference → Table note → Return to context

Current accessibility guidance recommends keeping table notes outside the table structure itself while maintaining a clear association between the table and its notes.

Why this matters

Placing explanatory notes inside structural areas intended for table data or summaries can confuse the table model and make navigation harder for assistive-technology users.

The reader should be able to move logically through:

Table cell → Note reference → Table note → Return

10. Numbering Must Remain Consistent

Note numbering problems are easy to introduce during conversion.

Examples include:

• Note 12 links to note 13
• Two references use the same destination
• Note 7 is missing
• Chapter numbering resets incorrectly
• Roman numeral references are converted incorrectly
• Symbols no longer match their notes

For large backlists, these errors can become systematic.

QA should compare:

Source reference ↔ Digital reference ↔ Destination note ↔ Return destination

This is not simply link validation.

It is relationship validation.

Note Placement: Inline, Chapter-End or Book-End?

There is no single layout that suits every publication.

The right choice depends on:

• Number of notes
• Publication type
• Reading flow
• Existing editorial structure
• Distribution requirements
• Compatibility needs

A useful decision framework is:

The priority should always be:

Preserve context without forcing secondary content into the primary reading flow.

How Notes Affect Screen-Reader Experience

Human QA should test more than whether links exist.

Review what actually happens when a reader:

1. Encounters a note reference
2. Activates it
3. Arrives at the note
4. Reads the note
5. Activates the return link
6. Continues from the correct location

Listen for problems such as:

• Unclear link purpose
• Excessive announcement
• Incorrect numbering
• Wrong destination
• Loss of reading position
• Notes announced unexpectedly
• Confusing note-group hierarchy

The technical relationship may validate correctly while the reading experience remains awkward.

Automated QA vs Human QA for Notes

The principle is the same as other accessibility work:

Technical validity confirms implementation. Human QA evaluates usability.

A Publisher Workflow for Accessible Notes

Stage 1 — Inventory

Identify:

• Footnotes
• Endnotes
• Table notes
• Notes linked from figures
• Chapter-specific notes

Stage 2 — Classify

Determine where notes belong structurally.

Stage 3 — Link References

Each note reference should connect to the correct destination.

Stage 4 — Apply Semantic Structure

Represent note references, notes, and grouped endnote sections appropriately.

Stage 5 — Add Return Navigation

Provide an effective way back where required for the reading experience.

Stage 6 — Check Numbering

Verify:

• Sequence
• Symbols
• Chapter resets
• Source alignment

Stage 7 — Validate

Check structural and link integrity.

Stage 8 — Human Accessibility QA

Test real reading journeys.

Stage 9 — Correct and Retest

Recheck every changed relationship.

The complete process becomes:

Identify → Structure → Link → Return → Validate → Human Test → Retest

Common EPUB Note Problems

Note numbers are only superscript text

They look correct but are not navigable.

Reference goes to the wrong note

Technical links exist, but the relationship is incorrect.

No return navigation

Readers lose their place.

All notes interrupt reading automatically

Secondary information becomes part of the main narrative.

Endnotes have no structure

Readers face one long undifferentiated block.

Old semantics are reused indefinitely

Legacy conversion specifications may contain patterns that current guidance no longer recommends.

Print placement is copied directly

Digital notes need relationships and navigation, not merely print-like appearance.

Publisher QA Checklist

Before approving an EPUB containing notes, confirm:

• Every note reference is identifiable
• Each reference links to the correct note
• Note numbering matches the source
• Footnotes are structurally identified
• Endnote sections have clear headings
• Large note groups use logical list structure
• Table notes remain associated with their tables
• Return navigation works where needed
• Link wording is understandable
• Notes do not unnecessarily interrupt the narrative
• Cross-file links work
• Human accessibility QA is complete
• Corrections have been retested

The critical question is:

Can a reader explore a note without losing the book?

How Gentize Supports Accessible EPUB Note Workflows

Gentize supports publishing workflows that include:

• Accessible EPUB/EPUB3
• EPUB conversion
• Backlist conversion
• Structural remediation
• Screen-reader testing
• Keyboard testing
• Human accessibility QA
• XML and structured conversion

A relevant Gentize proof point is:

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

Academic and scholarly backlists frequently contain dense structures such as:

• Notes
• References
• Tables
• Figures
• Page references
• Cross-references

That makes controlled structural conversion and human QA especially important.

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

Internal verification required: Before public publication, retain only the proof points currently approved for external use.

Final Takeaway

Accessible EPUB notes are not created simply by making numbers superscript.

They require a complete navigation relationship:

Reference → Note → Return → Continue Reading

For publishers, the strongest approach is to ensure that:

• References are real links
• Notes are semantically structured
• Endnotes are logically grouped
• Return navigation preserves reading context
• Numbering remains faithful to the source
• Human accessibility QA tests the actual journey

A reader should be able to explore supplementary information without being punished for leaving the main narrative.

That is the difference between a note that merely exists in an EPUB and one that genuinely supports an accessible reading experience.

Gentize CTA

Have academic, educational, scholarly, or backlist EPUBs containing hundreds of footnotes and endnotes?

Start with a representative title containing the most complex note patterns.

Gentize can assess note structure, navigation, return links, cross-references, and assistive-technology behaviour before a remediation or conversion workflow is scaled across the catalogue.