34 ms·
By that definition, many screen reader browsers would not be considered browsers yet they enable the user to surf the web none the less.
by Etheryte 4y ago
By that definition, many screen reader browsers would not be considered browsers yet they enable the user to surf the web none the less.
- robin_reala 4y agoThat’s not how a screen reader works. It interfaces with a “normal” browser’s exposed accessibility tree, and generates speech / Braille from that.
- zinekeller 4y agoAs stated by robin_reala, that is not how screen readers work. At minimum they still definitely parse CSS as many accessibility enhancements were only introduced by CSS with no equivalent (or even a workaround) using pure HTML, and in practice will also require to have JavaScript support because when a website decides to be an obnoxious GPU-hungry Flutter application even CSS wouldn't cut it.
- Etheryte 4y agoThis is not really correct, many screen readers only support a very small subset of CSS which doesn't really match the parent's comment, that browsers must support HTML and CSS.
- zinekeller 4y ago> This is not really correct, many screen readers only support a very small subset of CSS which doesn't really match the parent's comment, that browsers must support HTML and CSS. This doesn't match with current versions of accessibility software which either connects to a browser or simply bundles an embedded version of Chromium. The ship has sailed on no-JS websites sadly, and not supporting (substantially) all of CSS modules would simply render 90% of websites inaccessible.