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.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…
As previously discussed, since completing work on PDF/UA-1, AIIM’s Committee for PDF/UA have been busy developing documents to support PDF/UA, and especially, to help developers use PDF/UA in the context of other accessibility standards.
It was for this reason that the US Committee developed “Achieving WCAG 2.0 with PDF/UA“.
If you can map PDF/UA to WCAG 2.0, why do you need PDF/UA? Why aren’t the PDF Techniques for WCAG 2.0 sufficient?
This document articulates the alignment between WCAG 2.0 and ISO 14289-1:2012 (PDF/UA), the international standard for accessible PDF technology. PDF software developers can achieve conformance with applicable WCAG 2.0 Success Criteria via implementations that follow this mapping to PDF/UA. As such, this mapping shows how to validate, in PDF file-format terms, a PDF/UA document against WCAG 2.0.
Conformance with PDF/UA does not guarantee conformance with WCAG 2.0. For some Success Criteria, especially those pertaining to media, actions, scripting, design or content considerations, authors and developers must refer directly to WCAG 2.0.
Vendors who deliver PDF files in many cases are being asked to deliver PDF files in conformance with WCAG 2.0. For many vendors this is unknown territory, and WCAG 2.0 does not provide sufficient PDF-specific technical information to achieve similar results between situations or implementations.
Since this mapping shows what’s necessary to create, process and validate, in PDF file-format and conforming reader terms, a PDF/UA conforming document and reader to meet all applicable WCAG 2.0 Success Criteria, it’s useful whether you are reading PDF/UA and the ISO 32000-1 from a WCAG 2.0 perspective, or the other way around.
Achieving WCAG 2.0 with PDF/UA is hosted on AIIM’s site.