Accessible PDF footnotes and endnotes: references that work

Make PDF footnotes and endnotes usable by preserving their relationship to the main text and testing the journey to the note and back. A superscript number is only a visual cue. Readers also need to understand what the note qualifies, reach the complete explanation, and continue without losing their place. This matters particularly when a note changes the interpretation of a statistic or a condition.

Identify the note's editorial purpose

In a fictional evaluation report, a sentence says that participation increased, with a note explaining that one location was excluded. The note is substantive because it changes how the claim should be interpreted. Do not remove it from the accessible reading experience simply because it sits in a smaller font at the bottom of the page.

Distinguish explanatory notes from bibliography entries, running footers, and decorative separators. A line drawn above the note may be page decoration; the note's qualification is content. Where an essential condition is easy to miss, discuss moving it into the main text with the author. Accessibility repair should preserve meaning, but the author may improve the wording and placement before export.

Use the authoring tool's note features

Create real footnotes or endnotes in the source instead of typing a superscript number and a separate text box. Microsoft's Word PDF accessibility documentation illustrates exported note text and reference links. The published mapping is useful context, but the final PDF still needs inspection because version, content, and export choices can affect the result.

Before export, update numbering, resolve deleted notes, and confirm every reference against its note. Check repeated references deliberately: two passages may refer to the same explanation, but a duplicated number can also be an editing error. Keep an inventory for long publications so a reviewer can account for each note without relying solely on visual scanning.

Check the PDF version before changing note tags

The PDF Association's standard structure element cheat sheet distinguishes the PDF 1.7 Note vocabulary from the PDF 2.0 FENote element and its compatibility mapping. Do not rename every note to whichever tag looks newest. Apply the structure and relationship requirements of the actual PDF version and conformance target, including appropriate namespaces where applicable.

Inspect the content associated with the note as well as its name. A correctly named element containing the wrong paragraph is still a substantive problem. Check whether a long note continues across pages and whether all its text remains grouped meaningfully. A page boundary should not silently detach the second half of an explanation.

Test links and the uninterrupted reading sequence

Where references are links, inspect both their structural representation and their destinations. W3C technique PDF11 describes link annotations and Link structure. A clickable superscript in one viewer is not enough evidence that its purpose and relationship are exposed consistently. Test activation using a keyboard and the intended assistive setup.

Read the surrounding passage continuously as well as using the link. Confirm that the reference is understandable and that the note does not interrupt the middle of an unrelated sentence. Then follow the note and return. Record the actual behavior; return paths can require deliberate authoring or repair, and a viewer's history command is not the same as an authored return link.

Review the final publication after revisions

1. Account for every reference and note, including repeated references and continuation text.
2. Compare note wording with the approved source, especially exceptions, units, and qualifications.
3. Inspect note structure using the document's PDF version and chosen validation profile.
4. Follow reference and return routes in the final saved file with a keyboard.
5. Repeat checks after inserting, deleting, renumbering, or moving notes and pages.

Keep the note inventory with the release review. A record such as 'reference 3 now reaches the exclusion note and returns to the findings sentence' explains what was fixed. A generic 'footnotes accessible' label does not show whether the reviewer tested structure, wording, or navigation.

For research publications, combine this work with the research-paper workflow. Use the link guide and screen-reader testing guide when documenting the reader journey. None of these checks replaces subject-matter review of what the notes actually claim.

Frequently asked questions

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

1. Microsoft: Word PDF accessibility, footnotes and endnotes
2. PDF Association: Standard structure elements
3. W3C PDF11: Link annotations and structure