FFCheckPrivacyCheck
♿ Accessibility

Making PDFs accessible (PDF/UA + ISO 14289)

Tagged PDF, reading order, alt text, form fields. Mandatory for government + post-EAA for many commercial PDFs (invoices, contracts, product documentation).

Last reviewed: 25 May 2026
PDFs are historically a nightmare for screen readers — scanned pages = pixels without structure. PDF/UA (ISO 14289) is the standard for accessible PDFs. Mandatory for: (a) government since the Dutch Temporary Decree, (b) commercial documents under EAA if they're "essential for use of products and services" (invoices, contracts, product documentation). Four core requirements: (1) Tagged PDF: every text, image, list, table has a tag (H1, P, Figure, Table, List). Untagged = unreadable for screen reader. (2) Reading order: order in which screen reader reads content. Can differ from visual layout (especially multi-column documents). (3) Alt text: images + charts + signature fields get description. (4) Form fields: PDF forms must have label linking + tab order + autocomplete. How to create? Word → PDF: use "Save As PDF" with "Document structure tags for accessibility" option. InDesign: use styled paragraphs, alt text on images, "Export as PDF Tagged". Acrobat Pro: "Make Accessible" tool + manual reading-order check. Test: Adobe Acrobat Pro Accessibility Check + axe Acrobat Pro plugin. PAC (PDF Accessibility Checker) is a free Windows tool. Quick practical tip: reduce PDF use. HTML/web page is almost always more accessible than PDF. Keep PDF only for: signable documents, print-intended docs, archival requirements.

Sources

🔎 Common search variants

Recognise your own search? Our answer above covers these too.

  • accessible pdf
  • pdf ua
  • tagged pdf
  • pdf wcag