[Athen] RoboBraille

Sean Keegan skeegan at stanford.edu
Wed Nov 20 16:44:58 PST 2013

> When you talk about using the system as a reliable conversion tool, what is the source

> document format that you recommend content authors start with?

Right now, I am suggesting that document authors start with MS Word (as docx). From this, our SCRIBE tool can go to several different file formats and maintain the accessibility information. For example, if starting from a docx file, the system can support
conversions to:
1. full-text/full-audio DAISY and text-only DAISY
2. ePub 3, with MathML rendering
3. tagged PDF
4. braille (just the text)

The system will also support PPTX to tagged PDF and will retain the accessibility information, such as image descriptions, heading information, etc.

Most of these same features are available in the Robobraille/Sensus Access tool as well, except for the ePub 3 conversion - that will be ported over soon. I would like to be able to support other input formats, including OpenOffice and LaTeX files, but that will have to come along when we have sufficient funding.

Does this help with all formats and file types used in higher education? No, but it can address some of the more commonly used applications and I think that is a good place to start. For content authors who are dealing with more technical applications (e.g., Adobe InDesign, etc.), then that will require a different conversation to address accessible authoring techniques.

I have also put together a short "how to" tutorial that reviews basic accessible MS Word authoring techniques. Feedback is welcome: http://scribe.stanford.edu/msword.html

Take care,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20131120/815a1e3e/attachment.html>

More information about the athen-list mailing list