5 ms·
Tangential question: how does accessibility work in Google Docs after they've switched to canvas? Or in Google Maps, which would be a much closer parallel?
by azangru 3y ago
Tangential question: how does accessibility work in Google Docs after they've switched to canvas?
Or in Google Maps, which would be a much closer parallel?
- TonyStr 3y agoWhile not directly related to your question, Google docs' switch to canvas broke my custom dark theme which I'd been maintaining for years, and several others were also using. This had been the main draw for me switching to Google docs in the first place and they took it away. I'd argue this is much less accessible as I can't use the product at night. Ironically, I feel like I've experienced more bugs after the switch than before
- rablackburn 3y ago> Ironically, I feel like I've experienced more bugs after the switch than before Not ironic, expected. When you do a refactor like this any good PM knows you’re creating a bunch of new bugs, and the ROI of the rewrite should consider this. Unfortunately the way it goes most of the time is “ok, what if we’re really careful not to write any bugs? Then it’s all upside!” …and now your dark theme is broken
- a13o 3y agoThere's an accessibility mode you can enable which provides keyboard and menu navigation, as well as audio cues. It's basically an alternative interface for interacting with the data layer. I actually think this is a better approach to accessibility in web applications than trying to hang all of HTML+CSS+ARIA on the DOM. Check out Accessibility Object Model (AOM) for one spec proposal around this idea.