Metadata
Accessibility metadata is more critical to the supply chain than ever before. If you aren’t writing a11y metadata, you really should be. It is being exposed to consumers more and more in the supply chain — even on Amazon — making the writing and distribution of good accessibility metadata a competitive advantage. That said, my job here today isn’t to convince you to do it but to point you to resources that might be helpful as you figure it out.
Benetech is the driving force behind the Diagram Center. They have a brief explainer on accessibility data points. The second link is deeper. Published by the excellent APACE (Accelerating Publishing Accessibility through Collaboration in Europe) project from the EU late last year, this resource is very helpfully available in many languages — English, Bulgarian, Dutch, Finnish, Italian, and French. It is technical but lays out the argument for a11y metadata very plainly, and guides readers through the process of implementing the various flavours of data: the schema data that lives in an EPUB, ONIX, Marc, and guidelines for switching back and forth between the standards.
A resource that might come in handy for publishers who outsource ebook development is this DAISY Accessibility Metadata Viewer. This is a useful tool that transforms an ebooks metadata into something more human readable. This is a valuable tool for metadata administrators looking to choose ONIX values for a digital publication.
These next two resources are more technical. The Publishing at W3C community group, part of the group that oversees the EPUB specification, published an Accessibility Metadata Display Guide late last year after a great deal of work thinking through the details. This document is clear and technical, high-level guidance to rendering the various flavours of metadata for the consumer, covering both format metadata (EPUB and PDF), and ONIX and MARC records.
Finally, as a developer, my focus has always been the schema metadata that goes into an EPUB, but the last link is very clear, very deep guidance to how to use ONIX metadata to describe various accessibility metrics in a publication. Most of you here will be familiar with ONIX, I should think — it is the primary kind of metadata that goes into the supply chain. If it’s on a product page, it came from the ONIX feed. Editeur is the international taxonomy standards body that oversees the ONIX standard and provides guidance on its use. Their advice on ONIX is indispensable.
A lot of conversation around all of these bits and pieces of the accessible publishing puzzle all lead back to one place. Not Rome, but the DAISY Knowledge Base. It is often my first and last stop when I am trying to figure out a gnarly question. I use it every day. It is useful for EPUB, yes, but also for HTML, accessibility best practices, and general guidance. It is my favourite resource, bar none. Bookmark it and go forth and make accessible content.
QA and Testing
Okay, let’s shift gears a little to talk about QA and testing. There are two tools that every good ebook developer likely already has at the ready: EPUB Checker and Ace by DAISY. The first is a validator, the second an accessibility checker. There are many ways to use EPUB Checker; the link above is to my favourite drag-and-drop tool.
Let’s talk about Ace by DAISY for a minute. Ace is an excellent tool in your toolchest. It will scan an ebook and produce a very actionable report about any accessibility issues. It will help you sort through the various levels of WCAG (web content accessibility guidelines), the EPUB accessibility baseline spec, best practices, and it presents a clear view of the structure and navigation of a book in addition to a way to see the image descriptions. It is very practical but I want to caution you that it is just one tool. It goes about 30% of the way to checking the a11y of an ebook; the remainder must be accomplished by a human operator. Ace can’t guarantee accessibility nor can it be used to certify the accessibility of an ebook or an ebook publishing program. (Sideyeing publishers who claim their ebooks are certified by Ace!!) I see this happening now and then and want to caution against it in the strongest terms. Ace is just the start of the QA process, not the end.
The other two resources are a checklist that I use and adjusted for general use and which is available as a free download from my website. And a link to the Thorium Reading System, the desktop and mobile reading app that is developed with accessibility at its heart. It is a very good place to test your ebooks for the user experience. It has robust layout controls and a built-in screen reader. It is also in constant development which means that the developers are responding to reader’s needs in a healthy way.
PDF Accessibility
PDF accessibility is an area of the world that gets a lot of attention and development in document accessibility circles. I have three resources that I hope will be useful. Those of you who work with LaTeX, may find this guide to accessible PDF handy. The second link is to a handy-dandy downloadable checklist from the government of Canada, which has strict internal mandates for document a11y. And finally, the fine people at Vision Australia have a terrific roundup around accessible PDF.
EPUB Accessibility
Another Australian organization has a truly excellent guide, Books Without Barriers, a very thorough guide to accessible publishing. If you are new to accessible publishing, this document is a great place to start. Fair warning: it is more than 200 pages but that’s what makes it such a great and thorough resource.
The second document to link to is to a whitepaper that I had a hand in along with my friends at Westchester Publishing Services, EPUB Accessiblity with a View Toward the EAA and Ongoing Compliance. It is a rigorous look at EPUB through an accessibility lens, with useful sections about workflow planning and training resources.
And we can’t talk about ebooks without talking about the EPUB accessibility specification, which is at the 1.2 iteration. This link has detailed, technical information that is as up-to-date as possible (Dated September 12!). It is focused on discoverability — one of the most important issues in digital publishing at present. There are useful links in this doc to both the EPUB spec and the EPUB a11y 1.2 explainer which breaks down WCAG success criteria and how EPUB veers away from that slightly.
Lastly there is a link to a good explainer article on InclusivePublishing.org about recent changes to EPUB. While ebooks are mostly a mature product, there are updates, some significant when it comes to accessibility in particular.
MathML in EPUB and PDF
MathML is another thorny topic in digital publishing that is slowly getting smoothed out. I’ve got a number of links that will help you sort out your math issues — first in PDF, where there are new and very thorough best practices. The third link is to a DAISY webinar, Creating and Reading Accessible Math, from a number of years ago but which is very much still relevant and will help developers form a foundation of knowledge around MathML implementations.
For those not aware, it is now possible to create MathML natively in InDesign for export to both PDF and EPUB. The question of native math support in various places is a hot topic. The first link is to news about the exciting work happening with Microsoft tools. We hope there will be similar news from other major vendors soon.
The last two links are to guidelines for creating Math content. The Society for Industrial and Applied Mathematics has exceptionally detailed and technical guidelines for Math in EPUB. And Benetech’s Diagram Center — coming in clutch once again! — has a site with many valuable tools for learning how to code math and how to execute it.