3 ms·
Increasingly I think the screenreader/ARIA proposition of navigating a (linearized ordering of) elements on a 2D page is fundamentally limiting for blind users.
by idreyn 4y ago
Increasingly I think the screenreader/ARIA proposition of navigating a (linearized ordering of) elements on a 2D page is fundamentally limiting for blind users. The web needs a more robust model of application state from which text, audio, and GUI representations can be derived. Our applications clearly structure "objects" and their "methods" under the hood, and it should be possible to present these more directly to users in whatever format makes sense to them.
- CursedUrn 4y agoThat would require some regulation, since commercial web design deliberately obfuscates the underlying structure.
- edflsafoiewq 4y agoIs that not the DOM?
- Eduard 4y agoMaybe I don't get what you want to express, but screen readers allow for alternative presentations of an HTML document, allowing for alternative modes of content discovery, e.g. hierarchical outlines of headlines and "landmarks". Several ARIA attributes further allow for communicating the current application state, e.g. whether content has changed (aria-live), a button is in a pressed state (aria-pressed), or a menu is opened (aria-expanded).
- extra88 4y agoIt has to be linearized because hearing, and time itself, are one-dimensional. Screen readers can represent nesting of content, going into one element and coming back out, Apple's VoiceOver in particular uses this concept. It may be conceptually helpful in some instances or to some people but often it just makes things more cumbersome to navigate.
- spacebanana7 4y agoI agree. For visually impaired users, HTML/sceenreaders are simply wasteful layers between them and the core behaviour/data of an application. In an ideal world, we could have entirely different clients that focus on audio-touch interfaces like a some sort of keyboard driven Alexa skill.