- From: Florian Rivoal <florian@rivoal.net>
- Date: Wed, 5 Oct 2016 08:46:21 +0900
- To: Paul Topping <pault@dessci.com>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Avneesh Singh <avneesh.sg@gmail.com>, www-style list <www-style@w3.org>, W3C Digital Publishing IG <public-digipub-ig@w3.org>, Peter Krautzberger <peter.krautzberger@mathjax.org>
> On Oct 5, 2016, at 03:36, Paul Topping <pault@dessci.com> wrote: > > Except when the person using the UA needs math accessibility. Accessibility requires that the rendering be customized for the individual. The text to be spoken for a mathematical expression is different for a student learning math than for a scientist who already understands the math. This is mostly easily achieved via client-side implementation, though it is technically feasible to implement such a feature at the server with perhaps degradation in quality and higher latency. Since the user has to navigate around the math, latency is a particular issue. For practical reasons, delivering MathML to the UA works best. Finally, this is a classic chicken-and-egg problem. Publishers want to deliver MathML but, as most are in education, they also have to serve all users and can't usually dictate the user's browser. Fair enough, but you absolutely do not need a media query to do that. A media query lets you, on the client side, decide what CSS to apply based on the capabilities of the reading device / browser. If you want to ship MathML and make it accessible to the screen readers, you can just do it. No need to query about the capabilities of the reading device. - Florian
Received on Tuesday, 4 October 2016 23:46:48 UTC