3 ms·
The site the post mentions for the original code (https://reactive.network/hackathon https://reactive.network/hackathon) is an accessibility nightmare.
by gnutrino 2y ago
The site the post mentions for the original code (https://reactive.network/hackathon https://reactive.network/hackathon) is an accessibility nightmare.
- lelandfe 2y agoThe garbled text is included in the tree as relevant, pronounceable, and constantly changing text. Here's Chrome's accessibility tree: https://imgur.com/a/V1589Jr https://imgur.com/a/V1589Jr (I'd love if a screen reader user could upload some audio of how awful this sounds, by the by) Please use `aria-hidden="true"` for stuff like this, it just removes the element from the accessibility tree. I've also emailed Reactive a link to this thread. Here is a decent intro to ARIA things: https://www.smashingmagazine.com/2022/09/wai-aria-guide/ https://www.smashingmagazine.com/2022/09/wai-aria-guide/
- phatskat 2y agoBig props for ARIA attributes - they’re so crucial for differently abled and impaired users. I’ve been combing through our project’s components lately to bring them up to design spec and have been taking a look at our accessibility - it’s so important and so easily missable for most engineers.