PDF/UA (ISO 14289)

What is PDF/UA?

PDF/UA - short for PDF/Universal Accessibility - is an ISO international standard (ISO 14289) that prescribes the exact technical requirements a PDF file, a PDF processor, and assistive technology must each meet to ensure that people with disabilities can access and navigate PDF content. Unlike WCAG, which defines accessibility principles at a content level across all digital formats, PDF/UA translates those principles into precise, file-format-specific rules: mandatory tagged structure trees, logical reading order, Unicode font mapping, and machine-readable metadata. The current family includes PDF/UA-1 (ISO 14289-1:2014, built on PDF 1.7 / ISO 32000-1) and PDF/UA-2 (ISO 14289-2:2024, built on PDF 2.0 / ISO 32000-2), with the latter adding MathML support, expanded annotation requirements, and new structure element types. PDF/UA is maintained by ISO TC171 SC2 WG9 and the PDF Association's PDF/UA Technical Working Group.

Who must comply?

PDF/UA applies in practice to any organization that creates, publishes, or distributes PDF documents to the public or to employees - including government agencies, educational institutions, financial services firms, healthcare providers, retailers, and technology vendors. In the United States, federal agencies and their contractors must produce accessible PDFs under Section 508 of the Rehabilitation Act, and state and local governments must meet WCAG 2.1 Level AA under ADA Title II (deadlines vary by entity size following a DOJ Interim Final Rule issued April 2026). In the European Union, the European Accessibility Act (EAA), enforceable from June 28, 2025 for new products and services, requires businesses operating in the EU market to ensure customer-facing digital content - including PDFs such as invoices, contracts, statements, and manuals - meets accessibility standards harmonized through EN 301 549; existing services have a transition period until June 28, 2030. Privately-held organizations subject to ADA Title III, and any company with a federal nexus through contracts or grants, also face exposure when publishing inaccessible PDFs.

Key requirements

• All meaningful content must be fully tagged using a logical structure tree that correctly represents semantic roles - headings, paragraphs, lists, tables, figures, and form fields.
• Content must be presented in a logical reading order defined by the structure tree, independent of the visual layout order on the page.
• All non-text content (images, charts, diagrams) must carry descriptive alternative text; purely decorative elements must be marked as artifacts to be ignored by screen readers.
• All fonts must be embedded in the file and mapped to Unicode character codes so that text can be reliably extracted and rendered by assistive technologies.
• Document security settings must not block assistive technology from accessing text, structure, or metadata.
• The document's natural language must be declared in the document metadata (XMP), enabling screen readers to apply correct pronunciation and language rules.
• Conforming PDF processors must fully process tags and artifacts, support document navigation (bookmarks, headings), and expose document metadata to assistive technologies.

Key dates & deadlines

• April 26, 2027U.S. state and local governments serving populations of 50,000 or more must meet WCAG 2.1 Level AA under ADA Title II - covering all web and electronic document content including PDFs. This deadline was extended from April 24, 2026 by a DOJ Interim Final Rule effective April 20, 2026.
• April 26, 2028U.S. smaller public entities (populations under 50,000) and special district governments must achieve the same ADA Title II WCAG 2.1 Level AA compliance, including PDFs. This deadline was extended from April 26, 2027 by the same DOJ Interim Final Rule.
• June 28, 2025European Accessibility Act (EAA) became enforceable across all 27 EU Member States for new products and newly launched or updated services, requiring accessible digital content including customer-facing PDFs. Existing services already on the market before this date have a transition period until June 28, 2030.

Penalties & enforcement

PDF/UA itself carries no direct penalties - it is a technical standard, not a law - but inaccessible PDFs create significant legal exposure under the laws that reference or incorporate its principles. In the United States, ADA violations can result in DOJ enforcement actions with civil penalties up to $118,225 for a first violation and $236,451 for subsequent violations (2025 inflation-adjusted figures under 28 CFR Part 85), as well as private lawsuits and settlements that have reached six figures; under Section 508, federal agencies and contractors face contractual consequences including payment withholding, contract termination, and exclusion from future procurement. In the European Union, the EAA authorizes member-state regulators to impose fines; penalty amounts vary by country and can reach €100,000 or more depending on jurisdiction. California's Unruh Civil Rights Act allows $4,000 per inaccessible instance for state-law violations.

How PDF/UA relates to WCAG

PDF/UA is designed as a companion standard to WCAG and explicitly provides a means of making PDF files that conform to the W3C's Web Content Accessibility Guidelines. PDF/UA-1 (ISO 14289-1:2014) aligns with and operationalizes WCAG 2.0 principles within the PDF format, while PDF/UA-2 (ISO 14289-2:2024) states it "may be used in conjunction with WCAG 2.x" - covering WCAG 2.0, 2.1, and 2.2. Where WCAG sets outcome-based success criteria (such as "provide text alternatives" at Level A, or sufficient color contrast at Level AA), PDF/UA specifies the exact technical mechanism within the PDF file format to satisfy those criteria - for instance, requiring alt text in the /Alt dictionary entry and structure tags in a logical tree. Conformance to PDF/UA alone does not constitute full WCAG conformance, as WCAG also addresses color contrast, cognitive accessibility, and other concerns that fall outside PDF/UA's scope.

How EqualWeb helps you meet PDF/UA

EqualWeb's PDF Tools service directly addresses PDF/UA and Section 508 compliance by checking, remediating, and serving accessible PDFs - helping organizations work toward ISO 14289 conformance without rebuilding their document workflows from scratch. For organizations with large PDF libraries, EqualWeb's Managed Compliance service pairs certified IAAP/CPWA experts with systematic auditing and remediation, producing a signed Accessibility Compliance Certificate and an Accessibility Conformance Report (VPAT) that document progress toward full PDF/UA and WCAG conformance. Continuous Monitoring provides a live 0-100 compliance score and regression alerts, ensuring that newly published PDFs do not silently re-introduce barriers after remediation efforts. EqualWeb's Accessibility Testing tools - including a checker and crawler - can identify inaccessible PDFs across an entire domain, helping prioritize remediation efforts ahead of regulatory deadlines such as the April 2027 ADA Title II enforcement date for larger public entities. While no automated tool can independently resolve every accessibility issue in complex documents, EqualWeb's combination of AI-assisted remediation and certified expert oversight provides a structured, defensible path toward PDF/UA and broader digital accessibility conformance.

PDF/UA - frequently asked questions

Official sources & further reading

• ISO 14289-1:2014 - Document management applications: Electronic document file format enhancement for accessibility, Part 1 (PDF/UA-1)
• ISO 14289-2:2024 - Document management applications: Electronic document file format enhancement for accessibility, Part 2 (PDF/UA-2)
• PDF Association - ISO 14289 PDF/UA Resource Hub

Related standards & laws