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.
As we noted the Sophos blog has a long piece about modern-day link-farming with PDF documents. Less scrupulous marketers have discovered that Google trusts PDF documents more than HTML pages; they’ve been “poisoning Google search results” accordingly.
The notion that PDF document authors are innately pure of heart as compared to HTML pages is doubtless being re-evaluated right now, especially since PDF files are an enormous proportion of important web content, and interest in PDF continues to grow.
Apart from tweaking search algorithms so that PDF files aren’t receiving undue credit just because they are PDF files, what should Google (or other search engine developers) do about PDF? What are, for example, the benefits awaiting search-engine and other application developers that leverage high-quality PDF files?
Once the PDF specification is fully supported (it’s an ISO standard; it won’t bite!) lots of things get both easier and better.
An idea for Google and other search engine developers: to really impress people with your acumen in handling PDF documents, go beyond simply treating PDF as a page-description model, and support high-quality tagged PDF!
What might be possible if search engines were savvy to PDF’s model for semantics and logical reading order?
Although PDF is a page description format it can include all the necessary instructions to allow consuming software to make other choices. Supporting tagged PDF (ISO 32000-1:2008, 14.8, download it for free), by itself, would generate other fairly dramatic new features for browsers.
Accurate abstraction of tagged PDF’s content to vanilla HTML, much as callas’s pdfGoHTML does today (sadly, it requires Adobe Acrobat), would facilitate total flexibility in using tagged PDF on mobile devices. Apple’s iOS browser, Safari, effectively does this today on some HTML pages with “Reader View” – why not also for PDF?
Besides improved indexing for search and the ability to reliably reuse PDF content in web browsers there are many ways in which complete support for PDF technology would deliver substantial value to content management systems and end users alike:
It’s all ISO-standardized, and thus, inherently interoperable.
PDF is here to stay, and tagged PDF offers tremendous advantages for both search and re-use applications. It’s high time that search engine, browser and other application developers decided to think again about the crusty old format users have loved for over 20 years.