mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#imagedescriptions

0 Beiträge0 Beteiligte0 Beiträge heute
Stefan Bohacek<p>I created <a href="https://AltTextHallOfFame.org" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">AltTextHallOfFame.org</span><span class="invisible"></span></a> two years ago with the simple goal of celebrating the effort and creativity that goes into making the web a friendlier and more inclusive place, one captioned image at a time.</p><p>Here's a blog post from last year where I talked more about my motivations.</p><p><a href="https://stefanbohacek.com/blog/why-i-made-alt-text-hall-of-fame/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">stefanbohacek.com/blog/why-i-m</span><span class="invisible">ade-alt-text-hall-of-fame/</span></a></p><p><a href="https://stefanbohacek.online/tags/AltText" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AltText</span></a> <a href="https://stefanbohacek.online/tags/AltTextHallOfFame" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AltTextHallOfFame</span></a> <a href="https://stefanbohacek.online/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accessibility</span></a> <a href="https://stefanbohacek.online/tags/ImageDescriptions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ImageDescriptions</span></a> <a href="https://stefanbohacek.online/tags/anniversary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>anniversary</span></a></p>
Jupiter Rowland@<a href="https://mastoart.social/@elaterite" rel="nofollow noopener" target="_blank">Bob Tregilus</a> Only that "my best" has actually led to unimaginable extremes.<br><br>They say an image is worth a thousand words. I've once <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener" target="_blank">described one image</a> in over 10,000 words. <strong>Over 60,000 characters.</strong> The post is so long that, I think, Misskey and its various forks have rejected it, as have Pleroma and Akkoma. It took me two full days, morning to evening, to describe that one image, in-world research included.<br><br>And I actually had to limit myself. For once, I did not give in-depth descriptions of the images within that image, especially not beyond what's actually visible in these images. That's because I've discovered that if I were to do that, I'd have to describe dozens of images in one particular image (in my image) and potentially over a hundred images in these, even though they're so small that they're technically invisible. It would have taken me months to write all that. And it would have been futile anyway. My character limit is over 16 million, but Mastodon rejects posts over 100,000 characters, and in the few places that do accept posts with millions of characters, next to nobody cares about image descriptions.<br><br>I haven't posted a new in-world image in over half a year. I've been working on-and-off on the descriptions for a series of rather simple avatar portraits since last autumn.<br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a>
Jupiter Rowland@<a href="https://mastoart.social/@elaterite" rel="nofollow noopener" target="_blank">Bob Tregilus</a> Of course, this means that the more obscure the content of your image is, the more in-depth you will have to go. At worst, there's nothing in your image of which non-sighted people know what it looks like unless you describe it. Simply mentioning that it's there is not sufficient.<br><br>My own original images aren't even photographs, nor are they pieces of art that represent real life. They're renderings from 3-D virtual worlds, very obscure 3-D virtual worlds even. Nobody knows what anything in these world looks like unless they can see it in my images. At the same time, however, chances are that they become so curious about these virtual worlds that they also become curious about everything in the image, not just what matters within the context of the post. That is, sometimes the image itself as a whole is the context. Either way, this means I can't just focus on certain elements in the image in my descriptions. I have to describe everything.<br><br>So I've gotten to a point at which even filling the alt-text character limit forced by Mastodon, Misskey and their respective forks (they cut longer alt-texts off at the 1,500-character mark) doesn't cut it. All my original images have two descriptions now. In addition to the one in the alt-text that's very limited, there is another one in the post that's more or less fully detailed, that contains transcripts of all text within the borders of the image, and that also comes with all explanations that I deem necessary. Since I don't have a character limit to worry about (the limit is defined by the database field rather than a hard-coded or configurable number), this description is likely to grow well over a hundred times longer than typical alt-text.<br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a>
Jupiter Rowland@<a href="https://norden.social/@PalmAndNeedle" rel="nofollow noopener" target="_blank">PalmAndNeedle</a> I know. <a href="https://hub.netzgemeinde.eu/item/db8f9353-e126-49b2-ad06-87c5e1df8d00" rel="nofollow noopener" target="_blank">I have evidence.</a><br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AI" rel="nofollow noopener" target="_blank">AI</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AIVsHuman" rel="nofollow noopener" target="_blank">AIVsHuman</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HumanVsAI" rel="nofollow noopener" target="_blank">HumanVsAI</a>
Jupiter Rowland@<a href="https://mastodon.social/@iFixit" rel="nofollow noopener" target="_blank">iFixit</a> <blockquote>and it doesn't look like you can attach documents to posts</blockquote><br>You can't on Mastodon. I could, both here on <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> and on <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener" target="_blank">(streams)</a> where I post my images.<br><br>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.<br><br>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.<br><br>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.<br><br>Now I'm wondering if <em>that</em> could be helpful or actually required, or if it's overkill and actually a hindrance.<br><br>CC: @<a href="https://connectified.com/@masukomi" rel="nofollow noopener" target="_blank">masukomi</a> @<a href="https://mastodon.scot/@gunchleoc" rel="nofollow noopener" target="_blank">GunChleoc</a><br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescription" rel="nofollow noopener" target="_blank">MediaDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MediaDescriptions" rel="nofollow noopener" target="_blank">MediaDescriptions</a>
Jupiter Rowland@<a href="https://kolektiva.social/@enby_of_the_apocalypse" rel="nofollow noopener" target="_blank">undead enby of the apocalypse</a> It depends.<br><br>My original images, rare as they are, are even more niche than @<a href="https://mastodon.nl/@Rana" rel="nofollow noopener" target="_blank">Zeewater</a>'s, namely renderings from extremely obscure 3-D virtual worlds. This is something that maybe one out of 200,000 Fediverse users "has a basic understanding of". The other 199,999 need explanations.<br><br>I've long since decided how much detail is relevant, based on who may come across my images, and what they may be interested in. As I don't limit my target audience although I could, I write my image descriptions for random strangers who stumble upon a post of mine on some federated timeline. Considering the topic, they might be interested in <em>everything</em> in the image, regardless of context. And yes, at the same time, they may not be fully sighted.<br><br>And so I go to such detail that I need two image descriptions. A "short" and purely visual description in the alt-text (which still tends to grow to 1,500 characters, complete with the note where a longer description can be found), and a long, detailed description with all necessary explanations and all text transcripts in the post itself (I don't have any character limits to worry about).<br><br>CC: @<a href="https://mastodon.neilzone.co.uk/@neil" rel="nofollow noopener" target="_blank">Neil Brown</a><br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a>
Jupiter Rowland@<a href="https://toot.cat/@garry" rel="nofollow noopener" target="_blank">Garry Knight</a> @<a href="https://mstdn.social/@qurlyjoe" rel="nofollow noopener" 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:<br><br>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.<br><br>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" target="_blank">this comment thread</a>:<br><br> <a href="https://hachyderm.io/@gnomicutterance" rel="nofollow noopener" target="_blank"></a><span><a href="https://hachyderm.io/@gnomicutterance" rel="nofollow noopener" target="_blank">Deborah</a> schrieb den folgenden <a href="https://hachyderm.io/@gnomicutterance/110691919197248049" rel="nofollow noopener" target="_blank">Beitrag</a> <span class="">Mon, 10 Jul 2023 23:30:45 +0200</span></span> <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland" rel="nofollow noopener" target="_blank">@jupiter_rowland</a> <br><br>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.<br><br>But you don’t have to overthink it. The description of the image itself is a simple concept. <br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener" target="_blank">Accessibility</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePost" rel="nofollow noopener" target="_blank">QuotePost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweet" rel="nofollow noopener" target="_blank">QuoteTweet</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToot" rel="nofollow noopener" target="_blank">QuoteToot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoost" rel="nofollow noopener" target="_blank">QuoteBoost</a>
Jupiter RowlandLink to an article on what I've learned about describing images for the Fediverse; CW: Fediverse meta, Fediverse beyond Mastodon meta, alt-text meta, image description meta
Jupiter Rowland@<a href="https://nerdculture.de/@annam" rel="nofollow noopener" 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.<br><br>In both cases, I had the <a href="https://llava.hliu.cc/" rel="nofollow noopener" 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.<br><br>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.<br><br>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.<br><br>So without further ado, <strong>exhibit A:</strong><br><br><a href="https://hub.netzgemeinde.eu/item/db8f9353-e126-49b2-ad06-87c5e1df8d00" rel="nofollow noopener" target="_blank">This post</a> contains<br><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.<br><br>If you've got some more time, <strong>exhibit B:</strong><br><br>Technically, all this is in one thread. But for your convenience, I'll link to the individual messages.<br><br><a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener" target="_blank">Here is the start post</a> with<br><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><br><a href="https://hub.netzgemeinde.eu/display/69317442-c4b7-4dc2-beed-38438abfc50a" rel="nofollow noopener" target="_blank">Here is the comment with the AI description</a> (1,120 characters; I've asked for a detailed description).<br><br><a href="https://hub.netzgemeinde.eu/display/451d2f06-7746-4227-a043-76a959420c29" rel="nofollow noopener" target="_blank">Here is the immediate follow-up comment with my review of the AI description.</a><br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AI" rel="nofollow noopener" target="_blank">AI</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LLaVA" rel="nofollow noopener" target="_blank">LLaVA</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AIVsHuman" rel="nofollow noopener" target="_blank">AIVsHuman</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HumanVsAI" rel="nofollow noopener" target="_blank">HumanVsAI</a>
Jupiter Rowland@<a href="https://mastodon.online/@sunflowerinrain" rel="nofollow noopener" target="_blank">sunflowerinrain</a> @<a href="https://mastodon.green/@Tarnport" rel="nofollow noopener" target="_blank">Tarnport</a> From what I've read, a digital photograph is considered the default. So for brevity reasons, it <em>must not</em> be mentioned.<br><br>Any other media <em>must</em> 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.<br><br>But an alt-text must <em>never</em> 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.<br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a>
Jupiter Rowland@<a href="https://social.dhelonious.de/@daniel" rel="nofollow noopener" 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.<br><br>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.<br><br>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.<br><br>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.<br><br>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.<br><br>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" 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.<br><br>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" 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.<br><br>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.<br><br>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.<br><br>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 <em>three times</em> from the place shown in my image to be able to describe these sub-sub-subimages.<br><br>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.<br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener" target="_blank">CW</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener" target="_blank">CWs</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener" target="_blank">ContentWarning</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener" target="_blank">ContentWarnings</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener" target="_blank">ContentWarningMeta</a>
Jupiter Rowland@<a href="https://social.dhelonious.de/@daniel" rel="nofollow noopener" 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.<br><br>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.<br><br>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.<br><br>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.<br><br>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 <em>because</em> 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.<br><br>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.<br><br>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.<br><br>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusion" rel="nofollow noopener" target="_blank">Inclusion</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Inclusivity" rel="nofollow noopener" target="_blank">Inclusivity</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener" target="_blank">Accessibility</a>
Jupiter RowlandIf it's absolutely impossible to see where an image was made, should it be mentioned in the image description nonetheless? CW: long (over 1,000 characters), image description meta
Antwortete im Thread
@Alan Levine Judging by the advice I've read so far, it's always best to describe the colour using basic colours plus attributes such as brightness, saturation and what other basic colour or colours the colour you describe is leaning towards.

