4 ms·
If the screen reader were at fault, then explicitly specifying the implicit role (something that should be a no-op) would not fix the problem. It's the responsi
by wizzwizz4 1y ago
If the screen reader were at fault, then explicitly specifying the implicit role (something that should be a no-op) would not fix the problem. It's the responsibility of web browsers to implement and expose implicit ARIA roles (see https://www.w3.org/TR/html-aam-1.0/#mapping-html-to-accessibility-apis https://www.w3.org/TR/html-aam-1.0/#mapping-html-to-accessib...). Screen readers do not (in general) speak HTML, just like computer monitors do not (in general) speak CSS.
- cluckindan 1y agoIf that were true, no screen readers would work, which is not the case.
- wizzwizz4 1y agoHave you ever used a screen reader? A lot of their failure modes are exactly as you'd expect from the model I've described: look at, for example, the differences in how definition lists are exposed to Windows Narrator between Firefox, Chrome, Edge, and Edge-in-IE-mode.
- cluckindan 1y agoYou’re right, some screen readers work better with specific browsers. The article doesn’t mention anything about that, though.