#ImageDescriptions

1 post1 participant0 posts today

Jupiter Rowland@<a href="https://norden.social/@PalmAndNeedle" rel="nofollow noopener noreferrer" target="_blank">PalmAndNeedle</a> I know. <a href="https://hub.netzgemeinde.eu/item/db8f9353-e126-49b2-ad06-87c5e1df8d00" rel="nofollow noopener noreferrer" target="_blank">I have evidence.</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AI" rel="nofollow noopener noreferrer" target="_blank">AI</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AIVsHuman" rel="nofollow noopener noreferrer" target="_blank">AIVsHuman</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HumanVsAI" rel="nofollow noopener noreferrer" target="_blank">HumanVsAI</a>

FiXato<a href="https://toot.cat/tags/TodayILearned" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TodayILearned</a> that <a href="https://mastodon.social/@oatmeal" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@oatmeal</a> is on mastodon. Unfortunately the account doesn't provide alt text / <a href="https://toot.cat/tags/ImageDescriptions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImageDescriptions</a> for the comics :(

Jupiter Rowland@<a href="https://mastodon.social/@iFixit" rel="nofollow noopener noreferrer" target="_blank">iFixit</a> <blockquote>and it doesn't look like you can attach documents to posts</blockquote> You can't on Mastodon. I could, both here on <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> and on <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> where I post my images. But I wouldn't have to. Vanilla Mastodon has a character limit of 500. Hubzilla has a character "limit" that's so staggeringly high that nobody knows how high it is because it doesn't matter. (streams), from the same creator and the same software family as Hubzilla, has a character "limit" of over 24,000,000 which is not an arbitrary design decision but simply the size of the database field. By the way: Both are in the Fediverse, and both are federated with Mastodon, so Mastodon's "all media must have accurate and sufficiently detailed descriptions" rule applies there as well unless you don't care if thousands upon thousands of Mastodon users block you for not supplying image and media descriptions. In theory, I could publish a video of ten minutes, and in the same post, I could add a full, timestamped description that takes several hours to read. Verbatim transcript of all spoken words. Detailed description of the visuals where "detailed" means "as detailed as Mastodon loves its alt-texts" as in "800 characters of alt-text or more for a close-up of a single flower in front of a blurry background" detailed. Detailed description of all camera movements and cuts. Description of non-spoken-word noises. All timestamped, probably with over a hundred timestamps for the whole description of ten minutes of video. Now I'm wondering if that could be helpful or actually required, or if it's overkill and actually a hindrance. CC: @<a href="https://connectified.com/@masukomi" rel="nofollow noopener noreferrer" target="_blank">masukomi</a> @<a href="https://mastodon.scot/@gunchleoc" rel="nofollow noopener noreferrer" target="_blank">GunChleoc</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener noreferrer" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener noreferrer" target="_blank">MediaDescriptions</a>

FiXatoVery happy with how this northern lights photo of myself turned out. 💚<a href="https://toot.cat/tags/FiXatoFoto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FiXatoFoto</a> <a href="https://toot.cat/tags/FiXatoCreative" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FiXatoCreative</a> <a href="https://toot.cat/tags/NorthernLights" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NorthernLights</a> <a href="https://toot.cat/tags/AuroraBorealis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AuroraBorealis</a> <a href="https://toot.cat/tags/Aurora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aurora</a> <a href="https://toot.cat/tags/dailyPhoto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dailyPhoto</a> <a href="https://toot.cat/tags/photography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#photography</a> <a href="https://toot.cat/tags/FediArt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediArt</a> <a href="https://toot.cat/tags/mastoArt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastoArt</a> <a href="https://toot.cat/tags/DescribedMedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DescribedMedia</a> <a href="https://toot.cat/tags/ImageDescriptions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ImageDescriptions</a>

