@Tom Cole It is available everywhere AFAIK.

But: The convenient black "Alt" button in the corner is exclusive to Mastodon's Web interface plus maybe a few phone apps that have adopted it since. Technically speaking, a UI element to show alt-texts is completely unnecessary because alt-text is only a stand-in for the image itself, for when the image cannot be seen for whichever reason. The alt-text as an extra source of information is a purely Mastodon thing where people use it to expand their meagre 500-character limit by up to another 6,000 characters.

Just about everywhere else in the Fediverse, there is no button for showing alt-texts. That's also because there's nowhere in the Fediverse where people really need alt-texts to write around their tiny character limits, so that alt-texts can be what alt-texts are literally everywhere outside of Mastodon: a stand-in for the image and nothing more than that.

The normal way in the Fediverse (and other social networks and social media) for sighted people to access an alt-text is by moving the mouse cursor upon the image and hovering in there, and the alt-text pops up. The alt-text is the title tag at the same time. This has been the case on Mastodon before, I think, version 4.4 as well. I guess Mastodon changed that because just about everyone on Mastodon is on phones, and you don't have a mouse cursor on a phone, so you have to long-press on the image which is a not very intuitive thing to do.

Here on Hubzilla where I'm commenting from right now, the alt-text still is the title tag as well. In order to read an alt-text, the mouse cursor has to be hovered above the image. And Hubzilla has no alternative to its Web interface, only different themes for the Web interface. There is no phone app, at least none worth speaking of.

Also, on Hubzilla, we don't need to use alt-texts to write around character limits. Our character limit is 16,777,215, and that's the maximum size of the database field for the message text. Actually, on Hubzilla, alt-texts are included in these over 16 million characters as opposed to separate data fields. Thus, sighted Hubzilla users have no use for alt-texts whatsoever. Thus, there's no reason to make opening alt-texts easier (as if that was Hubzilla's only UI issue). Thus, there's no "Alt" button, and there will never be one.

It's just about the same just about everywhere else from Misskey (hard-coded 3,000 characters) to Akkoma (configurable 5,000 characters) to Friendica (same limit as Hubzilla) to (streams) and Forte (over 24 million characters) to pure long-form blogging stuff like WordPress, Ghost, Write Freely and Plume.

Now I ask you: What are people supposed to do whose both hands had to be amputated due to some accident? Or people with deformed hands who can neither use a smartphone nor a computer mouse nor a trackball nor any other pointing device on a computer? Who operate their computer with e.g. a headpointer, a plastic stick strapped to their forehead with which they poke the keys on their computer? And who are in the Fediverse, but not on Mastodon? How are they supposed to open an alt-text with only a keyboard as an input device?

Or how about people with a severe tremor? Who have big troubles moving a mouse cursor over an image and then keeping it there because it keeps slipping away? Who probably operate their computers via the keyboard and only the keyboard, too?

Or, a wholly different example, how about those who use Linux with a super-minimalist, keyboard-only tiling window manager? Who do have a GUI (albeit a very frugal one), who do use graphical Web browsers, but who deliberately, intentionaly, do not have any kind of pointing device? Who, nonetheless, are ten times faster with only keyboard shortcuts than you and me are with a mouse? How are they supposed to move a mouse cursor over an image without a mouse?

This is something that many Mastodon users don't know:
  • Not all Fediverse frontends have an "Alt" button.
  • "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
  • There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
  • Not everyone in the Fediverse uses a pointing device of whichever sorts.

Oh, and there's one more thing: Misskey and its various forks (Sharkey, Iceshrimp-JS, CherryPick etc.) all have a character limit of 512 for alt-texts. They should enforce it the same way as Mastodon enforces its 1,500-character limit for alt-texts, namely by truncating longer alt-texts. This is bad enough already.

However, they all have the same nasty bug that still hasn't been fixed yet AFAIK: Instead of truncating longer alt-texts, they delete them. So if you describe your image in an alt-text of more than 512 characters, users on Misskey, Sharkey & Co. will never know that your image is supposed to have an alt-text. Instead, they may think that you were too lazy to describe your image. And if you use the alt-text to explain your image in over 512 characters, this explanation will never reach users on Misskey, Sharkey & Co.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #i3 #i3wm #Disability #A11y #Accessibility
Netzgemeinde/Hubzilla

@Fluse The two channels that I have for posting images have no reach whatsoever anyway. Describing the images won't change that.

Still, I put more time and effort into describing (and explaining) my images than anyone else.

#AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Netzgemeinde/Hubzilla

[image description]

A cartoon by Cathy Wilcox.

In the foreground is Penny Wong, speaking at a podium.
"We call in the Israeli government not to treat the Samud flotilla activists the way they treat Palestinians"

The background shows two photos, one of the activists from the flotilla, kneeling with their heads down while the vessel was being boarded by Israeli forces. The second photo is of Palestinian people imprisoned and trapped in a razorwire covered cage.

#AltText4U #Alt4You #imagedescription

@cathywilcox

@DopeGhoti @Andrew How many characters would be sufficient for Mastodon to not count as ableist anymore?

If you say, 1,500, who or what says that 1,500 characters are sufficient to describe any and all images, but a lower limit is not?

For comparison, look at my cover photo. The one with the weird building. I have a post with just about the same image in it; here's the link.

In this post, the image has two separate image descriptions. One is in the alt-text. The alt-text is exactly 1,500 characters long, a bit over 1,400 of which are image description. And that's the short description. It doesn't even have room for any text transcripts. It actually isn't much more than an "alibi description". It's only there because many people on Mastodon demand there be a 100% accurate and sufficiently detailed image description in the alt-text of each image in the Fediverse.

