Microsoft open source vision blooms with Daisy

happygeek 0 288 Views

Microsoft has launched a new add-in, designed specifically to simplify the process of creating content that is accessible for visually impaired and what it refers to as 'print disabled' individuals. The new add-in is open source, being developed in conjunction with the Digital Accessible Information System (DAISY) Consortium, and will convert Open XML based files into DAISY.XML which is part of the globally recognized DAISY standard for reading and publishing navigable multimedia content.

With groups like the World health Organization and the World Blind Union telling us that the global visually impaired population stands at more than 160 million currently, and that is without counting the additional hundreds of millions who fall into the 'print disabled' category courtesy of physical, developmental or learning disabilities, the need for something like DAISY does not really need much explaining nor a hard sell. By providing free and global access to the add-in though, Microsoft is doing its part because it helps support access information contained within literally billions of MS Office Word documents in circulation.

This news should be of particular interest to the DaniWeb development community as it allows anyone working on a project to utilize the open source code when building those new applications that are aimed at the millions of global Office users who are likely to benefit from this add-in. "Because it's part of a familiar tool, this plug-in for Microsoft Office Word significantly reduces the friction for content creators in producing accessible digital material," said Andrew Savikas, director of publishing technology at O'Reilly Media Inc. "Support for DAISY, along with the emerging ePub standard, is an easy way for software makers to build accessibility into their products, and I hope to see others follow suit."

Also of interest is the simultaneous launch of the which is also free and provides a transformation suite to support seamless conversion of DAISY XML into DAISY Digital Talking Book (DTB) format. Together these technologies provide a comprehensive solution for converting text documents into accessible formats for people with print disabilities.

"Microsoft's initiative to put 'Save as DAISY XML' in Microsoft Word is the first step to bring fully accessible content to people who are blind or who have a print disability. We know that much of the information in documents today is created with Microsoft Word; this new add-in provides an unprecedented leap forward in the worldwide effort to make information available to all," said George Kerscher, secretary general of the DAISY Consortium. While Dominique Burger of BrailleNet added "As an advocate of technologies that help blind and low-vision individuals, and as chair of an organization managing a digital library based on DAISY XML formats, I can attest that this 'Save as DAISY XML' plug-in for Microsoft Office Word is a landmark development. The ability to generate DAISY XML content from within an application used by millions of people around the world is welcome news for all who have been pushing for such a broad-reaching solution."

Dani AI

Generated

Practical follow‑up for developers (complements ): use the Word add‑in for ad‑hoc authoring and DAISY Pipeline 2 for production or batch workflows — Pipeline gives you a desktop app, a server/REST API, a CLI and a Docker image so conversions can run on CI or servers. (support.microsoft.com)

Quick checklist so Word → DAISY (or EPUB/DTB) behaves predictably:

  • Use built‑in Title/Heading styles (Heading 1, 2, …) rather than manual formatting.
  • Run Word’s Accessibility Checker while authoring and add meaningful alt text to every visual.
  • Avoid floating text boxes/complex grouped SmartArt; flatten and add alt text if needed.
  • Keep tables simple and use header rows only.
  • Remove tracked changes/comments and set document language and basic metadata (title, creator). (support.microsoft.com)

Automating and validating (example): install Pipeline 2 on the server (or use the Docker image) and call the CLI to run validator or conversion scripts. Example dp2 invocation to run the DTBook validator (adjust paths to your install):

./dp2 dtbook-validator \
  --x-input-dtbook file:/path/to/book/dtbook.xml \
  --o-result /tmp/result \
  --o-report /tmp/report.xml \
  --o-html-report /tmp/report.html

Use Pipeline templates or the REST API for batch jobs and post‑process with EPUB/DTB validators. (daisy.github.io)

QA and tooling notes: use DAISY’s Ace for automated EPUB accessibility checks and EPUBCheck for EPUB conformance; both integrate well into CI pipelines. Pipeline 2 is open source (LGPL) and the checking tools have permissive OSS licenses — good for embedding into services but confirm license terms for your product. (github.com)

Short caution: authoring discipline matters — good semantic heading structure and proper alt text usually eliminate most conversion problems. If building a service, start with small test sets, validate outputs with the validators above, then scale to larger batches.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Edit Preview