PDF Association logo.

Facebook
Twitter
YOUTUBE
LINKEDIN
XING
About the contributor
PDF Association

Mission Statement: To promote Open Standards-based electronic document implementations using PDF technology through education, expertise and shared experience for stakeholders worldwide.
More contributions
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.

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…

Who will be first to support reading tagged PDF on mobile devices?

App store icons for PDFMobile devices are taking off worldwide. PDF technology has enormous potential in the mobile device context. The elephant in the room, however, is that although tagged PDF is an essential feature to government and large institutional PDF generators, it just isn’t yet supported on any mobile platform.

The major mobile platforms already include capable screen-readers as part of the OS. Accessibility is increasingly commodified for HTML content, but PDF gets little attention, vital though the technology is to business and governments worldwide.

Accessible PDF support on mobile devices would be a potent addition to mobile applications for digital documents, and not just in the relatively limited accessibility marketplace. There’s a world of new, and very cool, end-user products awaiting support for tagged PDF on mobile devices.

What sort of products could be developed on the basis that they worked best with PDF files that conformed to PDF/UA? There are many possibilities:

  • Dramatically superior full-text search results
  • High-quality reflow and content extraction. See callas software’s PDFgoHTML and SNAB’s VIP PDF Reader for demonstrations of such applications
  • Advanced text-to-speech conversion, including synchronized text highlighting
  • A framework for integration with voice-based annotations, digital signatures and more
  • Voice-based navigation
  • Interoperability with publishing or Product Lifecycle Management (PLM) systems
  • And coming soon, support for mapping third-party schemas such as MathML and DAISY to PDF tags

There are concrete consequences for the present-day lack of support. The government of Australia is using this fact to stand by it’s earlier decision that PDF was insufficient to meet accessibility needs. In it’s most recent update on the matter last November, it said:

…the Review also determined that the technical support in the mobile environment was insufficient to claim WCAG 2.0 conformance. Testing of Voiceover (iOS) and Talkback (Android) did not reveal the semantic information from a tagged PDF and bookmark navigation of the document was not available on mobile platforms.

As a result, PDF does not yet have the required accessibility support to fully claim WCAG 2.0 conformance, so it cannot be solely relied upon for the provision of government information except in limited circumstances.
Australian federal government, November 18, 2014

There’s been some level of support for tagged PDF in desktop screen-readers for over 10 years. It’s been over six years since publication of ISO 32000, over two years since the publication of ISO 14289 (PDF/UA). While libraries and applications for creating tagged PDF abound, full access to PDF on mobile devices remains unattained, and therefore, so do many other interesting possibilities for features, all enabled by tagged PDF.

Who will be first to deliver accessibility technology for iOS or Android that supports the accessibility model in PDF?


Tags: DAISY, MathML, PLM, WCAG 2.0, accessibility, mobile
Categories: Government, PDF/UA