- From: Vincent Hardy <vhardy@adobe.com>
- Date: Fri, 18 May 2012 08:05:54 -0700
- To: Dirk Schulze <dschulze@adobe.com>
- CC: Cameron McCormack <cam@mcc.id.au>, "public-fx@w3.org" <public-fx@w3.org>
Hello, Is there a way to keep the work Cameron has done and address the accessibility concerns Dirk raises? -v On May 18, 2012, at 3:43 AM, Dirk Schulze wrote: > > On May 18, 2012, at 12:49 PM, Cameron McCormack wrote: > >> Without even having noticed this thread (Dirk just pointed me to it), I >> added MathML supported by MathJax to the SVG 2 spec earlier today. It >> is currently referencing the CDN copy of the library (although the >> stable version, not the "latest" link). It works pretty well -- I've >> currently got it using the SVG rendering mode, since it looks nicer in >> than the HTML+CSS, IMO at least. >> >> I replaced one <pre>-formatted equation here: >> >> https://svgwg.org/svg2-draft/painting.html#StrokeMiterlimitProperty >> >> Anyway, I'd love to keep using it in the spec. I'd be fine with adding >> a local copy of the library to the svg2 repo if necessary. > (Previously posted on public-svg mailing list) > > I think it is to early to do this. For browsers that do not support MathML, the complete MathML code gets replaced by HTML or SVG as far as I can tell. Therefore it is no longer accessible by users of screen readers. That itself is in conflict with the idea of MathML and doesn't help at all. The semantics get lost completely. Not all people with the need of screen readers use Internet Explorer and the Math plugin. And there are still browsers like Chrome that don't support MathML. This becomes more problematic once we see laptops with ChromeOS and ChromeVOX. Therefore we should think about it twice. For the meantime I would like to see it removed from SVG 2 again untill we have a decision in the W3C with other WGs, including the MathML WG. > > Greetings, > Dirk
Received on Friday, 18 May 2012 15:08:35 UTC