At a glance
PDF-to-HTML conversion should map the source’s meaning to semantic HTML, not copy every drawing operation into an absolutely positioned box. Headings, lists, tables and links have different relationships. A tag tree can provide useful evidence, but the output must be checked against the actual source and reader tasks.
The HTML side is an intended semantic outcome, not an automatic conversion guarantee.
| Source meaning | HTML outcome | Review focus |
|---|---|---|
| Section heading | h2 | Hierarchy and navigation |
| Ordered steps | ol with li | Order, nesting and labels |
| Data relationship | table with headers | Values and associations |
| Chart and explanation | figure plus description/data | Equivalent important information |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
A practical semantic map
Use the map as a review aid rather than a mechanical role substitution table. The source can be untagged or incorrectly tagged, and PDF layout alone can be ambiguous.
| PDF evidence or content | HTML choice | Verify |
|---|---|---|
| H1–H6 heading | h1–h6 at the appropriate level | One meaningful page title and logical sections |
| P paragraph | p | Coherent text and correct sequence |
| L / LI list | ul or ol with li | Whether sequence is meaningful |
| Table / TR / TH / TD | table / tr / th / td | Header associations and merged cells |
| Figure with caption | figure / img / figcaption and description | The information the image communicates |
| Link | a with an appropriate href | Purpose, target and surrounding context |
| Interactive form | Labeled controls in a reviewed task flow | Behavior as well as names and values |
| Decorative artifact | Excluded from meaningful sequence | No important content is lost |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Some mappings need an editorial decision
A multi-column layout may become one sequential flow in HTML. A chart may need explanatory text and a data table. A scanned page first needs reliable text recovery. Those choices require comparison with meaning, not just a visual screenshot match.
Forms deserve particular care: copying an application’s boxes into HTML does not create a working submission process. Preserve instructions and obtain a reviewed interaction design. Keep signatures and original-download requirements explicit.
- Page furniture: separate repeated decoration from meaningful notes.
- Footnotes: preserve the connection to the relevant passage.
- Complex tables: review grouped headers and spans.
- Custom PDF roles: investigate their meaning before mapping.
Check the output in its reading environment
Inspect the HTML outline and DOM semantics, compare consequential content, then navigate with keyboard and suitable assistive technology. Verify the mobile presentation without changing the reading relationships.
Record source and output versions with test coverage and unresolved findings. Structural checks, text fidelity and visual comparison each answer different questions. A successful output file is not a completed accessibility evaluation.
Sources and scope
Methods, worksheets and illustrative examples are DocAccessible editorial contributions. These references support the technical or product details described above. W3C techniques are informative guidance; they are not a certification scheme.
- W3C PDF9: PDF headings
Heading tags communicate document structure.
- W3C PDF21: list tags
List, item, label and body structure.
- W3C H63: HTML table header scope
Associating row and column headers with data cells in HTML.
- W3C PDF12: form field names, roles and values
Programmatic field information required for usable PDF forms.
- W3C PDF4: decorative artifacts
Keeping decorative content out of the meaningful reading sequence.
Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.