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
-
-
Replying to @Nethermind
My current favourite is wrapping huge chunks of content in <a> elements so that a whole block of text, images, etc. is a link. My current record is a link with 65 words in. It's not locking the door, but it's a terrible user experience.
3 replies 0 retweets 5 likes -
-
Replying to @Nethermind @fstorr
Mind if I ask why is this bad/how does it manifest itself?
2 replies 0 retweets 0 likes -
It's about the overall ease of use in a normal (read: not testing) context. Beyond the flood of words (overly verbose stuff can be really, really tedious to listen to using a screen reader), it could actually cause some real confusion (what IS this run-on thing?).
2 replies 0 retweets 0 likes -
Replying to @Nethermind @mwichary
This differently-coded version nests the link inside the headline. With the use of CSS, it's still possible to create that "block-level-link" effect. See how http://bbc.co.uk/news codes their content.pic.twitter.com/YZOrVtvCAP
1 reply 0 retweets 1 like
Ah, I see it. Yikes. Thanks for sharing.
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.