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.
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.
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.
The PDF Association recognizes its members supporting ISO 14289 (PDF/UA)! Members offering PDF/UA services are also recognized.
See the key for more information about this table.
NOTE: All claims are made by the software publisher or service provider, and have not been vetted by the PDF Association. Please see each vendor’s “More info” link for additional information.
|Access for All||PAC 3¹|
|axaio software||MadeToTag for InDesign|
|axesPDF for Word|
|CommonLook||Clarity / Validator|
|Crawford Technologies||Accessibility Express|
|AutoTagger for Accessibility|
|Datalogics||Adobe PDF Library||P|
|kühn & weyh||M/TEXT|
|PDFlib GmbH||PDFlib 9 family|
|Solimar Systems||Accessibility Engine|
|Visual Integrity||PDF Conversion SDK||P|
|PDF Custom SDK (Object Data)||P|
¹ – PAC is developed by axes4
² – NV Access is a charitable organization maintaining open-source software
Organizations listed in italics are not members of the PDF Association but are included in this listing because they are either assistive-technology providers or developers of free open source software, with products that offer at least partial support for tagged PDF and PDF/UA.
The ability to create tagged PDF documents with semantically-appropriate structure elements from a source file or existing untagged PDF.
The ability to create PDF documents conforming to PDF/UA (ISO 14289-1:2014).
The ability to correct the logical structure tree of a tagged PDF file.
The ability to confirm PDF/UA conformance based on the Matterhorn Protocol‘s set of checks:
|P||Partial, some limited aspects of verification|
|M||All machine checks. Without human verification, machine verification is usually inadequate.|
|Complete validation, all checks (machine and human).|
The product includes an end-user-oriented interactive PDF (or PDF-alternative) viewer that uses tagged PDF to make PDF/UA files available to Assistive Technology.