At a glance
PDF tags describe semantic relationships such as headings, paragraphs, list items and table cells. Correct roles and a meaningful sequence help readers navigate. A populated tree or familiar role name is not sufficient: the tags must represent the actual content, and decorative artifacts are handled separately from meaningful structure.
This is an explanatory outline, not raw PDF syntax or a complete standards tree.
| Content | Intended role | Review question |
|---|---|---|
| Application instructions | H1 | Is it the main heading? |
| Who can apply | H2 | Does hierarchy reflect the section? |
| First instruction | P | Is it one coherent paragraph? |
| Required documents | L / LI | Are labels and bodies associated? |
| Fee schedule | Table / TR / TH / TD | Can each value be identified? |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Common roles and what to inspect
This dictionary introduces commonly encountered roles. PDF versions, custom role mapping and conformance specifications can affect the full vocabulary. Consult the relevant standard and validator for normative requirements.
| Role | Purpose | Inspect |
|---|---|---|
| Document / Sect | Group the document and sections | Meaningful nesting and content coverage |
| H1–H6 / P | Headings and paragraphs | Hierarchy, text boundaries and sequence |
| L / LI / Lbl / LBody | List and item relationships | Marker and item text remain associated |
| Table / TR / TH / TD | Table, row, header and data cells | Correct relationships, spans and values |
| Figure | Meaningful non-text content | Appropriate description or data alternative |
| Link | Link content and relationship | Purpose and destination |
| Form | Form-related content | Names, roles, values and actual task behavior |
Scroll sideways to see all columns. Use arrow keys when the table is focused.
Decoration should not become body content
Decorative content can be marked as an artifact instead of entering the meaningful reading sequence. Repeating furniture such as a purely decorative line is different from a consequential footnote, label or instruction.
Do not mark confusing content as decorative merely to remove a checker finding. Compare it with the source and ask whether a reader needs the information. A company logo that communicates identity may need different treatment from a background flourish.
- Keep meaningful captions and qualifications in the reading sequence.
- Review repeated headers and footers in context.
- Do not equate an artifact marker with a missing tag defect.
Review the relationships, not just the names
A paragraph tagged as a heading can create false navigation. A table tagged as paragraphs can lose its data relationships. Conversely, a correctly named role in the wrong sequence can still make the document confusing.
Use a tag viewer to inspect the structure, then test the exact revision with appropriate manual and assistive-technology checks. For detailed tables, forms, languages and title settings, follow the existing specialist guides and primary techniques linked below.
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 PDF6: table markup
Table, row, header and data-cell structure in PDF.
- W3C PDF4: decorative artifacts
Keeping decorative content out of the meaningful reading sequence.
- W3C PDF12: form field names, roles and values
Programmatic field information required for usable PDF forms.
Written by the DocAccessible team under our editorial policy. Suggest a correction if a source or product detail needs updating.