Accessibility for Trade Book Publishers

The venerable world of trade books has had accessibility options since the early 19th Century invention of Braille. However, only in the digital age has it been possible to make all books accessible to the visually impaired.

Guest blog by John Parsons

In the 1820s, Charles Barbier and Louis Braille adapted a Napoleonic military code to meet the reading needs of the blind. Today’s familiar system of raised dot characters substitutes touch for vision, and is used widely for signage and of course books and other written material. By the 20th Century, Braille was supplemented with large print books and records. For popular books these tools became synonymous with trade book publishers’ efforts to connect with visually impaired readers.

However, these tools—particularly Braille—has significant drawbacks. Before the advent of digital workflows, producing a Braille or even a large print book involved a separate design and manufacturing process, not to mention subsequent supply chain and distribution issues. But that has changed with the digital publishing revolution.

All Books Are “Born Digital”

With notable exceptions, trade books published since the 1980s started out as digital files on a personal computer. Word processors captured not only the author’s keystrokes but, increasingly, their formatting choices. (In the typewriter era, unless you count backspacing and typing the underline key, italics and boldface were the province of the typographer.)

On the PC, creating a larger size headline or subhead, or a distinct caption, evolved from a manual step in WordStar or MacWrite to a global stylesheet formatting command. When these word processing files made their way to a desktop publishing program, all the 12-point body copy for a regular book could become 18-point type for a large print version—at a single command.

Other benefits of digital-first content included a relatively easy conversion from Roman text characters to Braille, although that did not solve the actual book manufacturing process.

What really made the digital revolution a boon to accessibility was the rise of HTML—and its publishing offspring, eBooks. Web or EPUB text content can be re-sized or fed into screen readers for the visually impaired, but that’s only the start. It can also contain standardized metadata that a publishing workflow can use to create more accessible versions of the book.

Workflow Challenges

Trade books tend to be straightforward when it comes to accessibility challenges, but there are caveats that publishers and their service providers must address. The simplest of course is a book that is almost entirely text, with no illustrations, sidebars, or other visual elements. In those cases, the stylesheet formatting done by the author and/or publisher can be used to create accessibility-related tags for elements like headlines and subheads, as well as manage the correct reading order for Section 508 compliance.

Where things start to get tricky is when a book includes illustrations, or even special typographic elements like footnotes. To be accessible, the former must include descriptive alt text, which is usually best provided by an author, illustrator, or subject matter expert. Increasingly, just as writers became accustomed to adding their own typographic formatting, they may also include formatted captions containing this valuable, alt text-friendly information.

For other visual elements, service providers must fill in the accessibility gaps that authors cannot easily provide. This may include a certain amount of redesign, such as placement of footnotes at the end, to ensure continuity of reading, and defining the logical flow of content and reading order for page elements like sidebars. Service providers also add semantic structuring, alt text image descriptions not included by the author, and simplification of complex elements like tables.

It’s All About Format

Book publishers are already well ahead of the curve when it comes to accessibility. As mentioned in a previous blog, the page-centric PDF format is problematic. Fortunately, except for print workflows, trade publishers do not use it for their end product. In most cases, books are also produced in EPUB format, which is a derivative of HTML. These formats are accessible by default, although they need to be enhanced to meet the requirements of WCAG 2.0 standards. The gap is small, however, and can be easily bridged by focusing on design, content structuring, and web hosting.

Book reading for the visually impaired is no longer restricted to the popular titles, and compensatory technology of past centuries. With the advent of digital publishing, and the workflows that support and enhance it, accessibility for all books is an achievable goal.