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
But I wonder: At which point in both of these cases it should be the responsibility of screen readers to adapt? I feel like the web is malleable and like language — sometimes what early on feels like bad patterns get canonized as proper ones.
-
-
(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.
- Show replies
New conversation -
-
-
Information Architecture talks about "places made of information" (ref: https://rosenfeldmedia.com/books/living-in-information/ …), and those places need constructing properly. I'll toot my own horn with this: https://24ways.org/2016/front-end-developers-are-information-architects-too/ … (I really need my own site).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I wouldn't want to use any physical structure where the architect and construction company devolved the accessibility to, for example, people's hearing aids and skills with wheelchairs.
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.