Lots more small birds from the neighborhood and this time it looks like each one gets their own individual hotel room.
#birds
Remote
Matthew Hallonbacka
@mallonbacka@hachyderm.io
mastodon 4.7.3‼️ Currently not using Mastodon much while on sick leave, just checking in when I feel like it - probably back after summer.
Accessibility specialist - backgrounds in disability rights and software engineering (until they collided).
Dog person, outdoors enthusiast, maker, autistic.
Posting in English, but reading and replying in Finnish and sometimes Swedish, too.
152 Followers
182 Following
3 Posts
Joined May 04, 2023
Personal Homepage:
Location:
Helsinki, 🇫🇮
Open post
Replying to
@kleisli@mastodon.social an interesting reference (examples are not perfect, but the overall idea is ok): https://yoast.com/developer-blog/why-we-dont-set-the-og-image-alt-tag/
From a quick search, it looks like Mastodon supports og:image:alt.
0
0
0
0
Open post
Replying to
@kleisli@mastodon.social the preview image is often configured independently with meta tags, and might not be on the target page at all. If the image was taken from the page, there’s no technical reason that this idea wouldn’t work.
If the target image is set with meta tags, then it’s possible to set another meta tag, og:image:alt, according to the spec (https://ogp.me/) but a lot of platforms choose not to support this for various reasons.
Finally, if the image is part of a link, the standards focus on the link (including the image) needing an accessible name which describes the purpose of the link, rather than the contents of the image (standards are about minimally not having barriers, rather than creating a perfectly identical experience). The assumption is that whenever the preview image covers is either in the title of the page (the share text) or also available on the page, if you follow the link.
So, this isn’t a bad idea, but the current situation is considered an ok compromise, too.
0
1
0
0