For example, "light, yellowish orange", "a darker, slightly less saturated, slightly more brownish tone of orange", "various shades of slightly yellowish, medium-light-to-medium brown", "a solid, slightly pale medium blue with a minimal hint of green", "a medium-dark wood texture, slightly reddish, slightly greyish". All actually used by me in the long descriptions in (content warning: eye contact) this image post.

If the name of the colour plays a role, use it and then describe the colour in the same way as above. Blind or visually-impaired people may not know what Prussian blue or Burgundy red looks like.

@Stefan Bohacek @❄️Faerie❄️ @cobalt @Tanya McGee Wheatley 💜🥰 What do you say, is that appropriate, complete overkill or still insufficient?

#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Antwortete im Thread
@Morgan ⚧️ Well, what I meant with "do what I do anyway" is not what everyone else does.

My Fediverse meme posts have fairly standard image descriptions. What may make them long and complex are the explanations. They matter in this context because everyone else would explain meme images in the alt-text, but explanations don't belong into alt-text. And meme posts about Fediverse things do need a lot of explanation if they go beyond Mastodon, and mine tend to go way beyond Mastodon.

(Content warning: eye contact) My first attempt at a new meme-posting format on a new, specialised channel was made under the assumption that Mastodon users prefer explanations given to them on a silver platter, right in the post itself which also contains the image. I was told a while ago that external links are bad and inconvenient and probably not accessible, and it's better to explain everything myself.

