PDF accessibility checklist

PDF accessibility is now a regulatory requirement, not a best practice. US government entities serving populations over 50,000 must meet WCAG 2.1 AA by 24 April 2026 under ADA Title II. The European Accessibility Act has been enforced since June 2025. In 2025, 8,667 ADA lawsuits were filed — 1,427 against repeat defendants.

Who this is for

  • Compliance and IT leaders in government agencies facing ADA Title II or Section 508 deadlines
  • Enterprises selling into the EU under the European Accessibility Act
  • Organizations producing high-volume PDFs (invoices, reports, statements, contracts) that need to be accessible without per-document manual remediation
  • Procurement and legal teams preparing for VPAT reviews or accessibility audits

When to use this checklist

  • Before an audit or procurement review — Run through the checklist to identify gaps before an external reviewer does
  • When evaluating document workflow vendors — Use it as a scoring rubric to compare what each vendor actually covers across tagging, conversion, validation, and viewing
  • When scoping a remediation program — Assess how much of your existing document pipeline is already compliant and where the gaps are, so you can prioritize and budget accurately
  • After a regulatory deadline change or new legislation — Reevaluate your workflow against current requirements rather than the ones you planned for a year ago
  • When onboarding a new team or process — Hand it to content, engineering, or QA teams as a shared reference for what “accessible PDF” actually means in practice

What the checklist covers

  • Source quality — What needs to be right at the authoring stage: heading structure, alt text, form labels, language metadata, and which elements must be marked as artifacts
  • Conversion and auto-tagging — What to verify when Office files or untagged PDFs are converted to PDF/UA-1 (ISO 14289): font embedding, Unicode mapping, reading order, and table structure
  • Validation and proof — How to generate audit-ready conformance reports using tools like veraPDF and PAC, and what those validators actually flag: PDF/UA identifiers, tag tree completeness, role mapping, and security settings
  • Viewing, the gap most organizations miss — A fully tagged PDF viewed through a non-compliant viewer is still inaccessible to end users. Learn what to verify in your web viewer for screen reader support, keyboard navigation, and focus order
  • Governance — How to build accessibility into the document pipeline so it’s an operational standard, not a per-document cleanup project

Next steps