@Nickiquote but they're fun!

@alttexthalloffame Yes, very true.

@jupiter_rowland I’d suggest, with love, the problem is that you are doing far, far more than anyone is asking of you. Have you considered using one of the hashtags that gets people to write the alt text for you?

@DamonWakes @Nickiquote it's funny, Google Lens actually does a good job of writing captions for things, I use it all the time to take pictures of things with Chinese text (like snacks that have a street scene with a banner that says "City God Temple Street") and then get into discussions about how they made up Chinese characters for chemical words like "Phenol" and "Aldehyde"...

@Nickiquote There you go.

@Author-ized L.J. That's the problem: Whatever I do, I'll lose either way.

On the one hand, I feel a great pressure to describe and explain everything in advance. That way, nobody would ever have to ask me to describe a detail or explain something. And nobody, not even the most die-hard Mastodon alt-text activists, could say that I'm careless and that I only do the very bare minimum or not even that. There are people out there who are eager to block everyone who doesn't describe their images enough or lecture them or attack them for being lazy.

The last time I've described an image for Hubzilla, I refused to write detailed descriptions for the images within that image. That would have escalated and cost me weeks to describe them all because I'd also have had to describe dozens of images within these images and even more images within these images. Mind you, someone who travels to the place I've described couldn't actually see what I'd have described because the images in my image themselves have a limited resolution. But I genuinely felt bad for not describing these images.

Besides, if I only described my original images once, namely in the alt-text, and then briefly and concisely, and if someone came and asked me to describe certain elements at greater detail, I couldn't always do that. Sometimes I couldn't go back to the place shown in the image and take a closer look and write a more detailed description because that place simply doesn't exist anymore, or it has been modified, and it doesn't look like the image anymore. The details that I'd have to take a closer look at are gone.

On the other hand, my experience is also that posting more than 500 characters at once reduces my reach on Mastodon tremendously. I think I must have over 700 or 800 followers, but my reach on Mastodon is similar to that of someone with not even a dozen followers. And I don't think that's because what I post is so uninteresting or because of my rather controversial thoughts about the Fediverse, accessibility in the Fediverse, image descriptions etc.

Basically, I can't possibly post images without risking being sanctioned by anyone.

I've briefly considered putting my long descriptions into separate HTML documents and linking to them. In theory, that would reduce the length of my image posts greatly. However, this is entirely untested. I don't know if it'd work at all, i.e. open the HTML document in someone's browser rather than downloading it to their device as a file. I don't know either if a plain HTML document with no style sheet would be accessible to screen reader users.

What I do know, though, is that Mastodon hates external links with a flaming passion. That's also because the vast majority of Mastodon users is always on phones, using dedicated Mastodon apps. They hate their browser popping open when they tap a link all the same. Also, they tend to distrust external links because the linked documents or pages may not be sufficiently accessible.

Everything would be a whole lot easier if there were Fediverse-wide standards for image descriptions that take the requirements of blind or visually-impaired people into consideration as well as Mastodon's unique culture. If these standards were known to everyone both on Mastodon and in the non-Mastodon Fediverse. If everyone from blind or visually-impaired users to neurodivergent users to fully sighted alt-text activists agreed upon these standards all the same. And if these standards covered extreme edge-cases like mine as well. If there was a generally agreed-upon consensus on a whole lot of questions like:

• Is it okay to have to ask for detailed descriptions of certain details in an image that don't matter within the context of the post?
  Or do they have to be described right away if there's a chance that someone might be curious about them? What if nothing specific in the image matters more within the context than everything else?
• Is it okay to have to ask for explanations if you don't understand the topic of an image?
  Or do images about very obscure niche topics have to come with enough explanations for everyone to understand them right away (not counting technical or jargon terms which always have to be either avoided or explained)?
• So there's the rule that all text within an image must be transcribed verbatim. How far does this rule go?
  Let's suppose I have a few dozen individual bits of text within an image. Most or all of them are so small that they're unreadable. Some are so tiny that they're actually invisible at the image's resolution. Still, technically speaking, they're there. And: I can read them. Instead of reading them in the image, I can read them at the source. So I can transcribe them all.
  What is the rule then?
  Do I have to transcribe them although they're unreadable because the rule says all text has to be transcribed?
  Do I have to transcribe them although they're unreadable because not doing so and writing that they're unreadable with no transcript is or may be considered lazy?
  Do I have to transcribe them because they're unreadable, and even fully sighted people need a transcript to know what's written there?
  Mustn't I transcribe them because they don't show themselves as text in the image at the image's resolution (if they actually don't)?
  Mustn't I transcribe them because I must only describe what's visible in the image at the image's resolution to the naked eye?
  Do I have to transcribe them in my special edge-case in spite of the two above lines because this might be my last and only chance to transcribe them, for they may be gone tomorrow, and I would no longer be able to transcribe them if someone asked for a transcript? Or must I remember to keep personal transcripts of all the texts I come across in my images, just in case someone asks for a transcript of a bit of text that no longer exists?
• Must all text transcripts always be in the alt-text as opposed to an extra long image description in the post? Even if I have 20+ individual text transcripts to squeeze into Mastodon's limit of 1,500 characters of Misskey's limit of 512 characters?
  Or is it okay to
  
  • transcribe them in a separate long description in the post text
  • not put these transcripts into the alt-text
  • mention in the alt-text that there is a long image description in the post, that all the texts in the image are transcribed there, and how exactly to find that long image description?
• If any of the above requires a separate long image description because the image description won't fit within the alt-text character limits, is it preferred for the long description to be in a linked document that will open in the browser (given one has the means to write and host such a document, and users on Hubzilla, (streams) and Forte do have these means)?
  Or must the long description be where the image is at all costs? Must it be in the post itself for the convenience of app users even if it inflates the post to a hyper-massive length to the inconvenience of Mastodon users?

Unfortunately, this would require some very extensive discussions on Mastodon, involving mostly Mastodon users. But Mastodon isn't fit for this kind of discussion or debate at all.

Worse yet: I've recently found out that none of the things above must be discussed on Mastodon. Ever. You must not discuss that stuff. You must do it. But you must do it right off the bat. For whichever individual definition of "right".

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #A11y #Accessibility