Jupiter Rowland@<a href="https://toot.cat/@garry" rel="nofollow noopener noreferrer" target="_blank">Garry Knight</a> @<a href="https://mstdn.social/@qurlyjoe" rel="nofollow noopener noreferrer" target="_blank">qurly(not curly)joe</a> This, by the way, is something that next to nobody in the Fediverse knows, and that many will deny and fight with all they can: Alt-text must never include exclusive information that is neither in the post text nor in the image itself. Such information must always go into the post itself. If you don't have room in the post, add it to a reply or multiple. That's because not everybody can access alt-text. Certain physical disabilities can make accessing alt-text impossible, for example, if someone can't use their hands. Money quote from way down <a href="https://hub.netzgemeinde.eu/item/4376779b-8bd1-4da9-9c38-92a7fae57abb" rel="nofollow noopener noreferrer" target="_blank">this comment thread</a>: <a href="https://hachyderm.io/@gnomicutterance" rel="nofollow noopener noreferrer" target="_blank"></a><a href="https://hachyderm.io/@gnomicutterance" rel="nofollow noopener noreferrer" target="_blank">Deborah</a> schrieb den folgenden <a href="https://hachyderm.io/@gnomicutterance/110691919197248049" rel="nofollow noopener noreferrer" target="_blank">Beitrag</a> Mon, 10 Jul 2023 23:30:45 +0200 <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">@jupiter_rowland</a> I have a disability that prevents me from seeing alt text, because on almost all platforms, seeing the alt requires having a screenreader or working hands. If you post a picture, is there info that you want somebody who CAN see the picture but DOESN’T have working hands to know? Write that in visible text. If you put that in the alt, you are explicitly excluding people like me. But you don’t have to overthink it. The description of the image itself is a simple concept. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener noreferrer" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePost" rel="nofollow noopener noreferrer" target="_blank">QuotePost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweet" rel="nofollow noopener noreferrer" target="_blank">QuoteTweet</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToot" rel="nofollow noopener noreferrer" target="_blank">QuoteToot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoost" rel="nofollow noopener noreferrer" target="_blank">QuoteBoost</a>

Jupiter Rowland@<a href="https://mstdn.ca/@DavidM_yeg" rel="nofollow noopener noreferrer" target="_blank">David Mitchell :CApride:</a> <blockquote>Mostly, just imagine you’re telling your friend over the phone about image you’re looking at and what they would need to know.</blockquote> Let's just say I'm a bit critical about that because, in my opinion, it doesn't work in the Fediverse. <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland?f=&zid=social.tchncs.de%40social.tchncs.de" rel="nofollow noopener noreferrer" target="_blank"></a><a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland?f=&zid=social.tchncs.de%40social.tchncs.de" rel="nofollow noopener noreferrer" target="_blank">Jupiter Rowland</a> schrieb den folgenden <a href="https://hub.netzgemeinde.eu/item/21735784-8443-430a-aa09-e0d9d00a40c2?f=&zid=social.tchncs.de%40social.tchncs.de" rel="nofollow noopener noreferrer" target="_blank">Beitrag</a> Fri, 04 Oct 2024 23:30:02 +0200 You can't describe images in Fediverse posts like over the phoneAllegedly, a "good" advice for image descriptions is always to describe images like you'd describe them to someone on a landline phone. Sorry, but that's non-sense. At least for anything that goes significantly beyond a real-life cat photo. If you describe an image through a phone, you describe it to one person. Usually a person whom you know, so you've at least got a rough idea on what they need described. Even more importantly, you can ask that person what they want to know about the image if you don't know. And you get a reply. If you describe an image for a public Fediverse post, you describe it to millions of Fediverse users and billions of Web users. You can't know what they all want, nor can you generalise what they all want. And you can't even ask one of them what they need described before or while describing, much less all of them. In fact, you can't ask at all. And yet, you have to cater to everyone's needs the same and throw no-one under a bus. If I see a realistic chance that someone might be interested in some detail in one of my images, I will describe it. It won't be in the shorter description in the alt-text; instead, it will be in the long description which I've always put directly into the post so far, but whose placement I'm currently reconsidering. If something is unfamiliar enough to enough people that it requires an explanation, I will explain it in the long description. Right now, only meme posts are an exception. They don't need as much of a visual description as long as I stick to the template, and a poll has revealed that people do prefer externally linked third-party explanations over my own ones blowing the character count of the post out of proportion. This is the one time that I can safely assume that I actually know what most people want. @<a href="https://a.gup.pe/u/accessibility" rel="nofollow noopener noreferrer" target="_blank">accessibility group</a> @<a href="https://a.gup.pe/u/a11y" rel="nofollow noopener noreferrer" target="_blank">a11y group</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener noreferrer" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a> CC: @<a href="https://mstdn.ca/@monstreline" rel="nofollow noopener noreferrer" target="_blank">Monstreline</a> @<a href="https://ohai.social/@i_cannot_today" rel="nofollow noopener noreferrer" target="_blank">Claire (sometimes Carla)</a> @<a href="https://mstdn.social/@qurlyjoe" rel="nofollow noopener noreferrer" target="_blank">qurly(not curly)joe</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePost" rel="nofollow noopener noreferrer" target="_blank">QuotePost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweet" rel="nofollow noopener noreferrer" target="_blank">QuoteTweet</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToot" rel="nofollow noopener noreferrer" target="_blank">QuoteToot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoost" rel="nofollow noopener noreferrer" target="_blank">QuoteBoost</a>

