Workflow 8 min read 15 October 2026

PDF in Government: Open Standards, Accessibility Mandates, and Long-Term Archiving

Government agencies at every level produce and archive vast quantities of PDF documents. This guide covers the specific requirements that apply to government PDFs — open standards mandates, accessibility legislation, long-term archiving under PDF/A, e-signature laws, and the technical policies of key bodies including NARA, the EU, and national archives.

Government agencies — from national ministries to local councils — are among the largest producers and consumers of PDF documents in the world. Legislation, regulations, planning applications, tax forms, procurement contracts, public consultations, and court filings are all PDF-intensive. But government PDF is subject to a uniquely dense web of requirements: open standards mandates that prevent vendor lock-in, accessibility laws requiring documents to be usable by citizens with disabilities, records management legislation that demands multi-decade archiving, and e-signature frameworks that give digital approvals legal force. This guide maps the technical landscape for government PDF, covering the major policies and technical standards that apply in key jurisdictions, with practical guidance on how to implement them.

Open standards mandates: why governments require PDF

Governments have adopted PDF as the standard for document exchange and publication primarily because it is an ISO-standardised open format. ISO 32000-1 (2008) and ISO 32000-2 (2017) are publicly available specifications with royalty-free patent licences — any organisation can implement PDF without proprietary licensing. Key open standards frameworks that reference PDF: - **UK Cabinet Office**: The Government Service Design Manual and the Technology Code of Practice require government services to use open standards. PDF (ISO 32000) is on the UK government's list of approved document formats for publishing. See the GOV.UK open standards guidance. - **EU eGovernment Action Plan**: The European Interoperability Framework (EIF) recommends open standards for digital public services. PDF/A is specifically referenced as the archiving format for digital public records. - **US Federal**: NARA's records management guidance specifies PDF/A for permanent electronic records. The OMB (Office of Management and Budget) has issued guidance requiring text-searchable PDFs for government publications. - **Germany (DOMEA/XDOMEA)**: Germany's federal electronic records standard (XDOMEA) explicitly references PDF/A-2 as the target format for archived administrative records.

Accessibility legislation and PDF/UA

Accessibility of government digital documents is a legal requirement in most developed jurisdictions. Citizens with visual, motor, or cognitive disabilities must be able to access government forms, notices, and publications. **EU Web Accessibility Directive (2016/2102/EU)**: Requires all public sector bodies in EU member states to make their digital content accessible, including PDFs, conforming to WCAG 2.1 Level AA. Enforcement began in 2019 for public sector websites and 2020 for mobile applications. PDFs that are not tagged and accessible are non-compliant. **UK Accessibility Regulations 2018**: Implements the EU Directive in UK law (retained post-Brexit with equivalent requirements). Public sector bodies must publish accessibility statements and make all PDFs accessible. Non-compliant PDFs must either be remediated or an accessible alternative provided. **US Section 508 (Rehabilitation Act)**: Federal agencies must ensure all electronic content — including PDFs — meets WCAG 2.0 Level AA. The 2018 Section 508 refresh specifically references PDF/UA (ISO 14289-1) as the PDF accessibility standard. See the PDF accessibility audit guide for the technical audit workflow. **Australia WCAG 2.0**: The Digital Service Standard and Web Accessibility National Transition Strategy require government PDFs to meet WCAG 2.0 AA.

Long-term archiving: PDF/A in national records management

Government records are retained for years, decades, or permanently. A PDF created today must be reliably renderable in 2050 — which means it cannot rely on external fonts, colour profiles, or multimedia that may not be available in the future. PDF/A is the ISO archiving standard designed for exactly this requirement. **NARA (US National Archives)**: Bulletin 2014-04 requires that permanent electronic records transferred to NARA conform to PDF/A-1 or PDF/A-2. NARA also maintains the ERA (Electronic Records Archive) platform which validates PDF/A conformance at ingest. **The National Archives (UK)**: TNA's digital preservation guidance references PDF/A-1b and PDF/A-2b as accepted formats for long-term preservation. Records transferred under the Public Records Act should conform to these standards. **Nationaal Archief (Netherlands)**: One of the earliest national archives to mandate PDF/A — the Dutch government's DUTO (Duurzame Toegankelijkheid Uitvoeringsorganisatie) framework has required PDF/A for electronic government records since the early 2010s. **Bundesarchiv (Germany)**: The German Federal Archives' KOST (Koordinationsstelle für die dauerhafte Archivierung elektronischer Unterlagen) guidance mandates PDF/A-2 for digital government records. The recommended conformance level for new government documents is PDF/A-2a (for fully accessible tagged documents) or PDF/A-2b (for basic visual archiving where full tagging is not yet achievable).

E-signatures in government: eIDAS, ESIGN, and legal force

