The PDF Techniques Accessibility Summit’s objective is to establish a broad-based understanding of how PDF files should be tagged for accessibilty. It’s an opportunity to focus on establishing a common set of examples of accessible PDF content, and identify best-practice when tagging difficult cases.Modernizing PDF Techniques for Accessibility
The PDF Techniques Accessibility Summit will identify best-practices in tagging various cases in PDF documents. Questions to be addressed will likely include: the legal ways to tag a nested list, the correct way to caption multiple images, the appropriate way to organize content within headings.Refried PDF
My hospital emailed me a medical records release form as a PDF. They told me to print it, fill it, sign it, scan it and return it to the medical records department, in that order. In 2018? To get the form via email (i.e., electronically), yet be asked to print it? Did the last 20 years just… not mean anything! So I thought I’d be clever. I’d fill it first, THEN print it. Or better yet, never print it, but sign it anyhow, and return it along with a note making the case for improving their workflow. The story continues…Slides and video recordings of PDF Days Europe 2018
You missed the PDF Days Europe 2018? Never mind! Here you can find the slides and video recordings of all 32 stunning sessions!Using PDF/UA in accessibility checklists
PDF/UA, like PDF itself, is internally complex, but used correctly, actually makes things easier.
In a recent article I discussed using PDF as a container to organize, transport and archive collections of content. Since then I’ve had numerous discussions about this idea with members of the PDF technology and related communities. This article is an attempt to consolidate the substantial (and notably favorable) feedback. Written to stand alone, this article necessarily repeats several aspects of the previous article.
No-one owns PDF, but it’s accepted worldwide as the dominant end-state electronic document format.
The format includes rich capabilities in an ISO-standardized, vendor-independent specification.
Today, few customers leverage PDF’s richer capabilities.
That could change.
PDF is a self-contained, platform-independent page-description model with electronic document features. PDF/A, the archival subset of PDF, ensures reliable archival-grade electronic documents while accommodating virtually any arrangement of text and graphics that can be rendered.
PDF includes a set of features that, taken together, are unique to the format.
It may have been invented before the dawn of the modern web, but PDF has no real competitor in the broad and deep space it occupies in business and consumer technology. Indeed, the format’s mindshare continues to grow. Today, and with Google Docs, Office 365 and web-based technologies notwithstanding, the data shows that PDF is even more the de facto electronic document format than it was 10 years ago.
PDF supplies the lowest-common-denominator vehicle for sharing content. The format facilitates exchange between users and organizations because the format delivers equivalent – and flawless – representation on any system. Any technology that could replace PDF at this task would have to equal (at least) PDF’s enabling features.
Nonetheless, the organizations that rely on electronic documents have needs that extend beyond PDFs broadly-supported “electronic paper” features. These include:
Businesses focussed on each of these needs are already worth many billions of dollars, but today, no-one addresses all of these in an independent, consistent and interoperable (i.e., PDF-like) way. None of them yet harness the power of PDF to drive their solutions because few think of PDF beyond its core ‘electronic paper’ skill-set. And yet, PDF is undeniably familiar where it counts – with the users. The marketplace is already very comfortable with the PDF model, even if today’s vendors don’t yet to take full advantage of it. For vendors, this is not a stable situation.
It’s not a new idea per se – Adobe, Nuance, Foxit, BlueBeam and others have leveraged PDF’s embedded files feature to developed their own “package” implementations over the past 10-15 years. Although some of these are worthy efforts, they did not establish technology platforms that any user could leverage. They were not standards.
The PDFpackage future depends on providing enough structure to enable interoperability while letting the users (and user communities) define everything else their own way. Here’s what vendors need to do:
Collecting institutions will then know that email records retain necessary header information, metadata, links and attachments in a consistent structure that they may characterize, index, validate, maintain and provide access to in an efficient way.
PDFpackage profiles can be leveraged to provide trusted, predictable containers for record types that often present workflow and preservation challenges, with email and case files (associated files in arbitrary formats) as primary use-cases. Community-developed profiles can solve utilization, preservation and access challenges for specific domains.
PDF may be a relatively straightforward usage model away from a silver-bullet for archiving many types of electronic content, and useful in operational workflows as well.
There’s something about rendering
A former developer at Sun Microsystems explained their mid-1990s rendering-based “distributed ledger” methodology to me:
“This was a bit before blockchain. We’d digitally sign a document, then publish the resulting MD5 hash in the next day’s Boston Globe. As a certificate authority it left something to be desired, but it was the best way we could think of to indelibly record the signature.”
Although counter-intuitive to HTML-oriented developers, PDF’s unique feature-set make the format ideal for archiving email and “case files” – arbitrary collections of content.
Adobe’s PDF “portfolios” concept teased this idea, but was hobbled by the lack of a standardized means of leveraging PDF attachments via an interoperable set of profiles.
Why is PDF’s basis in a page-description model so important? Only a rendering can meet all handling requirements across the entire electronic document landscape. Accordingly, only an approach that considers rendering can readily accommodate existing rendered content.
One clear example of this need is the case of information security.
Modern data-protection regulations (notably the GDPR, in effect in the EU by May, 2018) include penalties so stringent that they are driving businesses towards comprehensive control over the documents they keep. Data retention regulations, on the other hand, tend to demand information retention… and if redactions are necessary, to retain information about the redaction (volume, context, purpose, etc.) as well.
If documents and email are archived using data structures that do not include a rendering, the content may be somewhat easier for familiar software to re-use, but the fundamental need to retain content safely – and in a readily human-readable fashion – becomes difficult or impossible to meet.
A PDFpackage model would leverage PDF to suit the email and case-files archiving use-case by using PDF’s features in the following way:
|Rendering||PDF/A presents a generic archival model for representing rendered electronic content.|
|Metadata||Appropriate metadata (such as that defined by PREMIS) may be included in the PDF using an XMP metadata schema identified in the PDFpackage model. Content semantics may be preserved for reuse by way of tagged PDF.|
|Attachments||PDFpackage files used for email archives would contain (and thus associate) email attachments with the baseline representation. The PDFpackage model would include requirements and encourage best-practices in using this feature, including attachment identification and processing requirements and recommendations. If appropriate to the use-case, source-files (mailboxes) may also be embedded in the PDFpackage.
For case-files, the PDFpackage includes cover materials, tables of contents, indexes or other information as appropriate to the case file type. Associated files are included as attachments, with appropriate metadata stored in the containing PDF files XMP.
|Navigation||The PDFpackage’s XMP metadata may be used to find attached documents; within these, outlines and links can provide rich navigation.|
|Data protection (contents)||Rendered page content may be authoritatively redacted using conventional (and long-standing) tools in an archival context.|
|Data protection (document)||PDF’s encryption facilities may be leveraged to protect the document in live workflow settings.|
|Authenticity||PDF’s digital signature facilities may be leveraged to verify authorship and prevent tampering.|
Leveraging PDF in this way as the universal solution for end-state content management invites vendors to consider supporting other features of modern PDF. If it’s possible to convert a PDFpackage-based email archive back into a mailbox, that same file will also be highly accessible and navigable, with excellent performance and extensibility in any reuse context.
The German ZUGFeRD specification details the use of PDF/A-3 files in a live workflow for electronic invoicing purposes. The “human readable” PDF/A-3 invoice includes, as an attachment, a “machine-readable” XML version of the invoice. The result: automated invoice processing at a low cost and 100% ready for the archive.
The potential for PDFpackage is nothing less than disruption of the current desktop, server and cloud-based paradigms for document creation, handling, finalizing and sharing. Even in the professional’s Office365-dominated world, users already use PDF as their generic platform for sharing end-state content. PDFpackages, although a dramatic upgrade, will also seem very natural. The new world can simply grow from within the old one.
Leveraging the already-accepted electronic document format as a generic packaging model for making information portable means business in:
Rendering, the process of resolving code into human-readable content, is what you do to make a sharable, accountable thing. As such, it’s rendering – not encoding – that is the truly meaningful act.
Mailbox files and proprietary source-content fit certain needs. These formats will never satisfy the universal requirement for a generic, self-contained and readily-consumable electronic record representing a given body of content at a given moment in time – its ‘rendering’. As such, PDF pages and XMP metadata, together with the other enabling features of the Portable Document Format, offer a practical and vendor-neutral, fully interoperable solution to finalizing, managing and using document-like electronic content.
If the PDFpackage concept interests you, let’s discuss it at PDF Days Europe this coming May!