Jupiter Rowland@<a href="https://a.gup.pe/u/accessibility" rel="nofollow noopener noreferrer" target="_blank">accessibility group</a> @<a href="https://a.gup.pe/u/a11y" rel="nofollow noopener noreferrer" target="_blank">a11y group</a> New rant/article: <a href="https://hub.netzgemeinde.eu/item/1e63be04-d96e-412a-ab47-aff18c5f9ad8" rel="nofollow noopener noreferrer" target="_blank">I have learned a lot about describing images according to Mastodon's standards, and I want to share my knowledge, but I haven't learned enough</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener noreferrer" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a>

Jupiter Rowland@<a href="https://nerdculture.de/@annam" rel="nofollow noopener noreferrer" target="_blank">Anna Maier</a> I don't know what constitutes a "good" example in your opinion, but I've got two examples of how bad AI is at describing images with extremely obscure niche content, much less explaining them. In both cases, I had the <a href="https://llava.hliu.cc/" rel="nofollow noopener noreferrer" target="_blank">Large Language and Vision Assistant</a> describe one of my images, always a rendering from within a 3-D virtual world. And then I compared it with a description of the same image of my own. That said, I didn't compare the AI description with my short description in the alt-text. I went all the way and compared it with my long description in the post, tens of thousands of characters long, which includes extensive explanations of things that the average viewer is unlikely to be familiar with. This is what I consider the benchmark. Also, I fed the image at the resolution at which I posted it, 800x533 pixels, to the AI. But I myself didn't describe the image by looking at the image. I described it by looking around in-world. If an AI can't zoom in indefinitely and look around obstacles, and it can't, it's actually a disadvantage on the side of the AI and not an unfair advantage on my side. So without further ado, exhibit A: <a href="https://hub.netzgemeinde.eu/item/db8f9353-e126-49b2-ad06-87c5e1df8d00" rel="nofollow noopener noreferrer" target="_blank">This post</a> contains <ul><li>an image with an alt-text that I've written myself (1,064 characters, including only 382 characters of description and 681 characters of explanation where the long description can be found),</li><li>the image description that I had LLaVA generate for me (558 characters)</li><li>my own long and detailed description (25,271 characters)</li></ul>The immediate follow-up comment dissects and reviews LLaVA's description and reveals where LLaVA was too vague, where LLaVA was outright wrong and what LLaVA didn't mention although it should have. If you've got some more time, exhibit B: Technically, all this is in one thread. But for your convenience, I'll link to the individual messages. <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener noreferrer" target="_blank">Here is the start post</a> with <ul><li>an image with precisely 1,500 characters of alt-text, including 1,402 characters of visual description and 997 characters mentioning the long description in the post, all written by myself</li><li>my own long and detailed image description (60,553 characters)</li></ul> <a href="https://hub.netzgemeinde.eu/display/69317442-c4b7-4dc2-beed-38438abfc50a" rel="nofollow noopener noreferrer" target="_blank">Here is the comment with the AI description</a> (1,120 characters; I've asked for a detailed description). <a href="https://hub.netzgemeinde.eu/display/451d2f06-7746-4227-a043-76a959420c29" rel="nofollow noopener noreferrer" target="_blank">Here is the immediate follow-up comment with my review of the AI description.</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AI" rel="nofollow noopener noreferrer" target="_blank">AI</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LLaVA" rel="nofollow noopener noreferrer" target="_blank">LLaVA</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AIVsHuman" rel="nofollow noopener noreferrer" target="_blank">AIVsHuman</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HumanVsAI" rel="nofollow noopener noreferrer" target="_blank">HumanVsAI</a>

