A reference on how books are made readableNot a library · no catalogue · nothing to borrow
Accessible Book Collection
In Permission

Born Accessible

If the accessible version is built during production, retrofitting becomes unnecessary. The publishing industry has known this for years and mostly not done it.

By the Register desk · Permission · 2 min read

A cluttered desk with an adjustable lamp, calculator, notebooks and papers pinned to a wall
Built in at publication, no separate permission is needed, because the accessible file is the edition.

01The Upstream Argument

Every accessible format described in this guide begins as a retrofit. A print book is published; sometime later — often much later, sometimes never — a braille transcription is commissioned, an audio recording made, a large-print edition typeset. Each conversion costs money and time and introduces new opportunities for error. The upstream argument says this is backwards: build the accessible version into the original production workflow and you spend less, finish sooner, and reach readers who otherwise wait years or go without.

The logic is sound. A publisher working in a properly structured workflow — one where headings are tagged as headings, images carry alt text, reading order is defined before any file leaves the building — produces an EPUB that already meets accessibility criteria at no meaningful extra cost. The same semantic structure that serves a screen reader on publication day is the structure a DAISY converter or large-print compositor can work from directly. Nothing needs to be reconstructed after the fact.

What this requires in practice is more demanding than it sounds. It means every editorial and design decision is made with structure in mind: styles applied consistently, tables built as real tables rather than spaced text, images described at the point of creation rather than years later when the editorial team has changed and nobody remembers what the photograph was meant to show. It means vendors and typesetters are briefed to deliver files that meet a standard, and that someone checks whether they have.

Heavy braille paper stacked beside a guillotine
Braille paper is chosen for how well it holds a dot, not for how it looks.Photo: Braille magazine example pages · Wikimedia Commons

The standard most often cited is EPUB Accessibility 1.1, itself aligned with WCAG, the Web Content Accessibility Guidelines. Publishers who meet it can assert conformance in metadata — a claim that downstream producers, library systems and readers can actually verify.

Why is it still uncommon? Partly inertia, partly the absence of a market signal strong enough to change workflows that already work for the majority of buyers. Accessibility requirements in public procurement are beginning to apply that pressure, slowly.

The core claim

From the register
ItemWhat it means
Born accessibleproducing the accessible version as part of original publishing, not as a conversion afterwards
EPUB Accessibility 1.1 — the most widely cited conformance standard for born-accessible ebooks, aligned with WCAG (Web Content Accessibility Guidelines)
WCAGWeb Content Accessibility Guidelines; the web-accessibility benchmark that EPUB accessibility criteria reference

What this requires in practice is more demanding than it sounds.

Spiral-bound large-print volumes stacked on a library trolley
Spiral binding is a legibility decision: the book has to lie flat while it is read.
A braille embosser mid-run, fanfold paper stacking in the tray
Interpoint embossing puts dots on both sides of the sheet, offset so that they never collide.

This is an independent publication about accessible book formats. It is not a library, publisher or lending service, and it does not provide access to books or documents.