Save as DAISY: Quick Tutorial for Authors and Educators

Save as DAISY: Converting Documents for Screen Readers

Creating accessible documents helps people with print disabilities access information independently. DAISY (Digital Accessible Information System) is a widely supported format designed for spoken-word navigation, making it ideal for screen reader users and anyone who benefits from audio navigation and structured text. This guide shows how to convert common document types into DAISY, best practices to prepare source files, tools to use, and quick troubleshooting tips.

What is DAISY and why use it

• Purpose: DAISY provides structured audio and text navigation (chapters, headings, page numbers) better than plain audio files.
• Users: Beneficial for people with visual impairments, dyslexia, or other print disabilities.
• Compatibility: Many screen readers, dedicated DAISY players, and mobile apps support DAISY.

Prepare your source document (recommended)

1. Use semantic structure: Apply heading styles (Heading 1, 2, 3) rather than manual formatting.
2. Add alt text: Provide concise alt text for images and meaningful descriptions for complex visuals.
3. Use lists and tables correctly: Use real list and table structures so they convert into accessible equivalents.
4. Ensure reading order: Verify logical reading order in complex layouts (columns, sidebars).
5. Remove nonessential decorative content: Keep the file focused and uncluttered for audio consumption.
6. Use accessible file formats: Start with well-structured Word (.docx) or tagged PDF when possible.

Tools for converting to DAISY

• Save as DAISY in authoring apps: Some apps and plugins offer direct “Save as DAISY” or export to DAISY XML.
• DAISY Pipeline 2: Open-source, powerful command-line/toolkit for converting from Word, EPUB, HTML, or Plain Text to DAISY 3 or DAISY XML.
• Obi (DAISY Consortium): A user-friendly tool for creating DAISY talking books from audio and marked-up text.
• Calibre with plugins: Convert documents to EPUB first, then use DAISY conversion tools if needed.
• Commercial services: Several vendors provide automated conversion with quality assurance for large volumes.

Conversion workflow (Word → DAISY example)

1. Finalize and save your .docx with semantic headings and alt text.
2. Export to EPUB (optional for some pipelines): many tools accept EPUB as input.
3. Run DAISY Pipeline 2 or Obi: select input, choose DAISY version (DAISY 3 or DTBook/DAISY XML), and configure metadata (title, author, language).
4. Review generated navigation: check table of contents, page markers, and heading levels.
5. Validate output: use DAISY validation tools or a DAISY player to test navigation and reading order.
6. Fix issues in source and repeat until output is correct.

Key metadata and settings

• Title, author, language
• Reading order and navigation granularity (e.g., by headings, pages, or sections)
• Audio synchronization: If you provide audio, ensure it’s synchronized to text (SMIL files in DAISY 3).
• Output version: DAISY 3 (widely used) vs. DAISY XML/DTBook — choose based on target players and distribution channels.

Testing with screen readers and players

• Test on at least one screen reader (NVDA, VoiceOver, JAWS) and one DAISY player or app.
• Verify: heading navigation, chapter skipping, page or section jumps, image descriptions, and bookmarks.

Troubleshooting common issues

• Navigation missing or flattened: ensure headings use built-in styles in source files.
• Images not described: add alt text or longer descriptions in the source.
• Incorrect reading order: check complex layouts and simplify or correct in source.
• Audio sync problems: verify timestamps and SMIL links; re-run conversion with corrected audio files.

Accessibility and distribution tips

• Provide multiple formats (DAISY, accessible EPUB, tagged PDF) to meet user preferences.
• Include a short accessibility summary describing navigation features and supported assistive technologies.
• Keep file sizes reasonable; split very long books into volumes if necessary.

Quick checklist before publishing

• Headings applied consistently
• Alt text for all meaningful images
• Tables and lists properly tagged
• Metadata populated (title, author, language)
• Validated DAISY output tested with screen reader/player

Converting documents to DAISY makes content navigable and usable for people who rely on audio and structured navigation. Following good source-authoring practices and using established tools will produce reliable DAISY files that work well with screen readers and dedicated players.