Jupiter Rowland@<a href="https://mastodon.online/@sunflowerinrain" rel="nofollow noopener noreferrer" target="_blank">sunflowerinrain</a> @<a href="https://mastodon.green/@Tarnport" rel="nofollow noopener noreferrer" target="_blank">Tarnport</a> From what I've read, a digital photograph is considered the default. So for brevity reasons, it must not be mentioned. Any other media must be mentioned, whether it's a painting, a screenshot from a social media app, a scanned analogue photograph, a flowchart, a CAD blueprint, a 3-D rendering or whatever. But an alt-text must never start with "Image of", "Picture of" or "Photo of". That's considered bad style and a waste of characters and screen-reading time. If the medium is not mentioned, digital photograph falls into its place as a default. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland@<a href="https://chaos.social/@crypticcelery" rel="nofollow noopener noreferrer" target="_blank">crypticcelery</a> There's generally too little feedback on image descriptions. There should be more praise for really good image descriptions, and there should be more constructive criticism. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a>

Jupiter Rowland@<a href="https://chaos.social/@crypticcelery" rel="nofollow noopener noreferrer" target="_blank">crypticcelery</a> I'm not quite sure if that's such a good idea. I mean, it may make trying to replace other users' alt-texts with your own ones commonplace. I mean, Mastodon in particular is escalating from going against no alt-text to going against non-descriptive alt-text to going against bad alt-text to going against not enough alt-text. The days of "better than nothing" are over. Mastodon is heading straight for going against any kinds of alt-text that isn't optimal, for any individual definition of optimal. It's dragging the rest of the Fediverse with itself by and by. And if suggesting replacement alt-texts for any alt-texts that someone personally deems less than optimal becomes the norm, you'll end up with disputes and flame wars over what's the optimal alt-text in lots of image post threads. That's because there is absolutely no consensus on what's "enough" or "optimal" alt-text, or if there's such a thing as "too much" alt-text. That's also because people who are interested in accessibility don't talk with each other, neither alt-text activists nor blind or visually-impaired people. Too many people think they have the One True Recipe for describing any possible image. What makes matters more difficult are obscure edge-cases that don't really fit into any existing scheme. Not all images are cat photos, event posters or social media screenshots. There's even less consensus on describing these edge-cases. <blockquote>On the other end: Would you be annoyed by this?</blockquote> Truth be told, it's highly unlikely in my case. If I spend hours or even days describing one single image in 900 characters in a 1,500-character-altogether alt-text and, on top of that, additionally in tens of thousands of characters of long description in the post itself (no, seriously, I do that, and I've got proof), I don't think that someone will come with two even more detailed and even more massive image descriptions and ask me to replace mine with theirs. But if someone came and tried to pressure me into replacing my 1,500-character alt-text with their 200-character alt-text and delete my tens-of-thousands-of-characters long description entirely, then I'd be annoyed. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a>

