PDF Day France will be the first French-speaking event of the PDF Association, organised by our member ORPALIS. It will take place in Toulouse which is the home ground of Airbus and we are very happy that Airbus will present a case study around its usage of PDF in their document management environment!Electronic Document Conference: Call for Papers
Prospective presenters at the Electronic Document Conference 2019 are invited to submit high-quality original proposals for 25-minute presentations on subjects of interest to developers and technical product managers concerned with electronic document implementations.Have we passed ‘peak PDF’?
How do we gain insight into how users’ views of documents are shifting? Google Trends is an increasingly interesting source of high-level marketplace data. By aggregating Google’s search data over time, reporting a term’s popularity as compared with all other searches.Participating in the PDF Techniques Accessibility Summit
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.Members supporting PDF features!
The typical adoption curve for PDF technologies until approximately 2007 tended to track with that of the original PDF developer. Since then the marketplace has shifted; it’s no longer clear that Adobe drivesPDF feature support worldwide. Accordingly, we are happy to report that adoption of PDF 2.0 continues apace, with new vendors announcing their support every month.
Organizations tasked with ensuring their electronic content is accessible aren’t really interested in the technical details. They need straightforward solutions, usable workflows, reliable results and accountable systems.
Throughout the US federal government the accessibility requirement these agencies must meet is Section 508, which itself identifies WCAG 2.0 Level AA as its standard, among other requirements.
Many other governments worldwide also use WCAG 2.0, and increasingly, it’s being adopted in commercial settings engaged in improving their accessibility to disabled populations.
As an operational matter, the process of assuring that content is accessible involves substantial training, adequate software and sufficient staff-time. Anything that helps streamline this process, reduces costs, or facilitates accessibility upgrades or validation in more content, is of interest.
PDF remains indispensable. A recent analysis presented at PDF Days Europe 2018 concluded that 1 in 20 static web pages was a PDF file. But the web holds just a small fraction of documents. Trillions of PDF files exist in private collections as the embodiment of documentation, contracts, invoices, statements, policies, records, terms, maps, academic papers and so many more applications.
Due to PDF’s inherent flexibility, the testing required to account for the potential variety of content in PDF files can be substantial. PDF/UA, the ISO specification for accessible PDF, packages these requirements together and includes (according to the Matterhorn Protocol) 136 distinct tests for accessible PDF files.
This might seem daunting. Which is unfortunate, because it should be liberating.
Of the 136 tests described in the Matterhorn Protocol, 87 may be fully automated with software. Human intervention is only required to assess and correct any errors located by software.
The 47 checks that may require human judgement boil down to:
All of these tests may be performed very efficiently by software designed for PDF/UA validation. For example. it’s possible to perform most of these tests via a quick review of pages and tags.
Applying PDF/UA to accessibility-validation processes allows one to package sets of tests together, streamlining the validation process.
If agencies can learn to use the PDF/UA indicator, accessibility checklists can get a lot easier. Authors and vendors could leverage PDF/UA as part of a declaration of conformance ( VPAT in Section 508 jargon) for each document. Deliverables specifications might then be summarized as:
This approach would set clear, consumable expectations and reduce testing complexity to help drive achievement of organizational accessibility objectives.