20 years ago, working on my HS newspaper website (http://hilite.org ), tried to convince folks to move away from imagemaps because regular HTML would be faster. I regret many of my youthful choices is the moral of this story.https://twitter.com/slightlylate/status/985592797469130752 …
-
Show this thread
-
-
Replying to @melaniersumner @slightlylate
More accessible than unlinked screenshots! Image maps with <area>s are keyboard accessible out of the box, and fine for screenreaders so long as you give the areas labels. Main downside is not responsive (areas don't scale). Server-side image maps are another story.
2 replies 0 retweets 2 likes -
But the content in the image map wouldn't likely end up in high fidelity (labels are usually truncated versions of the image content), right?
1 reply 0 retweets 0 likes -
ZOMG; srsly? The web is *drowning in script*, making content inaccessible for hundreds of millions...and you're arguing about labels!?!!!!!
1 reply 0 retweets 0 likes -
Slow up- no one is arguing.
1 reply 0 retweets 3 likes -
Yeah, sorry, that wasn't a proportional response. The way our current crop of tools lets down sooooooo many users gets the better of me.
1 reply 0 retweets 2 likes -
I totally feel your pain. Trying to make this better in EmberJS at least- we have some super useful A11y-related things in active development.
1 reply 0 retweets 2 likes -
The single most important contribution to accessibility any framework team can make today (in the sense of "users can access this content at all") is to simply send and run less script. We are collectively breaking the contract that tapping a link is a reasonable thing to do.
2 replies 0 retweets 4 likes -
Replying to @slightlylate @melaniersumner and
This matters (a bit) less on desktop, so documenting that a framework or tool is not appropriate for mobile development is also a huge help. Steers developers towards appropriate options.
1 reply 0 retweets 0 likes
Surfacing how broken the ecosystem is to developers is hard, tho. Lots of folks picking/choosing metrics. I want so much for us to get past speed to be able to address all the other a11y concerns.
-
-
Replying to @slightlylate @melaniersumner and
I keep thinking about this: https://www.webbloatscore.com/ We should make Lighthouse generate this number as a gut-check. /cc
@ebidel@paul_irish1 reply 0 retweets 3 likes -
Replying to @slightlylate
Tangential: When working on that PWA talk, I was slightly depressed to realize that I got a Lighthouse checkmark for "there is any content at all without JS". Kind of a low bar. I was thinking there should be another check for ">80% of the plain text content is the same w/o JS".
2 replies 0 retweets 1 like - 8 more replies
New conversation -
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.