- From: Neil Soiffer <soiffer@alum.mit.edu>
- Date: Tue, 10 Dec 2019 16:04:01 -0800
- To: public-mathml4@w3.org
- Message-ID: <CAESRWkB+pHKqxEnvD71pokM8emwCsqbFvwUiryfHw8_iEOhFxQ@mail.gmail.com>
I tested MathJax V3 after the meeting and discovered it wasn't accessible due to the changes. I reached out to a few others to confirm my results and filed an issue with MathJax <https://github.com/mathjax/MathJax/issues/2260>. Due to my complaints and some strong feedback from some the people I reached out to, it looks like they will revert at least some common configurations. I posted this info to the Wikipedia issue you referenced. I'm really surprised they made such a big change but didn't solicit testing from people in the accessibility community. I personally guarantee that I will reach out to people to test any of the MathML implementations that come out of the work of this group once they reach a public beta stage. Neil On Sun, Dec 8, 2019 at 6:41 AM Frédéric Wang <fwang@igalia.com> wrote: > On 05/12/2019 06:28, Neil Soiffer wrote: > > > > Charles: MS is interested but will not say publicly they will implement > what Igalia’s MathML implementation but they are very interested in it and > hopeful this will be their solution. > > George: we do have some influence from the accessibility side of Microsoft. > > I'm really curious about these. AFAIK, the Edge team wants > interoperability and will align Edge's support on whatever is in Chrome. > The rendering part is implemented in Blink, so that's just a matter of > deciding whether they turn on a flag anyway. > But I'm wondering if you were talking about the accessibility part > instead, which might indeed require some platform-specific (UI Automation) > work from the Edge team. Microsoft never commented on the public blink-dev > thread where a11y was mentioned, so I would be interested if you can share > more info or put me in touch with relevant contacts at Microsoft. > > > Avneesh: MathJax V3 has the default off. V3 has a workaround to turn > this back on it is buried in the menu system > > This is a big concern to be, I think this will cause serious regressions > for users. One special case is Wikipedia: > https://phabricator.wikimedia.org/T237516 > > @Moritz: Can you provide an update on this? The status/plan does not seem > clear at all from the comments on the phabricator entry. > > -- > Frédéric Wang > >
Received on Wednesday, 11 December 2019 00:04:15 UTC