PDF bookmarks and tables of contents: build usable navigation

Build PDF navigation around the tasks readers need to complete: finding a section, understanding where it sits, and returning to the wider document. Start with meaningful source headings, generate bookmarks and contents links where the exporter supports them, and verify every destination in the final file. A navigation pane full of entries is useful only when those entries match the publication.

Give each navigation mechanism a clear purpose

Heading tags express the structure of the content. Bookmarks form a separate navigation outline in viewers that expose them. A table of contents is part of the document itself and can include links to sections. W3C technique PDF2 illustrates bookmark creation from authoring structures and after conversion. These examples do not mean that adding bookmarks repairs missing heading semantics.

For a fictional volunteer handbook, a reader might need to jump directly to 'Claiming travel expenses'. A bookmark called 'Section 4' is less informative than the section's meaningful title. A contents page should support the same task, including for readers who encounter the file in a viewer that does not prominently display its bookmark panel.

Design a hierarchy that reflects the document

Avoid creating an entry for every short paragraph simply because automation permits it. Use enough depth to distinguish major sections and important subsections, then test whether someone unfamiliar with the document can predict where information lives. Keep the hierarchy consistent with the actual content, and resolve misleading section names with the author rather than patching only the navigation label.

Generate navigation from the source when possible

Microsoft's Word PDF accessibility documentation describes export information for headings, contents entries, and bookmarks, with bookmark creation dependent on the selected option. Inspect the settings available in your Word version and update the source contents field before export. An exporter cannot make an outdated contents page factually correct.

If the source is unavailable, add or correct bookmarks in a PDF editor. Adobe's bookmark documentation explains bookmark destinations and hierarchy. Set each destination while viewing the intended section, then verify it after saving. Do not confuse changing the bookmark's label with changing the content it opens.

1. Confirm the approved section names and their hierarchy before generating navigation.
2. Export with the applicable bookmark and tagging options enabled.
3. Compare the bookmark outline with the heading structure and contents page.
4. Correct missing, duplicate, misleading, or misplaced entries.
5. Open the saved file again and follow every bookmark and contents link.

Check destinations and keyboard operation

A destination should reveal the intended content at a useful position. Landing halfway through the preceding section may technically change pages while failing the reader's task. Check whether the section heading is visible, whether the view is usable, and whether a repeated title in an appendix has accidentally received the destination intended for the main chapter.

Test the contents links with a keyboard in a supported viewer. Confirm that link names communicate their destinations, focus is usable, and activation reaches the expected material. Separately inspect the contents page's reading order so titles and page references do not become a confusing sequence of disconnected numbers. Record viewer-specific limitations instead of assuming all PDF readers expose navigation identically.

Keep navigation current through revisions

Suppose the expenses section moves after an updated policy chapter. The label 'Expenses' may still look correct while its destination points to the old location. After inserting, replacing, or combining pages, repeat destination checks and compare printed page references with logical page labels. Review new and removed sections as well as moved ones.

Keep a concise release record listing the PDF revision, navigation checks, viewer, and unresolved issues. For long documents, an inventory of bookmarks and contents entries makes the review reproducible. Use the tag-role reference alongside this work if the content structure itself needs repair, and avoid presenting a working outline as evidence that every part of the document is accessible.

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. W3C PDF2: Creating bookmarks
2. Microsoft: Word PDF accessibility
3. Adobe: Page thumbnails and bookmarks