4 ms·

> MathML's removal in 2013 in Chrome was a huge deal in the accessibility community That sounds ahistorical to me. Maybe removal of the (potential) promise of

> MathML's removal in 2013 in Chrome was a huge deal in the accessibility community That sounds ahistorical to me. Maybe removal of the (potential) promise of future MathML from Chrome was a huge deal? MathML support across browsers in 2013 was very spotty and buggy (there's a reason that even back then MathJax didn't prioritize MathML output), but the accessibility story was atrocious. That's actually slowly changing for the better now. Some background and planning here: https://w3c.github.io/mathml-docs/gap-analysis/ https://w3c.github.io/mathml-docs/gap-analysis/

vehemenz 4y ago
"Ahistorical" is not the word you're looking for, and even if it were, you're incorrect. Firefox and Internet Explorer (with a third party plugin) both had support for MathML reading for screen readers. The support wasn't complete, but it was good enough for high school level math in HTML textbooks. I produced several dozen of these, so I should know.
- magicalist 4y ago
  > "Ahistorical" is not the word you're looking for, and even if it were, you're incorrect. In the sense that there were certainly people lamenting the feature loss, yes, in the sense that there were large parts of the accessibility community actually using MathML and left without an alternative, no. It was largely not usable (Igalia has been fixing MathML bugs in Firefox and WebKit as well), let alone in an accessible fashion. > The support wasn't complete, but it was good enough for high school level math in HTML textbooks Maybe basic algebra, but that would be it. The document I linked gives some good basic examples even screen readers today trip over due to their inherent ambiguity (as rendered and/or as markup). Anything beyond that you currently have to annotate yourself, and you can do that just as easily without a native markup dialect.

vehemenz 4y ago

"Ahistorical" is not the word you're looking for, and even if it were, you're incorrect. Firefox and Internet Explorer (with a third party plugin) both had support for MathML reading for screen readers. The support wasn't complete, but it was good enough for high school level math in HTML textbooks. I produced several dozen of these, so I should know.

magicalist 4y ago
> "Ahistorical" is not the word you're looking for, and even if it were, you're incorrect. In the sense that there were certainly people lamenting the feature loss, yes, in the sense that there were large parts of the accessibility community actually using MathML and left without an alternative, no. It was largely not usable (Igalia has been fixing MathML bugs in Firefox and WebKit as well), let alone in an accessible fashion. > The support wasn't complete, but it was good enough for high school level math in HTML textbooks Maybe basic algebra, but that would be it. The document I linked gives some good basic examples even screen readers today trip over due to their inherent ambiguity (as rendered and/or as markup). Anything beyond that you currently have to annotate yourself, and you can do that just as easily without a native markup dialect.