PDF Compliance Techniques

All images must have text alternatives (`/Alt` entry) for screen readers

Use PDF authoring tools to embed descriptive alternative text for every informative image

Screen readers announce correct alternative text and inspection tools verify `/Alt` entries

Long documents must contain bookmarks for clear hierarchical navigation

Generate table of contents in source document and configure PDF conversion to create bookmarks from headings

Bookmarks panel displays functional outline with correct section links

Tab order and screen reader reading order must be logical and consistent with visual layout

Structure documents logically in authoring application and use PDF editor to correct tag order for complex layouts

Tabbing through elements follows logical order and screen reader reads content in correct sequence

Purely decorative images must be marked as artifacts to be ignored by assistive technology

Use PDF authoring tools to apply `/Artifact` tag to decorative elements like background images and borders

Screen reader does not announce decorative images during reading

Users must be notified of mandatory form fields and their required status

Set "Required" property for mandatory form fields in PDF authoring tool

Alert appears for blank required fields and required status is programmatically available

Data tables must use correct structural elements (`Table`, `TR`, `TH`, `TD`)

Define header rows in authoring tool and inspect/repair table tags after PDF conversion

Screen reader correctly announces header-data relationships and tag tree shows logical hierarchy

Scanned image-only PDFs must be converted to searchable text using OCR

Use OCR functionality to convert images to text, review for errors, and add accessibility tags

Screen reader reads all text correctly and document can be saved as complete text

First occurrence of abbreviations must include full expansion for user understanding

Use PDF editing tool to add full expansion text using `/E` entry in tag properties

Screen reader announces both expansion and abbreviation on first use

All content sections must use appropriate heading tags (`H1` through `H6`)

Use built-in heading styles in authoring tool or apply/correct heading tags in PDF editor

Screen reader lists headings correctly and tag panel shows proper `H1`-`H6` structure

Every interactive form control must have programmatically associated label

Provide descriptive tooltip for each form field in PDF form creation

Accessibility API confirms name association and labels are positioned logically

All links must be programmatically determinable with descriptive link text

Create meaningful hyperlinks in source authoring tool or ensure visible link text is descriptive

Links are focusable, activatable with Enter key, and screen reader reads descriptive text

Form components must have name, role, and state/value programmatically available

Use form field properties dialog to define name (tooltip), role (control type), and value/state

Screen reader announces name and role correctly and state can be changed

Non-descriptive link text must have meaningful replacement text for assistive technology

Navigate to Link tag in PDF tag tree and add descriptive text in "Alternate Text" field

Screen reader reads descriptive alternate text instead of visible text

Documents should use consistent headers/footers for orientation information

Create headers/footers using authoring tool features and mark as pagination artifacts

Headers/footers are consistent and accurate across document

Forms must have clearly identified submit button that explicitly initiates action

Add button to form with "Submit a Form" action and "Mouse Up" trigger for keyboard accessibility

Submit button is present and can be tabbed to and activated with keyboard

Document must have default natural language specified in document catalog

Use PDF editing tool to set default language in document properties

Screen reader uses correct pronunciation rules for specified language

PDF viewer page numbering must match printed page numbers on document

Use PDF editor to define different page label ranges for multiple numbering schemes

Viewer navigation toolbar displays matching numbers and screen reader announces correct page

PDF must have descriptive title in metadata and display in window/tab bar

Enter descriptive title in document properties and set "Show" to "Document Title" in Initial View

Application title bar displays document title and screen reader announces it

Foreign-language passages must be tagged with correct language code

Use PDF editor tagging features to isolate foreign text and assign correct language

Screen reader switches pronunciation correctly for specified passages

Table tags with incorrect merged/split cells must be repaired

Use advanced PDF editor table repair tool to fix RowSpan/ColSpan properties

Screen reader navigates table logically and identifies correct header-data relationships

Ordered and unordered lists must use proper list tags (`L` and `LI`)

Use built-in list tools in authoring application or rebuild with correct tag structure in PDF editor

Screen reader identifies content as list and announces number of items

Form fields requiring specific format must validate input and provide clear error messages

Set validation pattern for fields and provide helpful error message explaining correct format

Field triggers alert for incorrect format and label states required format

All form fields must be interactive and fully operable with keyboard

Use form field recognition tool or manually add interactive controls to non-interactive forms

Entire form can be navigated using only keyboard with all fields functional