Follow the headings and figures in a PDF tag tree
Admin ·
Review the declared sequence of a tagged PDF when a drawing looks correct but you need to check how its parts are described and linked. Work from a known example before reviewing a larger document.
Follow the first heading and its map
Choose Load example PDF and show Page 1. The Document tag is titled Trail orientation. Its section starts with H1 and a marked-content reference with MCID 0.
Find Photo → Figure. The PDF uses a custom name and resolves it to Figure in its role map. Read its Alt value Two green markers along the trail. Collapse the containing section to hide its descendant tags, then expand it to continue.
Tagged North Trail sample PDFW3C technique PDF1 for Figure alternatives
Compare references from different pages
Show Page 2. Its H2 tag also has MCID 0, and its Figure references MCID 1. The page context distinguishes these references from the same number on Page 1.
The second Figure has neither Alt nor ActualText. Continue to the Link tag and find its object reference. The output keeps object references separate from marked-content IDs.
Tagged North Trail sample PDFW3C technique PDF3 for reading order
Check the declared order with a reader
Download the JSON report. Reference entries keep their reading positions, even when you filter the displayed tree by page. Check the page, kind and MCID or object reference together.
Use the structure as evidence when testing the PDF with keyboard navigation and the intended assistive technology. Choose another tagged export if you need to compare how a corrected role or reading sequence is represented.
Common questions
Why does showing a page also show the Document tag?
The filtered view keeps ancestor tags so each page's entries retain their tree context.
Will I see the same marked-content ID in two places?
Yes. MCIDs belong to a page or content stream. Keep the page and stream context with the number when comparing references.