2 ms·
Let's start with accessibility, because this is a field I am forced to be an expert in. Native "binary blobs" have access to the operating system accessibility
by ctoth 5y ago
Let's start with accessibility, because this is a field I am forced to be an expert in. Native "binary blobs" have access to the operating system accessibility APIs, and consequently any native app is a lot more likely to be accessible out of the box than something rendered to a canvas. People have spent literally decades building out APIs for the native platforms [0] [1] [2].
To think that a native app is equivalent to a canvas-rendered app is to not understand either.
[0] https://en.wikipedia.org/wiki/Microsoft_Active_Accessibility https://en.wikipedia.org/wiki/Microsoft_Active_Accessibility
[1] https://en.wikipedia.org/wiki/IAccessible2 https://en.wikipedia.org/wiki/IAccessible2
[2] https://en.wikipedia.org/wiki/Assistive_Technology_Service_Provider_Interface https://en.wikipedia.org/wiki/Assistive_Technology_Service_P...
- beaconstudios 5y agoit's viable to make accessible apps in DOM though - it's just canvas apps that can't be made accessible, and I agree with the GP that Google should not be trying to circumvent the DOM for the Docs interface.
- lhnz 5y agoCanvas apps can be made accessible. The example that Google shows in their post has accessibility features [0], although currently these need to be switched on with a keyboard shortcut (⌘+Option+Z). Pay attention to `document.getElementById('docs-aria-speakable')`. [0] https://docs.google.com/document/d/1N1XaAI4ZlCUHNWJBXJUBFjxSTlsD5XctCz6LB3Calcg/preview https://docs.google.com/document/d/1N1XaAI4ZlCUHNWJBXJUBFjxS...