The 2014 conference was the first major North American PDF event following PDF/UA-1 publication. Sessions gave practitioners their first structured introduction to the standard's requirements: The tagging requirement in detail — Sessions walked through the specific tagging requirements that PDF/UA-1 imposed on document structure: all real content in a tag tree; decorative elements marked as artifacts; semantic element types (headings with hierarchy, lists with /L and /LI, tables with /Table /TR /TH /TD, figures with /Figure and /Alt). The contrast with typical "auto-tagged" PDFs — which often had reasonable structure but frequently merged text objects incorrectly and placed decorative content in the tag tree — was striking. Reading order and multi-column challenges — The reading order requirement (logical reading order reflected in tag tree order) was the most challenging requirement for complex layouts. A two-column academic paper exported from Word or LaTeX typically had content in left-to-right drawing order, not column-by-column reading order. Fixing this in Acrobat Pro was possible but time-consuming for each page. The Alt text gap — Every figure needed /Alt text. In practice, virtually no automated PDF generation workflow produced Alt text. It required either: authoring in tools that carry Alt text through to PDF export (modern Word, InDesign with alt text configured), or manual post-processing in Acrobat Pro after generation. Early adoption organisations — A handful of US government agencies and academic publishers had begun PDF/UA implementation. Sessions shared early experience: the combination of PAC 2 validation, manual remediation in Acrobat Pro, and screen reader testing was the emerging workflow. No automated end-to-end solution existed yet.

PDF/A-3 was two years old by 2014. European e-invoicing (ZUGFeRD) was the primary success story, but North American sessions examined additional use cases: Healthcare: CCD/C-CDA clinical documents — The HL7 Consolidated CDA (C-CDA) format for patient clinical documents was being evaluated for embedding in PDF/A-3 documents. A patient discharge summary PDF/A-3 with an embedded C-CDA XML file would be simultaneously: a human-readable PDF record for clinical review; a machine-readable C-CDA record for health information exchange (HIE) systems; and a PDF/A-compliant archival document. The HL7 C-CDA standard was seeing mandatory use under Meaningful Use Stage 2 in 2014, creating demand for interoperable document formats. Financial document data embedding — Annual reports, fund factsheets, and prospectuses in PDF/A-3 with embedded XBRL (eXtensible Business Reporting Language) financial data were discussed. XBRL had been mandated by the SEC for financial filings; embedding XBRL data in PDF/A-3 alongside the human-readable financial statement would simplify compliance filing workflows. Legal discovery and PDF/A — Boston's legal community was well represented. The use of PDF/A for e-discovery (EDRM workflows) — producing productions in PDF/A-1b for archival quality, combined with load file metadata — was reviewed. PDF/A's self-contained format was valued for long-term preservation of produced documents in litigation hold scenarios.

The interoperability gap between US and EU digital signature frameworks was an active topic at the 2014 conference, predating eIDAS's full effectiveness: US digital signature landscape — In the US, digital signatures for documents used in federal programmes are governed by: ESIGN (commercial), UETA (state-level commercial), NIST Digital Signature Standard (FIPS 186-4, covering RSA, DSA, ECDSA algorithms), and agency-specific requirements for government digital signatures (PIV card-based signing for federal employees). PAdES vs CAdES — European PDF signatures use PAdES (PDF Advanced Electronic Signatures, ETSI standard). US signatures often used CMS/PKCS#7 signatures directly without the PAdES profile extensions. The interoperability question: can a European verifier reliably verify a US-generated PDF signature, and vice versa? In principle yes; in practice, differences in certificate chain inclusion, timestamp format, and revocation information embedding caused verification failures in cross-border scenarios. Federal PKI and PIV cards — US federal employees and contractors increasingly used PIV (Personal Identity Verification) cards for document signing. PIV card certificates are issued by the Federal PKI hierarchy. Sessions reviewed PDF signing workflows with PIV cards and how to embed the full federal certificate chain for reliable verification.