Jupiter Rowland@<a href="https://mastodon.social/@alttexthalloffame" rel="nofollow noopener noreferrer" target="_blank">Alt Text Hall of Fame</a> @<a href="https://sfba.social/@dbloom" rel="nofollow noopener noreferrer" target="_blank">David Bloom</a> Yes. Explanations, or any other information available neither in the image nor in the post text, must never ever go into the alt-text. That's because not everyone can access alt-text. And to those who can't access alt-text, any information exclusively available in alt-text is inaccessible and therefore lost. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland@<a href="https://friendica.world/profile/dandylover1" rel="nofollow noopener noreferrer" target="_blank">Georgiana Brummell</a> @<a href="https://partyon.xyz/@nat" rel="nofollow noopener noreferrer" target="_blank">Nat Oleander</a> Well, technically speaking, the long description isn't alt-text. What went into the actual alt-text of the image were 1,402 characters of visual description + 97 characters of notice that there's a long description in the post. The over 60,000 characters went into the post text body, right below the image itself. I could have put the long description into the alt-text. But it would have been a nightmare for blind or visually-impaired people because screen readers can't navigate alt-text. Also, Mastodon, Glitch, Hometown, Misskey, Calckey, Firefish, Iceshrimp, CherryPick, Sharkey, Catodon and the other Mastodon and Misskey forks chop long alt-texts from outside off at the 1,500-character mark. Mastodon would simply have deleted almost 59,000 characters from my image description on their side, had I put it into the alt-text. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland@<a href="https://friendica.world/profile/dandylover1" rel="nofollow noopener noreferrer" target="_blank">Georgiana Brummell</a> I'd say not everyone would consider almost 1,000 characters of image description in a 1,500-character alt-text accessible. And even fewer people would consider a long image description in the post itself that's tens of thousands of characters long accessible if your screen reader spends an hour or several rambling it down. My most extreme case is a post with only one image. That one image is described twice like all my halfway recent original images. The short description in the alt-text is a bit over 1,400 characters long which barely leaves any room for the note that there is also a long description in the post itself. That long description is over 60,000 characters long. I'm not kidding. It took me two full days from getting up to going to bed to research for it and write it. Now, there are a few dozen bits and pieces of text all over the image. At the resolution at which I've posted the image, two of them are ever so barely legible for sighted people. They're on a large logo on a building. Four more, two of them on that logo, too, two more on a sign on an easel, are illegible, but still visible. At least more on signs inside the building are visible, but they can't easily be identified as text. All the others are so tiny that they're invisible. It takes the long image description to even know where they are, for example, on the control panels of teleporters. And yet, they are all within the borders of the image. And I can transcribe them. I can't read them in the image, but I can go to the place shown in the image and take closer looks. Unfortunately, the rule or guideline that any and all text in an image must be transcribed verbatim does not take into consideration text that can't be read in the image, but that can be sourced and thus transcribed by whoever posts the image. No confirmation, no exception. And so I have to assume that I have to transcribe illegible text as well. And so I do transcribe them all. But there's no way for me to put all these text transcripts into the alt-text, not if I want to keep Mastodon, Misskey and their forks from chopping it off at the 1,500-character mark. I'd also have to explain where all these pieces of text are, after all. And so the text transcripts are only available in the 60,000-character monster of a long image description. It isn't really accessible to expect blind users to have their screen readers ramble and ramble and ramble for hours, just to get information that should actually belong into the alt-text which, in turn, shouldn't be longer than 200 characters. On the other hand, it doesn't really seem accessible to me if I expect people to ask me to describe things in the image for them. It rather feels sloppy, if not out-right ableist to not describe everything that someone could possibly want to know right away. The problem with my images is that they're renderings from very obscure 3-D virtual worlds. This means that nobody knows what anything in these images looks like unless they can see these images. This, in turn, means that I cannot expect anyone to know what something in my images looks like anyway. They don't. At the same time, I can't expect everyone to not care about my images. In fact, I expect the very topic of 3-D virtual worlds that actually exist to make people curious. At this point, it doesn't matter what's important in my images within the context of the post. Sighted people will go explore the new and unknown world by taking closer looks at all the big and small details in the image. But blind or visually-impaired people may be just as curious. They may want the same chance to explore this new world by experiencing what's in that one image. Denying them the same chances as sighted people is ableist. But giving them this chance requires an absolutely titanic image description. Sure, I describe lots of details which a sighted person can't possibly recognise when looking at the image, especially not at the resolution of the image as I've posted it. But I simply can't keep telling blind or visually-impaired people that certain things in the image can't be recognised due to the image resolution. It feels lazy, like weaseling out. I mean, I can see all these details. Not in the image, but where the image was made, simply by walking closer to them or moving the camera closer to them. If there are two dark objects inside a building that may or may not be plants, but that can't be identified as plants by looking at the image, why shouldn't I describe them as follows: "On the sides of the teleport panel, there are two identical açaí palms in square terracotta pots with wide rims. Like the other potted plants, these mostly dark green plants with long pointy leaves are kept at an indoor-compatible size, namely about three and a half metres or eleven and a half feet tall. Also, like the other potted plants, they are made of only four flat surfaces with partially transparent pictures of the plant on them, arranged in angles of 45 degrees to one another." If there's room for improvement in my image descriptions, I improve my future image descriptions and declare my past image descriptions outdated. In fact, the 60,000-character-long description is outdated because it's bad style to describe dimension using measures. Instead, dimensions should be described by comparing them with something everyone is familiar with like body parts. Right now, by the way, I'm upping my game at describing avatars, using rules and guidelines for describing people which I've discovered over the last few months. The last time I've described an avatar, I've done so in about 7,000 characters, but according to my new discoveries, I may have missed something. However, I can't go into so much detail while still making my image descriptions short enough that a screen reader can read through them in under a minute. CC: @<a href="https://partyon.xyz/@nat" rel="nofollow noopener noreferrer" target="_blank">Nat Oleander</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland@<a href="https://partyon.xyz/@nat" rel="nofollow noopener noreferrer" target="_blank">Nat Oleander</a> It's just a pity that if you post about an obscure enough niche topic like I do, it's the more difficult to make image posts perfectly accessible to everyone, the more obscure the topic is. For the more obscure the topic is, the more you have to describe, and the more you have to explain. (Caution: Never put explanations into alt-text! They must go where everyone can access them.) I currently write the longest image descriptions in the whole Fediverse by a wide margin. But they may not actually be accessible enough, even though I describe all my original images twice. The short descriptions in the alt-text don't always contain text transcripts, especially not all of them, and being only short descriptions, they aren't full, detailed visual descriptions either. The long descriptions for the same images in the post regularly end up with a five-digit character count. They may not be accessible because they're way too long. But sometimes they're the only place where all text transcripts can be found. And they are the only place where explanations can be found. So the consequence should be that I quit posting my original images because they're impossible to make perfectly accessible to everyone, at least as long as there is no rock-solid definition for what's actually required in image descriptions in my obscure edge-case. But there isn't even any consensus on whether text that's illegible or that's so tiny that it's basically invisible must be transcribed if it can be sourced. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland<blockquote>Don't hesitate to ask if you're unsure of something, but never think that we don't notice your effort.</blockquote> I do have a few questions, specifically because my image posts have gone unnoticed by blind or visually-impaired users so far. Judging and assuming from the information I've gathered so far, my original images require very extensive and detailed descriptions. A full description is too long for alt-text, so what I do is write a full description with all text transcripts and all necessary explanations, put it into the post text body and then condense a shorter, but still long alt-text from it. What's your stance on this method of describing the same image twice over? Also, where would you personally prefer a long description? In the post itself? Or in an external document that's linked into the post? If you're on a phone app, remember that the external document will inevitably open your Web browser. Do you prefer images described, based on what a sighted person can see in the image as it is posted? Or do you prefer a description that is not limited by the restriction of the image itself, for example, assuming an infinite image resolution and an infinite zoom factor that would let sighted people theoretically see even tiniest details? If I mention something in my image description of which you don't know what it looks like, do you need a detailed visual description? Concerning text transcripts: Let's assume a bit of text in an image is too small to be legible for sighted people, but I can read it at the original source, so I can transcribe it nonetheless. Shall I transcribe it? What about if said text is too small to be recognisable as text or so tiny that's it's practically invisible? I mean, after all, the concept of image resolution should not matter to totally blind people, so writing that a piece of text can't be read because the resolution of the image is too low ought to sound like a lame excuse for skimping a transcript. If there's a building in one of my images, I can safely assume that you don't know what that one specific building looks like, so I guess I can also assume that you need it described. If I could, I would do so using architectural terms and then explaining all these architectural terms right after using them. Would you say that's the correct way? Because that's why I avoid having realistic buildings in my images. If there's an image in my image, do you need it described? At a level that I can source right where the image is without moving away too far, or at a level that I can only source by moving farther away to the place shown in the image? What about an image in an image in my image? (I'm serious. I've actually described images within images within my image, but I've stopped when this was about to go out of hand due to there being too many to describe.) I'm currently working on a series of posts with images showing a virtual-world avatar in various but similar outfits; in fact, I have been since last year. I may have questions later regarding at what level of detail I have to describe that avatar. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland@<a href="https://infosec.exchange/@ErikvanStraten" rel="nofollow noopener noreferrer" target="_blank">Erik van Straten</a> <blockquote>I often spend more time writing alt text than the text in the toot itself - not just to keep the toot itself as short as possible.</blockquote> I always spend more time describing my images than writing the post that they go into. For my meme posts, that's because I have to explain the picture and find the appropriate links to external explanations (KnowYourMeme etc.) to shorten my explanation block if possible. For my original images, it's because I have to describe them twice. There's always an alt-text which, as of late, fills the 1,500-character limit imposed by Mastodon, Misskey etc. to the brim. But that alt-text is only a shortened and slightly adapted version of an extremely long long description which goes into the post text body and which also includes transcripts of any and all text in the image, readable or not, as well as all explanations which I deem necessary for outsiders to understand the image. Since the images are about an extremely obscure niche topic, this means I have to explain a lot. A while ago, I spent two full days, morning to evening, researching for and describing and explaining one single image. The result was <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener noreferrer" target="_blank">probably the longest image description ever posted in the Fediverse</a>. And I actually had to limit myself, otherwise the description would have been even vastly longer and taken over a month to complete. Good thing I don't have any character limit to worry about. The only exception is that Mastodon may reject posts from outside with over 100,000 characters. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a>

