Re: The AAP EPUB 3 Implementation Project

Hi Richard – Welcome to the group!

I just saw your comments in my inbox, and as I’m getting ready to do a mathml webinar tomorrow, you immediately got my attention…

You say that “A big issue will be getting open source MathML readers (voice) and renders – preferably based on SVG as it is a good fit for mobile.”

Do you mean that it would be better to have MathML that is rendered as SVG than rendered natively in a browser because of the ARIA and tab index support?

The DPUB has started to collect some MathML use cases here: http://www.w3.org/dpub/IG/wiki/MathML_UC. We would definitely like to identify and record additional use cases around MathML and Accessibility. Please go ahead and send email to the group regarding any MathML use cases you wish to add. I’ve been the “de facto” keeper of the MathML use cases for the group to date. (yep. I volunteered. And sort of dragged Peter along with me, since he’s the guy who provided the initial write-ups of the 3 use cases we’ve documented to date…)

Here’s the link to register for the webinar we’re doing tomorrow if anyone’s interested:

https://event.on24.com/eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=681450&sessionid=1&key=BF15E182E16C4F1C3A04C885DF1DC212&sourcepage=register

This was originally going to be a 2 person effort between Peter Krautzberger of MathJax and myself, but we recently expanded our speaker list by one to include Sanders Kleinfeld from O’Reilly who will be presenting a case study about how O’Reilly built a toolchain API to deal with the need to put math on different retail reading devices in addition to mobile apps, the web, and in printed books.

Jean Kaplansky
Solutions Architect
Aptara, Inc.
Email: jean.kaplansky@aptaracorp.com<mailto:jean.kaplansky@aptaracorp.com>
Skype: JeanKaplansky
Mobile: 518 487 9670

[cid:5FEB827A-A5CA-4CE8-8E44-1F3F63EC4A04]

From: Richard Schwerdtfeger <schwer@us.ibm.com<mailto:schwer@us.ibm.com>>
Date: Tuesday, November 5, 2013 at 6:57 PM
To: Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>>
Cc: W3C Digital Publishing IG <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>, W3C Public Digital Publishing IG Mailing List <public-digipub-ig-comment@w3.org<mailto:public-digipub-ig-comment@w3.org>>
Subject: Re: The AAP EPUB 3 Implementation Project
Resent-From: <public-digipub-ig-comment@w3.org<mailto:public-digipub-ig-comment@w3.org>>
Resent-Date: Tuesday, November 5, 2013 at 6:57 PM


Ivan,

This is a great. Going forward we will be able to expand on ePub's accessibility capabilities. For example, SVG 2 now has ARIA and tabindex in the spec. In the future we will be able to roll this support into books. A big issue will be getting open source MathML readers (voice) and renders - preferably based on SVG as it is a good fit for mobile. Access to digital math by the blind and those with attention deficit would benefit from having this capability. In fact we recently did a study for the Department of Education. The ability for students to have Math navigable through highlighting and speech improved math comprehension by 10-15 percent across the board.


Rich


Rich Schwerdtfeger

[cid:1__=09BBF689DF1098758f9e8a93df938@us.ibm.com]Ivan Herman ---11/05/2013 05:34:09 AM---I would expect many of you (most of you?) may be familiar with this, but gor those of you who are no

From: Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>>
To: W3C Digital Publishing IG <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>, W3C Public Digital Publishing IG Mailing List <public-digipub-ig-comment@w3.org<mailto:public-digipub-ig-comment@w3.org>>
Date: 11/05/2013 05:34 AM
Subject: The AAP EPUB 3 Implementation Project

________________________________



I would expect many of you (most of you?) may be familiar with this, but gor those of you who are not:

https://nfb.org/images/nfb/documents/html/aapepub3implementation.xhtml

Lots of good guidelines point on accessibility issues, for example

Ivan

----
Ivan Herman
+31 641044153

(Written on my mobile. Excuses for brevity and frequent misspellings...)