I always have to explain the meme template, and especially in this case, I also had to explain the topic. So I ended up with nine explanations on four or five levels with some 25,000 characters altogether, more than half of which went into the two explanations for the topic.

I couldn't imagine that this was actually what people wanted, seeing as it was generally Mastodon users who seemed to want me to explain everything, but at the same time, it's Mastodon users who complain the most loudly about long posts. And so I ran a poll on how people actually wanted meme posts to be explained. At least of the few who voted, nobody wanted explanations in the post if they end up tens of thousands of characters long.

Ever since, I've delegated the meme template explanations to KnowYourMeme which I link to.

As for the topic, (content warning: eye contact, guns) sometimes it needs no explanation. Sometimes ](content warning: eye contact, food) it can entirely be covered by links. Sometimes (content warning: eye contact) I only need a short explanation.

But in cases like (content warning: eye contact, swearing) this or (content warning: eye contact, anger, crying, Japanese swearing) this, I have to write extensive explanations, even if I can link to a whole lot of external information sources.

For my original images, renderings from very obscure 3-D virtual worlds, I do much more. I always write two image descriptions for each image.

One goes into the alt-text, and it's as long as I can make it within the 1500-character limit imposed by Mastodon, Misskey and their forks. And that's the short description that's mostly only there to satisfy the "every image must have alt-text, no matter what" fundamentalists.