Jupiter Rowland@<a href="https://social.dhelonious.de/@daniel" rel="nofollow noopener noreferrer" target="_blank">Dr. Daniel Dizdarevic</a> It isn't just because of compression, nor is it because I scale my images down from my original 2100x1400 renderings to 800x533. As I've said: I don't describe the image with the things in it. I describe the things. Not as they appear in the image, but as they are in-world where I can walk closer to them or move the camera closer to them. It's like an image with a near-infinite resolution. For example, if there's a light grey blob in the image, four pixels wide, three pixels high, I describe it as what it is in-world, a white sign with three lines of black writing on it. I transcribe the text on the sign 100% verbatim including all spelling mistakes, I translate it afterwards if it isn't in English, I may even explain the text if someone out there needs an explanation, and I may go as far as naming and describing the typeface. Or if there are two by two pixels on different levels between red and white, I describe them as what they are in-world, a strawberry cocktail in a conical glass, somewhat like a Martini glass. And I slap an "alcohol" content warning on the whole post. Nowadays, I'd even flag the image sensitive just because of these four pixels. I used to go as far as describing images within my image and even images within images within my image at higher levels of detail than anyone else would describe their own images. I used to describe things that weren't even visible in-world in the place shown in the image. Pictures of places that I would have to walk or even teleport to to be able to describe them. Textures that I would have to make visible otherwise to be able to see all details. The last time I've described an image in an image with details not visible in the place shown in my image was in <a href="https://hub.netzgemeinde.eu/item/136f021c-06cb-4e38-abe6-2bf37fd521d8" rel="nofollow noopener noreferrer" target="_blank">this post</a>. I used almost 5,000 characters to describe a poster on the info board. I had to walk to the place displayed in the image on the poster to be able to describe it. The description of the image within the image got so lengthy that, when I was done, I had to remind the reader that I'm returning to describing "my" image. And I actually "cheated" by adjusting the camera in such a way that one of the three posters on the info board is entirely concealed behind a tree trunk because it would have been painfully difficult to describe. I stopped going that deep when I wrote the image description for <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener noreferrer" target="_blank">what will probably remain my last image post on this channel</a>. The long description was already growing absolutely humongous, and it's my longest one to date with over 60,000 characters. I had actually thought this scene would be easy to describe. The problem I encountered was that there were simply too many images within images within my image. There's one teleporter near the left-hand edge with a preview image that made me reconsider. In-world, no matter how close I move the camera to the preview image, it mostly shows a square area that appear to be tan all over except for something dark and unidentifiable in the middle. Actually, however, the place shown in the preview image has hundreds of single-destination teleporters. Several dozen of them are activated and have one preview image each of their destination. I teleported there to take closer looks at everything. I was actually about to write a description of that "teleport station" when I realised that I also had to describe every single one of these preview images, at least those that face the camera in the preview image on the teleporter in the place that I was originally describing. And some of these preview images had images in them in turn. I would have had to describe probably over a hundred images. In dozens of images. On teleporters which are shown in yet another image on a sub-pixel level. In an image description which was already going out of hand length-wise. On the second day that I was working on that image description. I would have had to teleport at least three times from the place shown in my image to be able to describe these sub-sub-subimages. That was when I decided to sacrifice details for convenience and only describe what's visible in-world within the borders of the image, excluding both objects that are entirely obstructed by something else and surfaces that entirely face away from the point of view. I do fully transcribe any text that's partially obstructed, though, although I'm considering two transcripts of such texts, namely one transcript of what's visible and one full transcript for better understanding. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener noreferrer" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener noreferrer" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener noreferrer" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta</a>

