DAISY, and What It Was For

01A talking book that could also be navigated

DAISY — the Digital Accessible Information System — was designed to solve that. Developed through the 1990s by a consortium of libraries for the blind, it treated a recorded book as a structured object rather than a continuous stream. The standard associated audio with a synchronized text file carrying markup: chapters, sections, page numbers, headings. A reader with a DAISY player could skip to chapter three directly, jump to a page reference, or navigate heading by heading, the way a sighted reader's eye skims a contents page or index.

The technical achievement was modest by later standards; the conceptual achievement was not. It required producers to think about a recorded book the way an editor thinks about a book — as something with architecture, not just sequence. The audio itself was encoded as digital files (initially on CD, later as downloadable packages), and the structure was expressed in XML. That pairing — human-readable content with machine-readable navigation — anticipated what ebook formats would eventually do for everyone.

DAISY 3, published as the ANSI/NISO Z39.86 standard in 2005, formalized the specification. By then the format had two modes: audio-only, for recordings without a text layer, and full text-audio, where recorded speech and the underlying text were locked together so a playback device could highlight words as they were spoken. The latter made the format useful not only for blind readers but for people with dyslexia or other reading differences.

When EPUB 3 was developed, its accessibility features drew heavily on DAISY's structural logic — an acknowledgment that the consortium had worked out the right questions a decade before mainstream publishing needed to answer them. DAISY did not disappear so much as migrate into a format most publishers already produce.