There's also a long description in the post itself which is much, much more detailed. It also contains all necessary explanations which I have to write myself because I can't really rely on external links. And if there's any text anywhere within the borders of the image, legible or not, verbatim transcripts of all these bits of text go into the long description.

My most recent example, already on my new image-posting channel, but from four months ago, is (content warning: eye contact) this. I've taken care to have as little scenery or surrounding or anything else in the pictures as possible, and still, I ended up with over 20,000 characters of image description. Here I explain why portraits are easier to describe.

A few examples with scenery, in chronological order, and much longer descriptions, and I consider them all outdated regardless: (content warning: eye contact, food) this, (content warning: eye contact) this and (content warning: eye contact) this.

The first two links also demonstrate how I used to describe pictures within a picture, even on three levels in the case of the second link. But if I had carried on doing this the same way for the image behind the third link, I would have had to describe over a hundred images in various locations on at least four levels. Besides, I would have described details that not only aren't visible in the image, but that aren't visible either in the place shown in the image. Also, this might have revealed eye contact or another trigger of sorts.

So I decided against describing things that cannot be seen in the shown place. This was the first time that I actually imposed a limitation on myself.

I could post many, many, many more scenery pictures, maybe even with actual scenery and with many more details. But it would always take me days to describe one of them. The last two image posts I've linked to required two days to write descriptions.

For example, I've been to a New Orleans-themed place a month ago. It would have made for a gorgeous picture report. But it would have taken me at least a week and a half to only describe the four images that Mastodon would let through. In fact, Mastodon would have rejected the post anyway because, with the massive image descriptions, it would have exceeded 100,000 characters by far.

