I look forward to people sharing the auto-text from this, which I imagine will be as useful as Facebook’s.
RT @googleaccess@twitter.com
Coming later this year: Screen reader users can ask Chrome to get automatic image descriptions from Google when an image is missing alt text. Get a sneak preview now using Chrome Canary, just open the context menu! #a11y #CSUNATC19

This is my fear, of course. But if practitioners continue to educate I am hoping it will not come to this.

RT @sonniesedge@twitter.com
The year is 2020: screenreader users have to request "what does this image show?" on every. single. fucking. image, because lazy devs have gleefully abandoned alt text. twitter.com/googleaccess/statu


@aardrian next step: an attribute to trigger auto-text automatically, so devs can say "problem solved" / "not my problem anymore" / "go complain to Google/Facebook/Microsoft".

@pkra i think they will have that attribute shortly — by excluding it.

@aardrian do you mean a missing alt attribute triggering auto-text? Yeah, that makes "sense" (for some value of sense).

@aardrian sigh. I mean, it's a good idea, obviously. But the race to the bottom will be painful.

@aardrian in slightly related news: Kindle still doesn't support alt text. Only some books have "screenreader: supported" status -- which seems to mean "image alt text works with NVDA" (no headings, lists etc). I can't find any documentation on how a book can get that status either.

Le Sigh...

@pkra None of this surprises me. Which is itself sad.

@aardrian indeed. But since I'm just writing up a report after a testing project across reading systems, I just had to tell someone to feel a little less sad. 😖 Sorry for abusing the thread.

@pkra No worries. Admitting your pain is key to defeating it. Or drinking. Not sure which.

Sign in to participate in the conversation

A Mastodon instance for maths people. The kind of people who make \(\pi z^2 \times a\) jokes.

Use \( and \) for inline LaTeX, and \[ and \] for display mode.