Only that "sufficiently detailed" isn't always possible even in 1,500 characters.

That's why there is an additional long description in the post text. It's sufficiently detailed, as in, fully detailed. An image like this requires a fully detailed description. It comes with transcripts of all bits of text within the borders of the image, and it comes with all explanations necessary to understand the image and the description. It's over 60,000 characters long.

Yes, over 60,000 characters in one post. Your character limit is 500. Mine is over 16 million.

Oh, and yes, it's guaranteed to be 100% hand-written. It took me two full days, morning to evening, to research for and write the long description with literally absolutely no help from any AI whatsoever. In fact, I've described details that no AI on the planet will ever be able to see in the image.

So ideally, all Fediverse server platforms should have two image description fields for each profile image, one being the alt-text behind the image, one being a long description next to the image. The latter should not have an arbitrarily-chosen character limit.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta
Universal Campus: The mother of all mega-regions

OpenSim's famous Universal Campus and a picture of its main building; CW: long (62,514 characters, including 1,747 characters of actual post text and 60,553 characters of image description)

Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?

Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.

So you write a short image description for your alt-text. That should be much better than nothing.

But then you're criticised and sanctioned because your image description lacks detail.

Since you can't or don't want to write a longer description, you leave that to an AI.

But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.

Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.

And still, someone may come and criticise and/or sanction you for having left out certain details.

If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.

Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.

There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.

Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.

Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.

As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.

Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.

Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.

But I hope that nobody can say I haven't tried hard enough.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Jupiter Rowland - [email protected]

Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?

Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.

So you write a short image description for your alt-text. That should be much better than nothing.

But then you're criticised and sanctioned because your image description lacks detail.

Since you can't or don't want to write a longer description, you leave that to an AI.

But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.

Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.

And still, someone may come and criticise and/or sanction you for having left out certain details.

If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.

Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.

There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.

Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.

Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.

As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.

Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.

Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.

But I hope that nobody can say I haven't tried hard enough.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Jupiter Rowland - [email protected]

@Roknrol Well, I'm kind of afraid of being sanctioned for alt-texts that lack text transcripts, even if the additional long image description in the post text contains them. I mean, the rule says that text must always be transcribed, and the transcripts must always go into the alt-text. That, and not everyone may want to wade through a long description of 20,000 to 60,000 characters to read the transcripts.

Also, I go as far as transcribing more than 20 individual bits of text within one image, only two of which are actually halfway readable at the given resolution. About a dozen of these bits of text can be found in an area that's five pixels tall and a dozen pixels wide in the image. The individual bits of text are so tiny at this resolution that they're invisible in the image. And yet, I transcribe them because, technically, they're still within the borders of the image.

But as long as you don't say I could and should try harder...

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts
Netzgemeinde/Hubzilla

@Jecture It's hard to do that in the Fediverse if the only place where people know, much less care about images being described is Mastodon. I have to single such people out and mention them.

I don't think that I've explicitly been told to shorten my short descriptions in the alt-text and, at the same time, ditch the additional long descriptioins in the post text, at least not by blind or visually-impaired users.

On the other hand, I've been told by a neurodivergent user that they've actually read through a ca. 40,000-character image description of mine, and that they've really needed this level of detail of information to get the image.

I know that accessibility professionals recommend alt-texts to be 200 characters at most, and they don't even take long descriptions in the text body itself into consideration.

But my images are nothing like whatever may go onto professional websites or blogs. And if I take all the rules and guidelines for image descriptions into consideration at the same time (and I do, at least I try, even though they sometimes contradict each other), I can't possibly describe my images adequately only once and then in 200 characters or fewer.

Also, describing images for a professional website is different from describing images for corporate social media.

Which is different from describing images on Mastodon for Mastodon.

Which is different from what I'm doing: describing images in a place with virtually no character limits (seriously, I could post 24 million characters at once), but for an audience that's largely on Mastodon and living by Mastodon's culture.

And there are no guidelines for the latter, much less steadfast rules.

Seriously, a 500-character alt-text may be vastly too long for a professional website where it must not exceed 200 characters. The same alt-text for the same image may be criticised as insufficiently detailed when posted to Mastodon where the image should rather be described in 800-1,200 characters. Such are the differences.

Not to mention that there are no guides on how to properly and adequately describe images with extremely obscure contents (e.g. 3-D virtual world renderings) to a Mastodon audience that doesn't know diddly-squat about what the images show, but that may or may not be super-curious about it.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Netzgemeinde/Hubzilla

@Roknrol I don't post social media app screenshots.

When I post memes, I only transcribe the pieces of text that are important within the context, but I do transcribe all of them.

I hope it's okay to leave out bits of text that don't matter in this case.

On the other hand, when I post original images, I transcribe every last bit of text within the borders of the image that I can read at the source, regardless of whether it's readable in the image at the resolution at which I'm going to post it.

I hope that's okay, too. And I hope it's okay that these transcripts only go into the long image description in the post text and not into the alt-text where there isn't enough space for them.

Also, I've yet to find a way to correctly transcribe things like text in other languages or text in multiple languages or misspellings, seeing as text must normally be transcribed 100% verbatim.

And I wonder if I can get away with deviating from transcribing 100% verbatim in the cases of all caps, misspellings, multiple paragraphs, quotation marks in the transcribed text and the like.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts
Netzgemeinde/Hubzilla