Twitter friends! I'm collecting all the evil tricks that people (inadvertently?) do to make things less #accessible. What are the top 3 things #UX or #dev folks do that feel like they're basically locking the door? Give me your worst! #a11y #inclusion
(See: HTML5 as a whole.) I keep hearing an argument that we need to adapt coding practices to screen readers – but is there another side of that coin where a pragmatic response would be for screen readers to adapt?
-
-
I should know more about this, so apologies if I’m retreading old arguments.
-
With regards to icon fonts, there's a usability/understandability concern that the web *does* adapt to fix. We can use the conventions we have to make it readable for everyone, regardless of AT: https://www.w3.org/WAI/GL/wiki/Icon_Font_with_an_On-Screen_Text_Alternative …
- Show replies
New conversation -
-
-
How would a screen reader know exactly which element should be the link? HTML is almost always written so atrociously that it would be almost impossible to do. It is the responsibility of the designer and developer to learn their craft and create inclusive structures.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.