- From: Neil Soiffer <soiffer@alum.mit.edu>
- Date: Sun, 16 May 2021 22:51:33 -0700
- To: Paul Libbrecht <paul@hoplahup.net>
- Cc: Deyan Ginev <deyan.ginev@gmail.com>, public-mathml4@w3.org
- Message-ID: <CAESRWkANZgXzLhO+C4zskwJVskWciKKBeCOQcRR5sCm17p3FyQ@mail.gmail.com>
I just tried their sample page with NVDA -- 0 accessibility. In fairness though, you normally have to go to the tools menu to turn on accessibility and the sample page lacks any menus, so maybe it is not fair to talk about accessibility yet. From a MathML point of view, they never supported MathML and the (soon to be retired) Google Doc's use of the DOM was just span soup, so pretty useless for most things outside of MathML also. My understanding is there was a ton of JS that drove a google doc. Neil On Sat, May 15, 2021 at 8:45 AM Paul Libbrecht <paul@hoplahup.net> wrote: > Wow, this seems like a very effective way to better control what is > copied from! That’s rather scary. > > paul > > On 15 May 2021, at 14:47, Deyan Ginev wrote: > > > Dear all, > > > > My Saturday reading brought news of a rather startling planned > > development in Google Docs. They appear to be well on their way to > > migrating away from using the DOM in its entirety, and becoming a > > Canvas application, as announced here: > > > > > https://workspaceupdates.googleblog.com/2021/05/Google-Docs-Canvas-Based-Rendering-Update.html > > > > There's a lot to be said and reacted to here, also from a MathML > > integration perspective. > > > > But the easiest reaction is that such a change may prove quite > > turbulent to minute-taking with enhanced accessibility features. And > > if we wanted to play things safe, we may want to rely on a more > > conservative solution that isn't planning a change to Canvas any time > > soon. > > > > Greetings, > > Deyan > >
Received on Monday, 17 May 2021 05:52:03 UTC