Use numbered headings, not the generic H tag

PDF/UA check H_TAG_USAGE · Headings · severity High · PDF/UA 8.2.5.12 Headings

↩ Back to the rules index · WCAG cross-reference

Why it matters#

The generic H tag provides no heading level information. PDF/UA-2 requires numbered heading types (H1 through H6) so screen readers can communicate the document hierarchy to users.

What you will see#

The document uses the generic H tag, which carries no level information.

How to fix#

Replace each generic H tag with the numbered heading type (H1-H6) that matches the heading's level in the document hierarchy. In Acrobat: Tags panel > select the tag > Properties > change the Type.

Step-by-step guide#

1. Open the Accessibility tags panel (View > Show/Hide > Side panels > Accessibility tags) and locate every generic H tag; the EQChecker report gives the count and pages.
2. Determine each heading's level from the document outline: a main section heading is H1, its subsections H2, and so on down to H6.
3. Select each H tag, open its context menu > Properties, and change the Type to the matching numbered heading (Acrobat lists these as Heading Level 1 through Heading Level 6, which write H1-H6).
4. Check the role map (Accessibility tags panel options menu > Edit Role Map) for custom tags mapped to H and repoint them to a numbered level instead.
5. Where the PDF comes from an authoring tool, prefer fixing at source: apply proper heading styles in Word or InDesign and re-export - style-based exports emit numbered headings, never generic H.

Verify: Re-run the EQChecker scan: H_TAG_USAGE should report zero errors.

Note: PDF/UA-2 only: ISO 14289-2 8.2.5.12 says conforming files shall use H1-Hn and shall not use H, because generic H forces processors to track section depth and creates ambiguity. PDF/UA-1 (ISO 14289-1 7.4.4) permits generic H in strongly structured documents, so files authored to UA-1 commonly trip this rule.

Fixing it in your authoring tool#

WCAG success criteria#

1.3.1 Info and Relationships — Level A#

Structure and relationships conveyed visually (headings, lists, tables, labels, groups) must also be available programmatically.

Understanding 1.3.1

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549