And who might beat Apple and Adobe to it?
It’s pretty easy to visualize what support for tagged PDF on mobile devices might look like, because the feature already exists in iOS’s default Safari browser. Unfortunately, as of February 2015 it only works for some web (HTML) pages, and not yet PDF.
By leveraging the logical structures of tagged PDF, Reader View could work just the same way for PDF documents.
For many users, especially those who have difficulty reading PDF files in a fixed layout, extending Reader View to use tagged PDF would revolutionize their experience.
Beyond Reader View’s current functionality, which is limited to presenting the body text on HTML pages, tagged PDF could be leveraged to deliver a rich, highly navigable experience of a PDF document’s content, with text and navigation optimized to the user’s needs.
For example, software developers would be free to apply the TAdER guidelines to PDF viewers, allowing users to make adjustments in font, size, color, leading, character spacing and more.
Since it’s a PDF, the user would always be able to “drop back” to the original document’s page layout if needed.
As applications like pdfGoHTML and VIP Reader already prove, tagged PDF provides both the original document and a fully customizable extraction of that document’s contents. Where users need it most, however, is on mobile devices.
Let’s hope developers will respond to US Access Board’s adoption of PDF/UA with these sorts of innovations!