3 ms·
It's worse than that. The site isn't accessible at all. I can't get my screenreader to make heads or tails of it.
by shakna 2y ago
It's worse than that. The site isn't accessible at all. I can't get my screenreader to make heads or tails of it.
- lelandfe 2y agoThat's because all the text is inside <div> elements, so there is no hierarchy for a screenreader to latch on to: https://imgur.com/a/D78Tbgk https://imgur.com/a/D78Tbgk ...And the three nav links are made via empty, transparent <a> containers absolutely positioned over <div> text. Focusing, therefore, has nothing to read. N.b both left- and right-clicking activates these anchors, because navigation is implemented as a delegated `mousedown` event on the document.
- codethief 2y agoKeep in mind that Clay is a layouting library, the rendering as HTML, as OP mentions elsewhere, is just a demo.
- shakna 2y agoThat's true... But... The fact is, I can't read the page. Can't tell what the project is, because I can't read the page. The demo should at least have a noscript tag, to tell me why I can't read the page.
- codethief 2y agoSorry, maybe I should have phrased this differently: Of course that should be fixed! (I have spent the last half year or so fixing a11y issues on a highly frequented website, mainly thanks to the EU Accessibility Act, so I'm starting to get a feeling for how awful non-accessible websites must be.) What I meant to say was: The lack of a11y doesn't seem to be a deficiency of the library itself but rather of a hastily written demo application/renderer.
- ranger_danger 2y agoIf they're using a screen reader, there's a very good chance they cannot see your image.
- lelandfe 2y agoMy surrounding description serves as alt text! More directly: that is a depiction of the flat hierarchy of the page, which also shows empty text anchors.