If you're wondering why my descriptions of virtual world images have to be so long and so detailed, I've written an article about that.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
Antwortete im Thread
@Morgan ⚧️ I've spent two full days describing one image.

I feel bad when I can't describe something in an image the way I'd like to see myself describe it.

I keep coming across scenes that I think might make for nice pictures. But then I start trying to describe them in my head. And when I discover something that I can't properly describe, I don't even take the picture. I couldn't post it anyway without a description that's up to my standards.

I refuse to post images with realistic-looking buildings in them due to how complex they are to describe. After all, I'd have to first research architectural terminology and then explain it to my readers in the long image description.

A bit over a year ago, while working on an image description which, the next day (!), would end at over 38,000 characters, I realised that I had to describe three pictures of stellar nebulae. I didn't even really know how. I was about to abandon the whole image-posting project due to this. What I've eventually written still feels like a sub-par kludge, not to mention outdated a few times over.

I've read about people going back and alt-texting their entire backlog of image posts. I've wondered a few times if it is or should be recommended to go back and edit and improve your old image descriptions after you've learned something new in terms of describing images.

What do you think, is this genuine or not?

And seriously, I don't even know whom exactly I'm doing all this for because I almost never get any feedback in any form. I do it for whoever comes across one of my image posts. Since my new channel for original images (which I do these monstrous descriptions for) has only got nine followers, and my channel for Fediverse memes (which at least tend to come with extensive explanations) has only seven, it has to be a very rare occurrence that someone who really needs an image description finds one of my image posts.

But I guess the ultimate solution is to forget about "Nothing About Us Without Us" and do what I think is right until too many people come complaining. Which will probably amount to indefinitely.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility
hub.netzgemeinde.euWhen old meets new: Arcadia Asylum exhibits at OpenSimFest 2023Classic creations by Arcadia Asylum a.k.a. Lora Lemon/Aley at OpenSimFest 2023; CW: long (post text: 258 characters, first image description: 38,650 characters, second image description: 26,213 characters, third image description: 9,687 characters, full net length: 76,780 characters), eye contact
Antwortete im Thread
@Darrell Hilliker 👨‍🦯♾️📡 I think that's part of the issue, even if it's unavoidable: There's no one way to please everyone. And the more niche and special your content is, the harder it becomes to please as many disabled people as possible.

There's a saying: "Nothing about us without us." Don't assume what disabled people may need. Ask them. Talk to them. Listen to them.

But I guess the attitude in the Fediverse is that everything is said, everything is defined, everything is set in stone, and it'll work in 100% of all cases. No need to talk about it. You're expected to know it. Just do it.

I mean, I could just carry on assuming, based on what I've read here and there, even if that's technically the wrong thing. I know that there are at least some people who enjoy what I do, for whom it may be helpful.

I could just go on doing that and improving that, for any definition of improving. I could go on until enough people complain to me that I'm doing it completely wrong, and that staggering level of detail is bad for magnitudes more people than it helps. But this is unlikely to happen, seeing as how little feedback I receive.

I mean, at the end of the day, I can't really know whom I describe my images for. Do blind or visually impaired users even come across my image posts, seeing as they come from two different channels than this one now? Do those come across my image posts who demand sanctions for everyone who doesn't describe their images sufficiently? Are my extensive image descriptions and explanations useful for anyone?

Still, I go on putting huge efforts into describing them for the random stranger who stumbles upon one of them on some federated timeline, regardless of whether they're visually-impaired, blessed with a terribly slow Internet connection or a fully sighted alt-text enforcer.

And I will most likely go on increasing my efforts where I can. I'm currently polishing my way of describing persons or rather avatars. After all, I can see the alt-text quality requirements in the Fediverse be constantly raised, too. I need to stay ahead of them.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility
hub.netzgemeinde.eu"Nothing About Us Without Us", only it still is without them most of the timeWhen disabled Fediverse users demand participation in accessibility discussions, but there are no discussions in the first place, and they themselves don't even seem to be available to give accessibility feedback