Back to reviews and guides

PDF Accessibility Guidelines: Understanding the Key Standards

This guide explains the key PDF accessibility standards (PDF/UA and WCAG), essential requirements such as tagging, reading order, alt text and forms, plus a clear remediation workflow. It includes testing steps, a decision framework for remediation versus alternatives, common mistakes and UK policy notes.

PDF Accessibility Guidelines matter when people with vision, cognitive or motor differences need to read your documents. This guide explains the key standards you must know, why they matter, and a clear, practical workflow to test and fix PDFs.

Which standards govern PDF accessibility?

Three standards appear across audits and policies.

  • PDF/UA (ISO 14289) — the machine-readable PDF standard for structural tagging, reading order and metadata.
  • WCAG — Web Content Accessibility Guidelines (2.0, 2.1, 2.2). Public accessibility policies normally use WCAG success criteria and levels such as AA.
  • National laws and policies — examples include the UK Public Sector Bodies Accessibility Regulations 2018 and the Equality Act 2010. These often require WCAG conformance for public documents.

How PDF/UA and WCAG relate

WCAG sets content-level success criteria. PDF/UA defines how a PDF must be structured so assistive technology can meet many WCAG criteria. For accessible PDFs aim to satisfy both PDF/UA and the WCAG level required by your organisation.

Core PDF Accessibility requirements

Make these elements correct before fine tuning.

Tagged PDF and structure tree

Every meaningful element must be in the tag tree. Headings must use heading tags H1 through H6. Paragraphs, lists and figures need the correct roles so screen readers can present content logically.

Logical reading order

The visual layout must match the internal reading order. Use the order view or tag tree to confirm. Reading-order errors often come from complex layouts or when a document was “printed to PDF” instead of saved with tags.

Alternative text for images

Provide concise alt text for informative images. Mark decorative images as artifacts so they are skipped by assistive tech.

Tables

Use real table markup. Specify header cells and scope. Avoid using tables for layout. Complex tables need summaries or captions to explain purpose.

Headings and bookmarks

Use semantic headings in the tag tree. Add document bookmarks that mirror headings to help navigation.

Forms and interactive elements

Label every form field with an accessible name. Associate labels with fields and provide clear instructions and error messages that are detectable by assistive tech.

Language and metadata

Declare the document language in the PDF properties. Set a descriptive Title in metadata. These signals let screen readers select correct pronunciation and present context.

Colour contrast and text

WCAG contrast ratios apply to PDF text. For normal text aim for a 4.5:1 ratio and for large text a 3:1 ratio. Avoid using colour alone to convey meaning.

Fonts and encoding

Embed fonts and ensure text is actual text, not images. Tagged text must use Unicode mapping so assistive tech can read it accurately.

Security and attachments

Do not apply security settings that block text copying or the use of assistive tools. Attachments need their own accessibility checks and must be described in the main PDF if essential.

How to test and validate PDFs

Combine automatic checks with manual testing. Automated tools find many problems but cannot assess context or writing clarity.

Automated tools (first pass)

  • PDF Accessibility Checker (PAC)
  • Adobe Acrobat Pro Accessibility Checker
  • Commercial validators such as CommonLook

Manual checks (must do)

  • Keyboard only navigation. Tab through links and form fields.
  • Use a screen reader: NVDA on Windows, VoiceOver on macOS or iOS. Listen for heading structure, alt text and reading order.
  • Inspect the tag tree and reading order in your PDF tool.
  • Check language tagging and document properties.

Step-by-step remediation workflow

Follow this sequence when fixing a PDF. It reduces rework and speeds validation.

  1. Run an automated report to list issues.
  2. Confirm reading order and tag tree. Fix or add tags before changing content layout.
  3. Add alternative text for images and mark decorative images as artifacts.
  4. Correct tables: set header cells and remove layout tables.
  5. Label form fields and provide clear field instructions and error messages.
  6. Declare document language and set Title metadata.
  7. Verify colour contrast for text and graphics that convey information.
  8. Re-run automated checks, then perform manual screen reader tests and keyboard tests.
  9. Create an accessibility statement or report documenting remaining issues and work completed.

Decision framework: remediate, recreate or give an HTML alternative

Not all PDFs are worth full remediation. Use this simple framework.

  • Remediate when the document is short, updated often or legally required to be accessible.
  • Recreate in the source application when tagging is deeply broken or layout is too complex for reliable tagging.
  • Provide a clean HTML version when time or tools are limited and the content needs rapid access.

Document your choice and publish an accessibility statement that points to the accessible alternative.

Common mistakes and how to avoid them

  • Saving by “printing to PDF”. This removes tags. Instead save or export with accessibility tags enabled.
  • Missing or incorrect alt text. Review images in context and write meaningful alt text or mark as decorative.
  • Using images of text. Replace with selectable, accessible text or ensure correct reading order and tags.
  • Unlabelled form controls. Use labels and tooltips that assistive tech can read.
  • Locked PDFs. Remove restrictions that block copying or reading by assistive technology.

Testing checklist (quick)

  • Is the document tagged?
  • Is there a clear heading structure?
  • Are images given alt text or marked decorative?
  • Do tables have header cells and scope?
  • Are form controls labelled?
  • Is the document language set and Title populated?
  • Does text meet WCAG contrast ratios?
  • Are security settings allowing assistive tools?

In the UK, public sector organisations follow accessibility regulations that expect WCAG conformance for web content and documents. Also consider duties under the Equality Act 2010. Check official government guidance for exact legal steps your organisation must take.

Tools and resources to learn more

  • PDF Accessibility Checker (PAC) for automated PDF/UA checks
  • Adobe Acrobat Pro Accessibility tools for tagging, reading order and form labeling
  • Screen readers: NVDA, VoiceOver and JAWS for manual testing
  • Commercial validators such as CommonLook for enterprise workflows

Final practical tips

  • Start accessibility at source. Author in Word or InDesign with styles and export using tagged PDF settings.
  • Keep layout simple when possible. Complex multi-column layouts often need more remediation.
  • Include an accessible HTML equivalent if a faithful accessible PDF is not feasible.
  • Document your testing and remediation steps. That record helps legal compliance and future updates.

Following these PDF Accessibility Guidelines will make documents usable by more readers and reduce legal and usability risks. Use automated tools for speed, and always confirm fixes with manual testing and a screen reader.