Jupiter Rowland@<a href="https://social.dhelonious.de/@daniel" rel="nofollow noopener noreferrer" target="_blank">Dr. Daniel Dizdarevic</a> I always consider "let them ask if they want to know" bad style for such elementary information. It seems to me like one of these things where Mastodon's good alt-text proponents may criticise you for not mentioning it right away. That is, I wouldn't put that information into the alt-text. I only have about 900 or 1,000 characters at my disposal for describing an image in alt-text. Mastodon, Misskey and their forks chop alt-texts over 1,500 characters off in posts from outside, and I need the rest of the characters to explain where a longer and more detailed description can be found for as long as there are still instances of Mastodon under 4.4 around. This is information that would go into said long description. I've always put the long description into the post itself where I technically don't have any character limits. The limit of 100,000 characters above which Mastodon may completely reject posts is not much to worry about either as long as I don't have multiple highly detailed images with little in common to describe. Leaving out the information where an image is from, unless I have very good reasons to keep the location secret, feels like not giving a long description at all. And not giving the long and detailed description, in the case of my original images, is like omitting the alt-text for "normal" images entirely. I've asked the above question because I have a series of images which are special cases. If surroundings were visible in the images and not too generic, I would definitely explain where the image was made, not although, but because next to nobody in the Fediverse could tell from looking at the image where it was made because even the sighted users would never have seen anything like it before. I want to give everyone in the Fediverse the chance to see the image not only like any sighted person sees it, but like I see the original. This is also why I describe details and transcribe text so tiny that they're basically invisible in the image at its given resolution. But in this special case, the images don't carry any information at all on where they're from. In other words, the information where they're from might be completely useless. Or it might not. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener noreferrer" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusivity" rel="nofollow noopener noreferrer" target="_blank">Inclusivity</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a>

Jupiter RowlandNow I'm wondering again: Let's suppose I have a series of 3-D virtual world images that have a plain white background because they were intentionally created in front of a plain white background. It's impossible to tell from the images where they were made, and when I post them, it won't matter within the context where they were made. Any chances that someone out there might still want to know where exactly I've made these images? Either someone who doesn't know about these worlds, and who is totally curious about them, or one of those probably fewer than 20 Fediverse users who does know about these worlds, and who wants to know where I've gone to make these images? I can easily spare the few hundred extra characters. The only character limit I have to worry about are the 100,000 characters above which Mastodon probably rejects a post from outside. @<a href="https://a.gup.pe/u/accessibility" rel="nofollow noopener noreferrer" target="_blank">accessibility group</a> @<a href="https://a.gup.pe/u/a11y" rel="nofollow noopener noreferrer" target="_blank">a11y group</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener noreferrer" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusivity" rel="nofollow noopener noreferrer" target="_blank">Inclusivity</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a>

Recent searches

Search options

Administered by:

Server stats:

#imagedescriptions