Conference October 2013 📍 Washington D.C., USA

PDF Days North America 2013 — Washington D.C.: Federal Adoption of PDF/A and PDF/UA

PDF Days North America 2013 convened in Washington D.C. in October 2013, bringing together U.S. government agencies, federal contractors, and industry leaders to discuss mandatory adoption of PDF/A for federal records and the emerging PDF/UA standard for accessible government documents.

Official event page →

Key takeaways

PDF/UA-1 provided the first formal technical standard for accessible federal PDFs — filling the gap left by Section 508 standards written before PDF/UA existed.
Government Publishing Office scale made manual remediation impractical — automated tagging and workflow integration was the priority.
PDF/A-3 cleared for federal use: embedded files don't reduce archival quality of the PDF/A container — they are additional data with their own preservation considerations.
Federal plain language requirements and PDF accessibility requirements are complementary — plain language documents are more accessible and easier to tag.
Digital-first government services under the Obama Digital Government Strategy drove demand for accessible, machine-processable PDF documents.

PDF Days North America 2013 convened in Washington D.C. in October 2013, organised by the PDF Association. The conference took place at a historically significant moment for PDF standards: the year's preceding months had seen the publication of both PDF/UA-1 (ISO 14289-1:2012) and PDF/A-3 (ISO 19005-3:2012) — two standards with major implications for US government document management. Washington D.C. as a venue was particularly apt: the federal government was the largest single producer and consumer of PDF documents in the United States, and both new standards had direct implications for federal digital transformation programmes. The National Archives and Records Administration (NARA), the Government Publishing Office (GPO), federal agency IT departments, and government contractors formed a significant part of the attendance.

PDF/UA-1 arrives: accessibility for federal documents

The publication of ISO 14289-1:2012 (PDF/UA-1) gave the US federal accessibility programme its first formal technical standard for accessible PDF documents. Before PDF/UA, federal agency PDF accessibility guidance was informal and inconsistent — documents could claim to be "accessible" based on whether they passed Acrobat Pro's basic accessibility checker, which was a low bar. Section 508 and PDF/UA alignment — The existing Section 508 standards (2000 version) did not explicitly reference PDF/UA — the standard didn't exist when Section 508 was written. However, the 508 standards required accessible electronic information, and PDF/UA-1 was the authoritative technical specification for accessible PDF. Sessions at the 2013 conference reviewed how to operationalise PDF/UA requirements within existing Section 508 compliance frameworks. Government publishing workflows — The Government Publishing Office produced tens of thousands of documents annually: Federal Register publications, Congressional Record, executive agency reports, government forms. Sessions reviewed which publishing workflows could be updated to produce PDF/UA-compliant output and which required manual remediation — the GPO's scale made manual remediation impractical for the full document stream. Screen reader testing for government PDFs — JAWS (Job Access With Speech) was the dominant screen reader in federal accessibility testing contexts. Sessions reviewed government PDF documents with JAWS and identified the most common failure patterns: heading structure not reflected in tags, tables lacking header cell associations, figures without Alt text, reading order broken by decorative elements.

PDF/A-3 and federal records management

PDF/A-3 (ISO 19005-3:2012) had been published the previous year. For US federal records managers, PDF/A-3's embedded file capability opened new possibilities for hybrid document management: NARA format guidance context — NARA's guidance listed PDF/A (specifically PDF/A-1) as a preferred format for permanent electronic records. PDF/A-3's addition of arbitrary embedded files raised a question: does embedding non-PDF/A files reduce the archival quality of a PDF/A-3 document? Sessions examined NARA's position and the archival arguments. The consensus: PDF/A-3's visual-layer archiving quality is identical to PDF/A-2; the embedded files are additional data, not a replacement for the human-readable PDF. From NARA's perspective, the PDF/A-3 container remains a valid archival format — the embedded files are subject to their own format preservation considerations. This interpretation cleared the way for federal use of PDF/A-3 for hybrid document applications. Data exchange with embedded XML — Federal agency data exchanges often involve XML payloads alongside human-readable documents: grant applications with embedded structured data, regulatory filings with embedded XBRL, case files with embedded evidence metadata. PDF/A-3 with the associated files mechanism provided a standards-aligned way to bundle these. E-invoicing implications for federal procurement — The federal procurement system processed millions of invoices annually. PDF/A-3 e-invoicing (in the ZUGFeRD model, adapted for US procurement data standards) offered the potential to reduce manual invoice processing costs significantly by embedding machine-readable invoice data in the PDF supplier invoice.

Federal digital transformation and PDF strategy

The 2013 conference took place during an active period of US federal digital transformation. The Obama administration's Digital Government Strategy (May 2012) had mandated a shift to digital-first government services. PDF was both a vehicle for this transformation and a potential barrier — paper-equivalent PDFs created more accessible, lower-friction digital processes than paper, but PDFs that replicated paper forms without accessibility features created new digital barriers. Federal plain language and PDF readability — The Plain Writing Act (2010) required US federal agencies to write documents in plain language. This legislative mandate intersected with PDF accessibility: plain language documents were easier to tag correctly and more comprehensible through screen readers. Sessions reviewed the overlap between plain language and PDF accessibility best practices. Digital-first forms strategy — Government benefit application forms — FAFSA (financial aid), VA benefits, Social Security applications — were being reviewed for digital-first redesign. Sessions explored the choice between: PDF AcroForms for fillable digital forms; HTML web forms for online submission; and hybrid approaches where HTML submission produced a PDF summary record. Records management automation — Agencies with high document volumes were exploring automated PDF/A validation and conversion in their records management pipelines. Tools like Acrobat Pro's bulk processing, PDF-Tools AG's server products, and emerging open-source workflows were reviewed.

Frequently asked questions

What is the Federal PKI and how does it relate to PDF digital signatures?

The Federal Public Key Infrastructure (Federal PKI) is the US government's framework for managing digital certificates used by federal employees, contractors, and agencies. The Federal Root CA issues certificates to Agency CAs, which issue certificates to individual users via PIV (Personal Identity Verification) cards and program certificates. For PDF signing: federal employees sign documents using certificates from this hierarchy. For the signature to be trusted by both government and external recipients, the full certificate chain from the signing certificate up to the Federal Root CA must be included in the signature or accessible via distribution points. The Federal Root CA is included in many trust stores — including Adobe Acrobat's Approved Trust List (AATL) — but not universally. See PDF Certificate Signing for implementation details.

What is the Plain Writing Act and how does it affect PDF documents?

The Plain Writing Act of 2010 requires US federal executive agencies to write documents in plain language — language that is clear, concise, and well-organised, so the intended audience can understand it the first time they read or hear it. The Act applies to "covered documents" produced by agencies, including publicly distributed PDF documents. The practical implications for PDFs: plain language documents have simpler sentence structures that map well to PDF heading and paragraph tags; shorter paragraphs improve screen reader comprehension; clear heading hierarchy is both a plain language requirement and a PDF/UA tagging requirement. Agencies that implement plain language and PDF accessibility simultaneously find that the two reinforce each other — the structural clarity required for plain language is the same structural clarity required for accessible PDF tagging.

Try it in your browser

The PDF tools and standards discussed at this event are available free — no account needed.

Edit PDF Sign PDF Annotate PDF Open editor