
A PDF table can show bold column labels while its structure still treats those labels as ordinary data or unrelated text. Inspect the table tags, including rows, header cells and data cells. Then review the actual catalog with the recipient's reading method. Repeating a visible label on each printed page does not establish that assistive software receives the table's relationships.
Key Takeaways
- Visual headings and PDF table-header tags are different evidence.
- Inspect the saved table's structure rather than its appearance alone.
- Complex merged cells may be better rebuilt in the source application.
Name the relationship the reader is missing
For a proposed photo catalog, each row might contain an asset identifier, revision and approval status. Record which label explains each value. If a listener hears only a series of numbers and short words, identify the affected row and expected context before attempting repairs.
A header that vanishes visually on the next page is the separate InDesign continuation problem. This task can occur even in a one-page PDF with every label visible. Do not duplicate labels manually and assume the table has acquired the missing semantic structure.
Keep the source layout and an identified PDF candidate. Where possible, correct repeatable authoring problems in the source, so a later export does not require the same repair again. An approved visual layout is worth preserving while its information structure is reviewed.
Inspect the actual table tags
Adobe's table-tag instructions describe Table containing rows, with TH header cells and TD data cells inside TR rows. Tables can also use THead, TBody and TFoot sections containing those rows. Expand the relevant table in the Tags panel and compare it with the intended catalog grid.
Use a bounded check:
- Identify the disputed table in the document.
- Inspect whether it has an appropriate Table structure.
- Expand the rows and distinguish actual header cells from data cells.
- Check that the represented cells correspond to the visible information.
- Review any spanning cells before accepting the relationships.
Changing a large text line into a heading tag is not this operation. The heading export guide concerns document sections; a column label needs the table role that matches its job.
Treat merged cells as a structural decision
Adobe documents ColSpan and RowSpan attributes for cells that span columns or rows. A visually merged rectangle does not, by itself, prove those relationships exist in the exported structure. Record the intended span before editing attributes, and retain a comparison copy.
The documentation warns that cell-level repairs can be labor-intensive and recommends recreating suitable tables in the authoring application. If the table is complex or the repair exceeds your tagging expertise, return it to the responsible document author. Do not force every irregular table into a simple grid merely to make an automated check stop reporting an issue.
Verify meaning in the delivered catalog
Adobe's accessibility-checking guide recommends manual review because table structures can be complex. Reopen the actual delivery PDF and check a header, a representative middle row and any merged region through the intended assistive reading route. Record the software and observations rather than declaring success from the presence of TH tags alone.
Keep surrounding photo-and-caption relationships intact too. Accept the table when its labels, values and relevant relationships can be understood in the tested workflow. A clean visual proof and an automated report are useful inputs, but neither replaces that final reading check.
Related tasks
- Why Does My InDesign Table Lose Its Column Labels on the Next Page?
- Why Does My Large InDesign Heading Export as an Ordinary Paragraph in an Accessible PDF?
- Why Does a Screen Reader Read My Photo-Catalog Caption Before the Wrong Image?
Sources and scope
- Adobe Acrobat: Edit document structure with the Content and Tags panels: Documents Table/TR/TH/TD structure, optional table sections, cell RowSpan and ColSpan attributes, and returning complex table construction to the authoring application.
- Adobe Acrobat: Create and verify PDF accessibility: Table structure and headers need inspection; complex table accessibility is best checked manually, not inferred from a correct-looking page.
Based on supplied complete Adobe table-structure and accessibility documentation, reviewed October 29, 2026. No PDF tags were edited and no assistive reading test was run. The catalog example is hypothetical. This guide does not invent an unverified Scope dialog procedure or certify a complex table.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.