ecoevo.social

Jupiter Rowland@<a href="https://masto.ai/@Pineywoozle" rel="nofollow noopener" target="_blank">@pineywoozle ‘s #3WordNote</a> In my defence, I don't post cat photos or social media screenshots. I post either renderings from extremely obscure 3-D virtual worlds or memes about similarly obscure topics. Either way, extensive explanations are necessary for people to understand my image posts. And in the case of the renderings, so are detailed visual descriptions because I cannot rely on anyone knowing what anything in my images looks like. <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener" target="_blank">I have very good reasons for writing such extremely long image descriptions.</a> And I can reassure you that <a href="https://hub.netzgemeinde.eu/item/1e63be04-d96e-412a-ab47-aff18c5f9ad8" rel="nofollow noopener" target="_blank">I've learned more than a thing or two about describing images and writing alt-texts for the Fediverse</a> over the last few years. <a href="https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Home" rel="nofollow noopener" target="_blank">I'm even working on a wiki about this topic.</a> The eight hours that I've mentioned led to 20,000 characters of image description for two images. These 20,000 characters went into the post text body, not into the alt-texts. The extra hour was for cutting alt-text descriptions down from these 20,000 characters in addition to these 20,000 characters in the post text. The alt-text of each image contains a little under 1,000 characters of description + a bit over 500 characters which announce the long descriptions in the post and explain how to find them. This means that each image is described twice. In case you can't imagine what I'm talking about: <a href="https://streams.elsmussols.net/item/b6ae326a-c207-46dd-836b-6bc2b6a3509c" rel="nofollow noopener" target="_blank">This is the post in question.</a> (You'll have to click on the summary to see the post, then scroll down to the content warning spoiler tag way down the post and then click it to see the images.) Also, it doesn't matter whether the majority of users may or may not need such a long description. Someone somewhere out there may actually need it, I can see why they may need it, and I've actually been thanked for even longer descriptions by people who needed them, if only a few times. I will continue writing such long image descriptions as long as I don't have rock-solid written proof that the majority of Fediverse users is staunchly and decidedly against long image descriptions in posts, no matter how obscure and at the same time curiosity-inducing the topic may be, and not only because they're against posts that exceed 500 characters. #<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://chaos.social/@oxytocinated" rel="nofollow noopener" target="_blank">charly :antifa:</a> <blockquote>I do alt text, but it's not low effort at all.</blockquote> Same here. In fact, I've had the image descriptions for a series of avatar portraits in the making since late 2024, and I may have to rework them again. Last time I've posted images was over a year ago, and it took me eight hours to describe two images plus one hour to distill shorter alt-text descriptions from the long descriptions. But before I post an image without an appropriate description and appropriate explanations, I don't post any. CC: @<a href="https://masto.ai/@Pineywoozle" rel="nofollow noopener" target="_blank">@pineywoozle ‘s #3WordNote</a> @<a href="https://beige.party/@maxleibman" rel="nofollow noopener" target="_blank">Max Leibman</a> #<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://mas.to/@iwein" rel="nofollow noopener" target="_blank">iwein</a> This is why I've started (occasionally) working on a wiki about how to describe images and write alt-texts specifically in and for the Fediverse. Not just a one-pager, but an entire wiki that will have about three dozen pages when it's done. I'm sourcing various alt-text and image description guides that exist out there on the Web, and I cite them when necessary or appropriate. They may contradict each other, but I'm going to point that out as well. Still, I also point out when something that's valid for alt-texts on static websites or in blog posts is not valid for Fediverse posts. I simply want to be able to tell people how to do it right. I often have to because people keep doing so much wrong. And I want to be able to do so without having to write my explanations directly into posts over and over and over again. Instead, I'll simply be able to link to the pages in my wiki. It's a very early WIP, it's nowhere near completion, but if you're curious, <a href="https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/Home" rel="nofollow noopener" target="_blank">here it is</a>, right on the same Hubzilla channel that I'm commenting from right now. #<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=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</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://circumstances.run/@Szescstopni" rel="nofollow noopener" target="_blank">Szescstopni</a> <blockquote>What is too long/too short?</blockquote> There can't be any fixed definition for that. Not here in the Fediverse. The "Over 200 characters is too long" rule does not work in and can't be applied to the Fediverse. No, sorry, it can't. I've explained it in my (very early WIP) wiki about image descriptions and alt-text in the Fediverse: <a href="https://hub.netzgemeinde.eu/wiki/jupiter_rowland/How(20)to(20)describe(20)images(20)in(20)the(20)Fediverse/How(20)are(20)alt-text(20)and(20)image(20)descriptions(20)in(20)the(20)Fediverse(20)different(20)from(20)other(20)places(3f)" rel="nofollow noopener" target="_blank">How are alt-text and image descriptions in the Fediverse different from other places?</a> (tl;dr: On the Web, over 200 characters in alt-text are evil, but you've got captions, and you've got ample of other possibilities to describe an image than the alt-text. On Mastodon, you've only got the alt-text for image descriptions, and people cheer for 1,000-character alt-texts.) Depending on a) the kind of image you post, b) the obscurity of its contents, c) your audience (including whoever might stumble upon your image post; if you post in public, that's basically the whole Fediverse and everyone with Web access), d) their knowledge about what your image shows and e) their to-be-expected curiosity about what your image shows, you may have to describe your image in way more than 200 characters. <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener" target="_blank">This was the last time I've posted an image here on Hubzilla.</a> It's a rendering from within a super-obscure 3-D virtual world. Next to nobody has ever seen it, but due to this being a 3-D virtual world (= proof that "the Metaverse is surprisingly not dead"), curiosity may be high. And my impression of especially Mastodon is that people prefer being given any and all information they may need right away to having to ask. Like, ask what something specific looks like. And so the image description in the alt-text is a bit over 1,400 characters long. And it's still very lacking. It doesn't even mention certain elements in the image. And it doesn't transcribe even only one bit of text. It's actually an extremely shortened version of the long image description in the post text itself. Over 60,000 characters of visual description and necessary explanations and text transcripts. That's over 10,000 words. That's probably over three hours of a screen reader rambling. That's two full days of me examining the place up-close, looking up additional information and writing the description. But I deemed it necessary. If it was an absolute requirement for me to a) cut the alt-text down to a maximum of 200 characters and b) cut the long description altogether, lots and lots and lots of information would be lost, including all text transcripts. <blockquote>I must learn more about the rules of the capitalization police.</blockquote> If you use a hashtag like <code>#⁠superbowl</code>, how is NVDA or any other screen reader software supposed to know whether that means "Super Bowl" or "superb owl"? Thus, any new word in a multiple-word hashtag must be capitalised so that screen readers know that this is where a new word starts. There are two ways of doing this. One is camel case. Camel case is the lazy variant: The first word is not capitalised, all other words are. <code>#⁠oneTwoThree</code> The other one is Pascal case, named after the programming language Pascal. Pascal case is the prettier variant: All words are capitalised. <code>#⁠OneTwoThree</code> <blockquote>Oops, I shouldn't have posted those images in replies as public. Anyway, 833 out of 836 images with alttext ain't so bad.</blockquote> Replying to a public post with a DM isn't supported everywhere in the Fediverse anyway. This only works on purist microblogging server applications on which a thread is just a bunch of posts tied together with mentions. It does not, however, work on more elaborate Fediverse server applications like Hubzilla (where I'm commenting from right now), (streams) and Forte. On these, a thread is an enclosed object with exactly one post, the start post, and otherwise comments. They have a highly complex permissions system in which all permissions in a conversation are defined by the post. If the post is public, all comments are public, full stop. So if you had replied to this otherwise 100% public, 100% Mastodon thread with a DM, then Hubzilla would have monkey-wrenched your DM into a public comment with a red padlock symbol for a permission conflict. CC: @<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener" target="_blank">Stefan Bohacek</a> #<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=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=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=Forte" rel="nofollow noopener" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CamelCase" rel="nofollow noopener" target="_blank">CamelCase</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=PascalCase" rel="nofollow noopener" target="_blank">PascalCase</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener" target="_blank">Permissions</a>