Government processes increasingly require legally binding digital signatures — planning approvals, contract execution, regulatory submissions, and court filings. The legal frameworks governing electronic signatures determine what technical requirements PDF digital signatures must meet. **EU eIDAS Regulation (910/2014)**: Defines three signature levels: Simple Electronic Signature (SES), Advanced Electronic Signature (AdES), and Qualified Electronic Signature (QES). For most government transactions, AdES (specifically PAdES — PDF Advanced Electronic Signature, ETSI EN 319 100 series) is the minimum standard. QES, which requires a Qualified Trust Service Provider (QTSP) certificate, has the legal equivalent of a handwritten signature under EU law. **US ESIGN Act and UETA**: Federal and state law gives electronic signatures the same legal effect as handwritten signatures. For PDF digital signatures in U.S. government contracts, the PAdES and PDF digital signature standards satisfy ESIGN requirements when combined with appropriate identity verification. **Long-Term Validation (LTV)**: Government records signed today must be verifiable in 20–75 years. LTV, which embeds certificate revocation data at signing time, is essential for long-lived government digital signatures. Without LTV, a signature may become unverifiable when the issuing CA's OCSP service goes offline.

Government-specific PDF workflows

**Freedom of Information (FOI) / Subject Access Requests**: Most FOI responses are delivered as PDFs. Before release, sensitive information must be permanently redacted (see the PDF redaction guide) and metadata stripped (see the metadata guide) to prevent inadvertent disclosure of exempt information through hidden document data. **Planning applications**: Local authorities receive planning applications as PDFs and publish them online. PDFs must be text-searchable (not scanned images) and accessible. Page sizes must match the submitted drawings. Some local planning authorities have specific PDF version and file size requirements. **Tax and benefits forms**: HMRC (UK), IRS (US), and equivalent bodies publish AcroForm PDF forms for tax returns and benefit claims. These must be accessible, must function in non-Acrobat readers (important for citizens who don't have Acrobat installed), and must be available in multiple languages with correctly encoded character sets (see PDF encoding). **Court e-filing**: Federal and state courts require PDF filings via electronic systems (CM/ECF in the US, CE File in England and Wales). Requirements include text-searchable PDFs, maximum file sizes, and in some courts, PDF/A conformance for permanent record submissions.

Government PDF is not simply enterprise PDF with extra requirements — it is a distinct domain shaped by democratic accountability, long-term preservation obligations, legal force requirements, and the need to serve every citizen regardless of ability or technology access. Agencies that invest in accessible, archiving-conformant, digitally-signed PDF workflows reduce compliance risk, improve citizen services, and build records that will remain usable for generations. Start with an annotation-based review workflow for internal documents, and ensure all citizen-facing publications pass a PAC accessibility check before publication.

Frequently asked questions

What PDF format should UK government bodies use for published documents?

UK government guidance recommends PDF/A-2b as the minimum for published documents intended for long-term availability, and PDF/UA-compliant (or PDF/A-2a) documents for accessibility-critical content. The GDS (Government Digital Service) Design System guidance recommends providing HTML as the primary format for government content, with PDF as a supplementary option for print-specific documents. All government PDFs must meet the UK Accessibility Regulations 2018 (WCAG 2.1 AA). See GOV.UK publishing accessible documents guidance.

Does the EU Web Accessibility Directive apply to PDFs?

Yes. The EU Web Accessibility Directive (2016/2102/EU) requires public sector bodies to make all digital content accessible, including PDFs published on websites or in mobile apps. PDFs must meet WCAG 2.1 Level AA, which for PDFs maps to PDF/UA (ISO 14289-1) conformance. Exemptions apply for: content published before 23 September 2018 that has not been substantially updated; archived content not needed for active administrative processes; and live audio/video content. Third-party PDFs that the public body has not created are also exempt, though links to them must include an accessibility notice.

What is PAdES and how does it relate to PDF digital signatures in Europe?

PAdES (PDF Advanced Electronic Signatures) is the ETSI standard (EN 319 100 series) that profiles PDF digital signatures for use under the EU eIDAS Regulation. PAdES defines three levels: PAdES-B (basic), PAdES-T (with timestamp), and PAdES-LTA (with long-term archival — includes LTV data). For EU government transactions requiring Advanced Electronic Signatures (AdES), PAdES-LTA is the recommended level because it supports long-term validation. Qualified Electronic Signatures (QES) require PAdES signed with a Qualified Certificate from a QTSP listed on an EU Member State trust list.

How should government FOI responses handle PDF redaction?

Government FOI responses must use true PDF redaction — permanently removing exempt content from the file's page streams — not visual covering with black boxes (which leaves the underlying text extractable). After redaction: (1) apply redactions to remove content from page streams; (2) sanitise to remove metadata, annotations, attachments, and hidden data; (3) verify by extracting text and searching for the redacted strings. Acrobat Pro's Redact tool followed by Sanitize Document provides the most reliable workflow. The PDF redaction guide covers the full process.

What is NARA's PDF/A requirement for US federal agencies?

NARA Bulletin 2014-04 requires that permanent electronic records transferred to the National Archives conform to PDF/A-1 (ISO 19005-1) or PDF/A-2 (ISO 19005-2). Temporary records can use other PDF formats. Agencies must validate PDF/A conformance before transfer, using tools like veraPDF or Acrobat Preflight. Records that cannot be converted to PDF/A without loss of essential functionality may be transferred in their native format with justification. NARA's guidance is available at archives.gov.

Try it yourself

Everything in this article can be done directly in the free PDFTheGuide editor — no account required.

Protect PDF Sign PDF Redact PDF Open editor