PDF Conversion Issues

Fix Missing Link Tags for Word Footnotes in Tagged PDF

Muhammad TalhaMuhammad Talha Nov 3, 2026 869 views

Question details

Missing Link and OBJR structure elements for footnotes when converting a Word document to a tagged PDF, resulting in PAC accessibility errors.

How to Fix Missing Link Tags for Word Footnotes in Tagged PDFs
Product
Microsoft Word
Device & OS
not provided
Scenario
Exporting a structured Word document containing footnotes into a tagged PDF for accessibility compliance.
Observed behavior
Footnotes in paragraphs that span across a page break cause the PDF tagging to fail. The exported PDF lacks proper Link and OBJR tags, and subsequent text in the paragraph is either untagged or tagged multiple times, triggering PAC errors.
Before you start

Before modifying paragraph layouts, deleting footnotes, or adjusting table structures, save a backup copy of your original Word document to protect your formatting.

Solution 1Recommended

Adjust Pagination to Prevent Page Breaks in Footnote Paragraphs

Since the tagging bug is triggered by paragraphs spanning across two pages while containing a footnote, forcing the entire paragraph onto a single page avoids the issue.

This workaround effectively bypasses the native export bug in both Microsoft Word and the Acrobat PDFMaker ribbon by ensuring the structural elements do not split across physical document pages.

1
Locate the affected paragraph

Find the paragraph that contains the missing footnote tag and stretches across a page break in your Word document.

2
Keep lines together

Highlight the paragraph, right-click, and select 'Paragraph'. Go to the 'Line and Page Breaks' tab and check the 'Keep lines together' option.

3
Manually insert a page break

Alternatively, place your cursor at the beginning of the affected paragraph and press Ctrl+Enter to push the entire paragraph to the next page.

4
Re-export the PDF

Save your document and export it to PDF again to verify that the PAC accessibility errors are resolved.

Adjust Pagination to Prevent Page Breaks in Footnote Paragraphs
Accessibility Passed: Keeping the footnote entirely on one page ensures the PDF converter successfully maps all OBJR and Link structures.

Convert Word to PDF Seamlessly with WPS Office

If you are struggling with persistent PDF tagging and export bugs in Microsoft Word, WPS Office offers an integrated, highly reliable PDF converter. It natively processes complex document structures to generate accurate PDFs.

  1. 1. Open your document in WPS Office: Launch WPS Writer and open the problematic Word (.docx) document.
  2. 2. Access the PDF export tool: Click on 'Menu' in the top-left corner and select 'Export to PDF'.
  3. 3. Configure export settings: Adjust your save location and export preferences in the prompt window.
  4. 4. Export your file: Click 'Export to PDF' to generate a clean, accurate PDF document without broken structure elements.
100% compatible with Microsoft Word (.docx) formatsBuilt-in Export to PDF feature maintains complex layouts and footnotesLightweight, fast, and completely free to useFamiliar interface requires zero learning curve
microsoft office alternative - wps office

Frequently Asked Questions

What are Link and OBJR elements in a tagged PDF?

In an accessible (tagged) PDF, Link tags identify hyperlink structures, while OBJR (Object Reference) elements represent the interactive, clickable parts of that link, such as a footnote reference. These tags are strictly required for screen readers to navigate the document correctly.

Why does the PAC error only occur on certain footnotes?

This error is a known conversion bug that typically triggers when a paragraph containing a footnote spans across a physical page break. The export utility gets confused by the split, causing it to drop the Link tags and either duplicate or miss tags for the text that follows.

Will using the Adobe Acrobat ribbon in Word fix the missing link tags?

Not necessarily. Users report that this specific footnote tagging issue persists whether you use Microsoft Word's native 'Save as PDF' function or the Adobe Acrobat PDFMaker ribbon add-in, indicating a deeper structural conflict during conversion.