Jupiter Rowland@<a href="https://mastodon.social/users/Karen5Lund" rel="nofollow noopener" target="_blank">Karen E. Lund 💙💛</a> Would you lose points for very long alt-texts/image descriptions? I tend to describe my original images in extremely high details. Recently (for any definition of "recently" because I haven't posted a single image in over a year due to the huge effort of describing them), my alt-texts tend to reach 1,500 characters or one or a few below that. At least ca. 900 characters are actual image descriptions, sometimes up to ca. 1,400. And that's what I consider a "short" description. Because the rest of the alt-text explains where to find the "long" description. It's in the post itself. It includes verbatim transcripts of every last bit of text anywhere within the borders of the image, readable or not. And it includes all explanations which I deem necessary for everyone to understand my images. This long description exceeds any known arbitrarily defined character limit anywhere in the Fediverse by magnitudes. I can post such long image descriptions because the only character limit I have here on Hubzilla is the maximum size of the database field for the post text. Yes, you've read that right. I describe each one of my original images twice. And I must write my image descriptions that long. I don't post real-life photos, nor do I post social media screen shots. I post renderings from extremely obscure 3-D virtual worlds. Maybe one in 200,000 Fediverse users has even only heard of the technology that drives them. Thus, I cannot assume anything in my images to be familiar to anyone out there. I can't assume that anyone out there knows what anything in my images looks like, also because my images tend to contain things which simply do not exist in real life in any shape or form. At the same time, my impression is that especially Mastodon users expect all information which they don't have to be served on a silver platter immediately with the image description. If you mention something in your image, and somebody doesn't know what it looks like, you're obliged to describe it right away. Expecting anyone to ask you anything about your image after the fact feels like being considered ableist. I mean, you could just as well expect people to ask you to describe the whole image in the first place, right? Same goes for explanations. Given the choice between looking stuff up themselves, being given links where they can look stuff up and being explained everything right there, right then, Mastodon users appear to greatly prefer the latter and only consider the latter really accessible. And I have to explain a lot. When I tell you where I've taken an image, this alone takes me more characters than some of you use for a whole day's worth of alt-texts. The whole topic is so obscure that I have to explain explanations of explanations. My personal record (warning: technically outdated image descriptions): <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener" target="_blank">1,500 characters of alt-text, 1,400+ of which are image description; 60,000+ characters of long description for one image</a>. That's about 10,000 words. It took me two full days, morning to evening, to research for and write the image descriptions. It takes a screen reader about three hours to read the long description out loud. But someone somewhere out there might be interested in all this information and displeased if they had to ask me about it to get it. As for bilinguality, I should add to my WIP wiki on image descriptions and alt-texts that an alt-text must never include more than one image because screen readers cannot switch between languages mid-alt-text. What I do, and I'm not even sure if that's such a good idea, is transcribe text in images that is not in English verbatim, literally letter by letter, and then translate it into English as closely as possible. I'm torn between a verbatim transcript which a screen reader cannot read out correctly and only giving a translation which would not be a verbatim transcript. In fact, I've once had a situation in which I had to transcribe a sign in English, (broken) German and French. So I gave <ul><li>a 100% verbatim transcript of the English text</li><li>a 100% verbatim transcript of the German text, all mistakes included</li><li>an English translation of the German text that's as close to the original as possible</li><li>a 100% verbatim transcript of the French text</li><li>an English translation of the German text that's as close to the original as possible</li></ul> Nowadays, I'd simply avoid posting images with non-English text anywhere in it like the plague. CC: @<a href="https://beige.party/@kimlockhartga" rel="nofollow noopener" target="_blank">Kim Possible :kimoji_fire:</a> @<a href="https://tech.lgbt/@dotjayne" rel="nofollow noopener" target="_blank">Jayne</a> #<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://beige.party/@LoganFive" rel="nofollow noopener" target="_blank">Logan 5 and 999 others</a> First of all: You must never put line breaks into alt-text. Ever. (<a href="https://www.tpgi.com/short-note-on-coding-alt-text/" rel="nofollow noopener" target="_blank">https://www.tpgi.com/short-note-on-coding-alt-text/</a>, <a href="https://joinfediverse.wiki/Draft:Captions#Line_breaks" rel="nofollow noopener" target="_blank">https://joinfediverse.wiki/Draft:Captions#Line_breaks</a>) Besides, that will certainly not be the day that I'll post my first image after more than a year. It's tedious enough to properly describe my original images at the necessary level of detail, and one image takes me many hours to describe, sometimes up to two full days, morning to evening. Not joking here. I certainly won't put extra effort into turning at least the 900 characters of "short" description that go into the alt-text into a poem. And I definitely will not also turn the additional 20,000, 40,000, 60,000 characters of long description that go into the post into a poem as well. (And yes, I can post 60,000+ characters in one go, and I have done so in the past. My character limit is 16,777,215.) #<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://layer8.space/@nihilistic_capybara" rel="nofollow noopener" target="_blank">nihilistic_capybara</a> LLMs aren't omniscient, and they will never be. If I make a picture on a sim in an OpenSim-based grid (that's a 3-D virtual world) which has only been started up for the first time 10 minutes ago, and which the WWW knows exactly zilch about, and I feed that picture to an LLM, I do not think the LLM will correctly pinpoint the place where the image was taken. It will not be able to correctly say that the picture was taken at <Place> on <Sim> in <Grid>, and then explain that <Grid> is a 3-D virtual world, a so-called grid, based on the virtual world server software OpenSimulator, and carry on explaining what OpenSim is, why a grid is called a grid, what a region is and what a sim is. But I can do that. If there's a sign with three lines of text on it somewhere within the borders of the image, but it's so tiny at the resolution of the image that it's only a few dozen pixels altogether, then no LLM will be able to correctly transcribe the three lines of text verbatim. It probably won't even be able to identify the sign as a sign. But I can do that by reading the sign not in the image, but directly in-world. By the way: All my original images are from within OpenSim grids. I've probably put more thought into describing images from virtual worlds than anyone. And I've pitted my own hand-written image description against an AI-generated image description of the self-same image twice. So I guess I know what I'm writing about. CC: @<a href="https://lgbtqia.space/@alice" rel="nofollow noopener" target="_blank">🅰🅻🅸🅲🅴  (🌈🦄)</a> @<a href="https://layer8.space/@nihilistic_capybara" rel="nofollow noopener" target="_blank">nihilistic_capybara</a> #<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=OpenSim" rel="nofollow noopener" target="_blank">OpenSim</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenSimulator" rel="nofollow noopener" target="_blank">OpenSimulator</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=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</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=LLM" rel="nofollow noopener" target="_blank">LLM</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://mspsocial.net/@bright_helpings" rel="nofollow noopener" target="_blank">Erik :heart_agender:</a> @<a href="https://beige.party/@roknrol" rel="nofollow noopener" target="_blank">Roknrol</a> What if I transcribe text within my image (for any definition of "text within my image") in a long image description in the post itself which I write in addition to the actual alt-text? And the alt-text explicitly mentions the long description at its end? E.g. "A more detailed description including explanations and text transcripts can be found in the post." I often have so many bits of text to transcribe (in addition to describing where in the image they are) that I can't fit them all into the 1,500-character limit for alt-texts that Mastodon, Misskey and their respective forks impose on the whole Fediverse. I'm not talking about screenshots from social media or something. I'm talking about renderings from 3-D virtual worlds where there may be 20, 30, 40 or more bits of text strewn across the scenery within the borders of the image. The rule says that all text within an image must be transcribed 100% verbatim, and it doesn't explicitly mention any exception, so I do have to transcribe them all. In addition, if they aren't in English, I must additionally translate them as literally as possible. There's no way I can fit all this plus a sufficiently detailed and accurate visual description into 1,500 characters. But if you (or others) insist that all text within an image must be transcribed verbatim in the alt-text, and if you sanction image posts that transcribe the texts in the image elsewhere than in the alt-text, then I simply won't be able to post certain images in an appropriate way. #<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> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Transcript" rel="nofollow noopener" target="_blank">Transcript</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Transcripts" rel="nofollow noopener" target="_blank">Transcripts</a>

Jupiter Rowland@<a href="https://mastodon.social/@alttexthalloffame" rel="nofollow noopener" target="_blank">Alt Text Hall of Fame</a> <blockquote>It's okay, you don't have to overthink it! Write how you'd describe the image to a friend over the phone.</blockquote> This only works with simple real-life photos. If your image shows more obscure stuff (like mine), <a href="https://hub.netzgemeinde.eu/item/21735784-8443-430a-aa09-e0d9d00a40c2" rel="nofollow noopener" target="_blank">this does not work</a>. (@especially Mastodon users: The link goes to a Fediverse post that you may import into your timeline by copying the URL and searching for it.) #<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=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://troet.cafe/@Irisfreundin" rel="nofollow noopener" target="_blank">Nervensäge 💐</a> I have found a few guides for alt-text and image descriptions, but they may contradict each other. <ul><li><a href="https://www.accessible-social.com/images-and-visuals/writing-image-descriptions" rel="nofollow noopener" target="_blank">https://www.accessible-social.com/images-and-visuals/writing-image-descriptions</a> (this one still mentions SEO, but it doesn't make HTML a requirement, and it's very informative when it comes to how to actually describe an image)</li><li><a href="https://www.cooperhewitt.org/cooper-hewitt-guidelines-for-image-description/" rel="nofollow noopener" target="_blank">https://www.cooperhewitt.org/cooper-hewitt-guidelines-for-image-description/</a> (this one is geared towards websites and blogs, too, but it goes into detail when it comes to the actual description, too)</li><li><a href="https://veroniiiica.com/media-accessibility/alt-text/" rel="nofollow noopener" target="_blank">https://veroniiiica.com/media-accessibility/alt-text/</a> (this has loads of individual pages about alt-text and image descriptions, and the author is visually impaired herself; she actually advocates two descriptions for each image, one in the alt-text, one in the text itself)</li><li><a href="https://www.sandstormdesign.com/blog/website-accessibility-101-5-best-practices-writing-alt-text-images" rel="nofollow noopener" target="_blank">https://www.sandstormdesign.com/blog/website-accessibility-101-5-best-practices-writing-alt-text-images</a> (again, website-focused, but again, no HTML, and it includes details like telling you not to mention the race of people in your descriptions and not the gender either if it isn't 100% proven and what to mention instead; it also recommends two descriptions for complex images)</li><li><a href="https://www.uml.edu/brand-communications-creative-strategy/resources-guidelines/web-accessibility/image-accessibility.aspx" rel="nofollow noopener" target="_blank">https://www.uml.edu/brand-communications-creative-strategy/resources-guidelines/web-accessibility/image-accessibility.aspx</a> (this one advocates alt-text that's no longer than 100 characters, and it contradicts the above in that alt-text must never repeat what's already in the text itself, but it underlines the rules about race and gender)</li><li><a href="https://www.tpgi.com/short-note-on-coding-alt-text/" rel="nofollow noopener" target="_blank">https://www.tpgi.com/short-note-on-coding-alt-text/</a> (this is a more technical one; it points out that and why alt-text must never include line breaks)</li></ul> The existing guides on how to write alt-text in social media aren't worth the effort. They don't tell you anything the guides above, at least not beyond walking you through the process of adding alt-text to images in certain social media, step by step. Most of them only cover American corporate social networks and social media (Facebook, Instagram, 𝕏, LinkedIn). A few add TikTok. Very few also add Mastodon, but even they only walk you through adding alt-text on Mastodon's standard Web interface. They do not deal with Mastodon's special alt-text culture. They assume that all social networks and social media have either the exact same alt-text culture as websites and blogs or none at all. And literally not a single guide covers anything in the Fediverse that is not Mastodon. Hence my wiki plans. For one, I want to explain alt-text and image descriptions in the Fediverse as a whole. I won't include step-by-step walkthroughs because I can't possibly know every Web UI and every phone app out there, but I will point out that alt-text doesn't work exactly the same everywhere in the Fediverse as on Mastodon. Besides, I want to take Mastodon's alt-text culture into consideration which is being forced upon the whole rest of the Fediverse. Finally, I want to write guides on certain aspects of describing images and writing alt-text and not only compile the information that's strewn about the Web in lots of individual guides, but also link to these guides as references and point out when they contradict each other. #<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://troet.cafe/@Irisfreundin" rel="nofollow noopener" target="_blank">Nervensäge 💐</a> Just a pity that this one particular guide doesn't really work in the Fediverse. First of all, the concept of "too long alt-text" or "too detailed alt-text" doesn't exist in the Fediverse, at least not on Mastodon where accessibility standards were defined by overly eager laypeople. Next, there are no decorative images in Fediverse posts. Also, only few Fediverse server applications support adding HTML tags to posts. The vast majority of Fediverse users, especially everyone on Mastodon, have a dedicated text entry field for adding alt-texts to image file attachments. Finally, SEO does not matter in the Fediverse at all. The whole guide is about alt-text on static websites designed by paid professional Web developers. As opposed to social media users, two out of three of whom can only post plain text. All this is why I've started putting together a wiki specifically for alt-text and image descriptions in the Fediverse. CC: @<a href="https://discuss.online/u/DNS" rel="nofollow noopener" target="_blank">DNS</a> #<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://masto.nu/@bigpawedbear" rel="nofollow noopener" target="_blank">Big Pawed Bear</a> I'm not talking about the technical side. That is, you may not have noticed, but I'm not posting from Mastodon. I'm on Hubzilla where things are quite a bit different. Images aren't file attachments; they're embedded into posts in-line using BBcode markup like in classic bulletin board forums. Alt-text has no dedicated text entry box; instead, it's manually woven into the image embedding code. No, what I mean is that here in the Fediverse, you can't describe an image like describing it to a friend over the phone. Open the link in my post. (If it looks like it may be a link, it actually is one, even if it isn't a URL in plain sight. I can do embedded links on Hubzilla, too.) Anyway, if you describe an image to a friend over a landline phone with no image transfer, your friend can talk back. Your friend can even talk back before you start describing. You can ask your friend what they need to know, what they want to know. You can do that beforehand. And then you can describe the image in exactly the way that your friend needs. In the Fediverse, you describe your images for potentially millions of Fediverse users and billions of Internet users. You can't first go around and ask them all, every last one of them, what they need to know and what they want to know. You have to perfectly cater to everyone's needs without even knowing anyone's actual needs because you can't know everyone's needs. Describing for one person over the phone is one-size-fits-one. It's tailor-made for one person. Describing in the Fediverse has to be one-size-fits-all at first try, right off the bat. This may not matter if you post a simple real-life cat photo. But I post renderings from super-obscure 3-D virtual worlds. Nobody knows what anything in my images look like until they can either see the images themselves, or I describe everything in these images to them. So this matters a whole lot in my case. #<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> Only that "my best" has actually led to unimaginable extremes. 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. Over 60,000 characters. 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. 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. 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. #<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://masto.nu/@bigpawedbear" rel="nofollow noopener" target="_blank">Big Pawed Bear</a> @<a href="https://mastoart.social/@elaterite" rel="nofollow noopener" target="_blank">Bob Tregilus</a> I beg to differ. You can't realistically do that in a Fediverse post <a href="https://hub.netzgemeinde.eu/item/21735784-8443-430a-aa09-e0d9d00a40c2" rel="nofollow noopener" target="_blank">as I've pointed out here</a> (that's actually a Fediverse post that you may be able to search for and find it on Mastodon). #<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=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. 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. 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. #<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://mstdn.ca/@JustinDerrick" rel="nofollow noopener" target="_blank">Justin Derrick</a> The question, however, is: What is "high-quality"? How is it defined? Would the bot go by the definition valid for commercial/scientific/technological websites and blogs, i.e. ideally no more than 125 characters, and only a short and concise visual description with no further information? Or would the bot go by Mastodon's culture and Mastodon's standards, i.e. the longer and more detailed, the better, any and all extra information is welcome in alt-text (because it doesn't fit into the toot), and the limit is 1,500 characters? That is, if it were for me, the bot would go look both for alt-texts and for image descriptions in the post text body and judge both. Because I do both at the same time for my original images. An extremely detailed long image description in the post itself (character limit for post and alt-texts combined here: over 16 million) that also comes with all necessary explanations and transcripts of all text in the image, plus an alt-text that's as detailed as 1,500 characters (minus notification about the long description in the post) allow, but with no explanations, and I usually have to leave out text transcripts as well because they're too many. You may say the alt-text is superfluous if it's just a much shorter version of the long description. But as long as the Mastodon HOA demands there be an alt-text to every image, no matter what (especially seeing as I always hide my image posts behind summaries/content warnings, so you can't see right of the bat that there's a long image description in the post), I add alt-texts to my original images. I'm actually curious about how the bot would judge my descriptions. Maybe it'd flag them "inadequate" because it notices that the bits of text in the image are not transcribed in the alt-text. Maybe it'd be irritated because I have headlines in my long image descriptions, because they're so long that they need two levels of headlines. Maybe it'd flag them "inadequate" because it goes strictly by WCAG, and a) the alt-texts exceed 200 characters, b) long image descriptions do not belong into the text body by any known official accessibility standards, and c) neither my alt-texts nor my long descriptions are limited to what's supposed to be important within the context of the post. Anyway, in the meantime, you can follow the account @<a href="https://mastodon.social/@alttexthalloffame" rel="nofollow noopener" target="_blank">Alt Text Hall of Fame</a> and the hashtag #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextHallOfFame" rel="nofollow noopener" target="_blank">AltTextHallOfFame</a>. CC: @<a href="https://mastodon.scot/@simon_brooke" rel="nofollow noopener" target="_blank">Simon Brooke</a> #<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=MastodonHOA" rel="nofollow noopener" target="_blank">MastodonHOA</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://beige.party/@OhOkKay" rel="nofollow noopener" target="_blank">🇨🇦 OhOkKay</a> <blockquote>Be kind, take a few extra seconds to share your image with everyone.</blockquote> Mind if I take a few days instead to describe one image and do some research for the description? <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener" target="_blank">My original images need an extremely high level of description detail.</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://c.im/@JosephMeyer" rel="nofollow noopener" target="_blank">Joseph Meyer</a> <blockquote>When you read exceptional alt text, do you ever compliment its author? What is the epitome of alt text, either in general terms or using a specific example?</blockquote> I'd really like to know that myself, also to up my own game further and always stay way ahead of image description quality requirements. I mean, <a href="https://hub.netzgemeinde.eu/item/1e63be04-d96e-412a-ab47-aff18c5f9ad8" rel="nofollow noopener" target="_blank">I've learned a lot about describing images in and for the Fediverse</a> over the last two years. But I guess I can still learn something new, even if I think I already take care of everything, even if the technical possibilities I have here on Hubzilla for describing images surpass those on Mastodon by magnitudes. Maybe, if I learn something new from those who reply, I can weave it into the image descriptions for a series of images that I've been working on since late last year (the descriptions, not the images which are ready to go). <blockquote>Alt text sometimes merely explains what I am viewing; other times it draws my attention to special details in a photo that I would have otherwise missed.</blockquote> I never explain in alt-text. I do always explain a whole lot because I always have to explain a whole lot. For my original images, it takes me over 1,000 characters alone to explain where an image was made. But I only ever give explanations in the long, detailed image descriptions that go into the post text body (in addition to shorter and purely visual descriptions in the alt-texts). Or if there's no additional long image description in the post itself which is the case for my meme posts, I still supply enough explanation in the post text body (still not in the alt-text) for just about everyone in the Fediverse to understand them without having to look anything up themselves. If I can link to external information, e.g. KnowYourMeme for the template I've used, I do so. If I can't, I write the missing explanations right into the post myself. #<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://mstdn.ca/@DavidM_yeg" rel="nofollow noopener" 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=ecoevo.social%40ecoevo.social" rel="nofollow noopener" target="_blank"></a><a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland?f=&zid=ecoevo.social%40ecoevo.social" rel="nofollow noopener" target="_blank">Jupiter Rowland</a> schrieb den folgenden <a href="https://hub.netzgemeinde.eu/item/21735784-8443-430a-aa09-e0d9d00a40c2?f=&zid=ecoevo.social%40ecoevo.social" rel="nofollow noopener" 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" target="_blank">accessibility group</a> @<a href="https://a.gup.pe/u/a11y" rel="nofollow noopener" target="_blank">a11y group</a> #<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=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> CC: @<a href="https://mstdn.ca/@monstreline" rel="nofollow noopener" target="_blank">Monstreline</a> @<a href="https://ohai.social/@i_cannot_today" rel="nofollow noopener" target="_blank">Claire (sometimes Carla)</a> @<a href="https://mstdn.social/@qurlyjoe" rel="nofollow noopener" target="_blank">qurly(not curly)joe</a> #<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=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

Recent searches

Search options

Administered by:

Server stats:

#ImageDescriptionMeta

Recent searches

Search options

Administered by:

Server stats:

imagedescriptionmeta

#ImageDescriptionMeta