The PDF format itself is standardized as ISO 32000, but several stricter PDF profiles exist for specific use cases. The most important are PDF/A for archiving, PDF/X for print production and PDF/UA for accessibility.
PDF/A — long-term preservation
PDF/A (ISO 19005) is designed for documents that must remain reproducible years or decades later. It restricts features that depend on external resources or future software behaviour: fonts are embedded, color must be defined predictably, metadata is required, and encryption is not allowed.
Modern variants such as PDF/A-3 and PDF/A-4 can also carry embedded files. This is why PDF/A-3 became important for hybrid e-invoices such as Factur-X/ZUGFeRD: the human-readable PDF and structured XML can travel together in one file.
PDF/X — predictable professional printing
PDF/X (ISO 15930) targets prepress and commercial printing. Its goal is not archiving or accessibility, but predictable reproduction: required fonts, controlled color spaces, output intents and restrictions on content that could make printing ambiguous.
PDF/X is therefore mainly relevant to publishing, labels, packaging and professional print workflows rather than government accessibility rules.
PDF/UA — accessible PDF
PDF/UA (ISO 14289) defines requirements for PDFs that can be interpreted correctly by assistive technologies.
A compliant document needs much more than visible text: semantic tags, logical reading order, headings, lists and tables, alternative text for meaningful images, language information and reliable text/Unicode mapping. PDF/UA-2, published in 2024, is based on PDF 2.0.
Why does this matter for government systems?
In the EU, the Web Accessibility Directive requires public-sector websites and mobile applications to be accessible, with EN 301 549 providing the harmonised technical framework. The European Accessibility Act has applied since 28 June 2025 to defined products and services including banking, e-commerce, transport and e-books. These rules do not simply say “use PDF/UA”, but accessible electronic documents are part of the compliance problem.
In the US, Section 508 requires federal electronic documents, including PDFs, to meet accessibility requirements based on WCAG 2.0 Level A/AA. ADA Title II also applies WCAG 2.1 AA to state and local government web content, including documents, with current compliance dates extending into 2027 and 2028.
For preservation, the US National Archives (NARA) explicitly supports PDF/A for permanent electronic records, while the Library of Congress lists PDF/A and PDF/UA among its preferred page-layout formats for textual works.
Where PLslash fits
PLslash is building standards-aware PDF processing directly inside Oracle PL/SQL. PDF/A-3B is already central to the PL/FACTUR / Factur-X workflow, including embedded XML. The new PDF stack is designed around the same building blocks required for standards compliance: embedded Unicode fonts, ICC/output intents, XMP metadata and associated files.
Tagged PDF provides the structural foundation for upcoming PDF/UA-oriented output. PDF/X can build on much of the same low-level font, color-management and validation infrastructure.
Top comments (0)