#imagedescriptionmeta — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #imagedescriptionmeta, aggregated by home.social.
-
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Mark Wyner Won’t Comply :vm: First of all, you completely forgot the social media posters. The TOC link leads nowhere.
Also, maybe it's fair to mention that I'm working on an entire wiki about alt-texts and image descriptions, especially for the Fediverse. 46 pages are planned as of now, 24 of them are already written. These will include over 30 pages on how to do things, how not to do things and what never to do at all.
I won't add step-by-step guides for certain frontends. But I've already started adding rules and guidelines for how to describe images appropriately and write alt-texts in a way that won't break stuff anywhere.
Even if it's a very incomplete WIP, it's unique in several ways:- It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
- It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
- It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
- It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
- It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
CW: How must foreign-language text be transcribed in an image description? CW: long (over 2,200 characters), alt-text meta, image description meta
I'm pretty sure that posting this will turn out completely futile. But I'll try anyway.
I'm especially asking the Mastodon alt-text enforcers: How must foreign-language text be transcribed, both by Web accessibility standards and by Mastodon's alt-text standards?
Let's assume I have some text in an image that's in a different language than the post and therefore in a different language than the image description. But I still have to transcribe it.
Now, according to image-describing rules, text must always be transcribed 100% verbatim. Word by word, character by character, exactly identical to the original in the image.
Here's the catch: Screen reader software may not be able to reliably switch the language in which they read out text in the middle of a description. They definitely cannot switch the language in the middle of an alt-text, I know that, just like they cannot navigate within alt-text.
This means that if I describe an image in English, but there's French text somewhere, a screen reader may read it out as gobbledygook instead of proper French. It may read the French text like it's English.
But even if the screen reader did read out the French text in proper French, someone who doesn't understand French won't understand the text.
This leaves me with two options:- Transcribe the foreign-language text verbatim, add a translation afterwards.
This would make the foreign-language text understandable, but it would also produce gobbledygook. - Give a translated transcript of the foreign-language text that's as close to the original as possible.
No gobbledygook, but I'd break the rule of always transcribing text verbatim.
The latter option would produce weird results if applied to a sign with essentially the same text in French, English and German where the French and German texts translate into something that slightly differs from both each other and the English text. I've happened upon this before.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #ScreenReader #ScreenReaders #ForeignLanguage #Inclusion #A11y #Accessibility - Transcribe the foreign-language text verbatim, add a translation afterwards.
-
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
@Prof. Rachel Thorn 🍉🇺🇦🏳️⚧️🏳️ Just out of curiosity: Are there any good excuses for not having added an alt-text that you'd accept?
For example, when someone new to Hubzilla tells you that they neither know what alt-text is nor how to add it? Hubzilla doesn't have dedicated UI elements for adding alt-texts. Images are embedded into posts like in blog posts rather than attached as files like on Mastodon. Alt-texts have to be manually woven into the image-embedding phpBB code, and the newbie might not know that this is explained in Hubzilla's built-in help, or it's simply too tedious to "program" an alt-text in.
Or when a Hubzilla veteran of over ten years tells you that Hubzilla has no way whatsoever to add an alt-text to a video? Like images, videos are embedded into posts. But the video-embedding code has no option for an alt-text. Granted, if it's a video, I'd rather expect or supply a full, time-coded transcript in the message text. But maybe what's expected is both a full, time-coded transcript and an alt-text that's sufficiently detailed by Mastodon's standards.
If neither of these are acceptable to you, there's something else you should know: Hubzilla does not support Mastodon's report feature either because that's a non-standard, homegrown Mastodon feature, and Hubzilla is not built against Mastodon. So if you report someone to their Hubzilla admin, the admin simply will never receive your report.
This is likely to lead Mastodon users into believing that either the server on the other end is unmoderated (which, in Hubzilla's case and by Mastodon's standards, is technically true because Hubzilla is all about self-moderation), or the admin doesn't care, both of which, by Mastodon's standards, is reason enough to have the server Fediblocked.
Again, I'm just being curious and cautious. You should not believe that I'm trying to weasel myself out of having to describe images.
After all, I'm working on an extensive wiki about image descriptions and alt-texts in the Fediverse with 50+ pages with dozens of webpages and blog posts on how to describe images. I'm using the same knowledge that I'm pouring into the wiki, the same rules and guidelines that already have or will have wiki pages, to describe my own images, even though some of them collide with each other and with Mastodon's image description preferences and quality standards. I don't think anyone else in the Fediverse is taking describing images more seriously.
I rarely post images anymore due to the effort involved. But whenever I do, I take all the effort that's needed to both describe and explain them, taking into consideration the context, Mastodon's culture and preferences regarding alt-texts and image descriptions, the potential target audience and what knowledge they may or may not have about what's in the image. I've declared all my existing image descriptions outdated, also because it'd be too tedious to go and upgrade them all whenever I learn something new about describing images. (Don't go looking for my most recent images on this channel; I post my images elsewhere now because Hubzilla can't make Mastodon blur sensitive images.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -
Jfc I got a lot of mileage out of one goddamn screenshot but hey!
My b/Blind and vision-impaired or sight-loss fellows shall feast tonight!… If any of you care about niche multi-layered terminology for humorous agenerational interconnective co-created commentary on base genuine media, surprises, commentary, and intersections of such!
You goddamn linguistic nerds!!
Ooh, I feel like https://www.youtube.com/watch?v=YrHGbCyAqOU is structurally related.
OMG. THAT’S HOW ADHD BRAINS CONNECT IDEAS.https://www.youtube.com/watch?v=cQKGUgOfD8U
AuHD or AudHD (urgh, I hate that initialism) people connect ideas by their structural relevance (and personal ascription of importance).
And, apparently, Neurotypical, neuro default, or neuro expected people connect ideas by narrative relevance! And, frankly, also how much importance they ascribe to the narrative, topic, or relevance.Omg I’m an edu blogger?! This is like finding out that non-binary gender was an option! Holy shit.
#EaseOfAccess #Alt #ALT4you #ALT4me #alt4u #altText #imgDesc #ImageDescriptionMeta #ImageDescriptionPostMeta #omg #AGAIN #thisCallsFor #CrusherP #Crusher #Vocaloid #metaCommentary #IdidNotKnow #itWasVocaloid #forYears #blind #BlindFedi #BlindMasto #vision #VisionLoss #eyes #eyesight #visible #visibility #sensory #sensoryImpairment #sensoryLimit #sensoryLoad #sensoryOverload #information #InformationTechnology #InformationOverload #info #InfoTech #EduBlogger