Ironically, my plugin still works on Docs...but only on comments. The body text is untouchable.
I thought docs was working? At least in Mac's voice over on a laptop. There's also a menu setting to turn on more accessibility things. Not sure what that actually does though. But as of December VO could read the body text.
These efforts will, in some cases, have hacks & workarounds. The ARIA group is active building alternative imperative accessibility options for graphical systems. Every one of the folks involved ripping out the actual html web for their own developer-defined Canvas-powered stack realizes accessibility is a minimum legal requiremement. But it can still violate every norm & break every tool an accessobility user wants to use/has ever used, and tick this legal box. It can still be a nightmare hellscape for them. (It probably will be.)
The original Hixie (former editor of HTML5) manifesto/proposal even included using WebUSB to talk directly to input devices!!
Flutter/CanvasKit[1] & Ian Hixie[2] are actively pursuing/shipping this. There's a blog suggesting Jetpack Compose goes this route[3]. Seems like interest is going to keep growing. These folks say they are just doing it so developers can build "pixel perfect" apps, but oh, it also coincidentally means users have no control or say in the pixel's as they'd prefer them. Not everything written will necessarily be as Lawful Evil/impedeing-basic-human-use as what Amazon is up to here, but it'll be up to each org & each dev what pixels on the screen are interactable how.
One huge nightmare/opaque infernally damned shitworld.
[1] https://news.ycombinator.com/item?id=34527980
[2] "Towards a Moderm Web Stack" https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC... https://news.ycombinator.com/item?id=34612696
[3] https://news.ycombinator.com/item?id=34779746