#alttexts — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #alttexts, aggregated by home.social.
-
@lhgmk2 Don't let the cynicism overtake your heart, my friend. I understand your views on alt texts, but at the same time, visually impaired people do exist.
-
@lhgmk2 Don't let the cynicism overtake your heart, my friend. I understand your views on alt texts, but at the same time, visually impaired people do exist.
-
@lhgmk2 Don't let the cynicism overtake your heart, my friend. I understand your views on alt texts, but at the same time, visually impaired people do exist.
-
For those who enjoy reading #AltTexts on images, and who used to hover over images to see them, be advised that Mastodon 4.4 has changed how you access them as a sighted/mouse-using user:
Just click the little "alt" badge in the bottom-right corner of the image.
-
For those who enjoy reading #AltTexts on images, and who used to hover over images to see them, be advised that Mastodon 4.4 has changed how you access them as a sighted/mouse-using user:
Just click the little "alt" badge in the bottom-right corner of the image.
-
For those who enjoy reading #AltTexts on images, and who used to hover over images to see them, be advised that Mastodon 4.4 has changed how you access them as a sighted/mouse-using user:
Just click the little "alt" badge in the bottom-right corner of the image.
-
For those who enjoy reading #AltTexts on images, and who used to hover over images to see them, be advised that Mastodon 4.4 has changed how you access them as a sighted/mouse-using user:
Just click the little "alt" badge in the bottom-right corner of the image.
-
For those who enjoy reading #AltTexts on images, and who used to hover over images to see them, be advised that Mastodon 4.4 has changed how you access them as a sighted/mouse-using user:
Just click the little "alt" badge in the bottom-right corner of the image.
-
over it, rarely actually use the same consideration they demand of me over #AltTexts, by not capitalizing their hashtags correctly, which makes screen readers, used by the same visually challenged people, that they claim they are supporting, by attacking me.
Another example that they arent actually concerned about the issue and are just virtue signalling.
7/7
-
over it, rarely actually use the same consideration they demand of me over #AltTexts, by not capitalizing their hashtags correctly, which makes screen readers, used by the same visually challenged people, that they claim they are supporting, by attacking me.
Another example that they arent actually concerned about the issue and are just virtue signalling.
7/7
-
over it, rarely actually use the same consideration they demand of me over #AltTexts, by not capitalizing their hashtags correctly, which makes screen readers, used by the same visually challenged people, that they claim they are supporting, by attacking me.
Another example that they arent actually concerned about the issue and are just virtue signalling.
7/7
-
over it, rarely actually use the same consideration they demand of me over #AltTexts, by not capitalizing their hashtags correctly, which makes screen readers, used by the same visually challenged people, that they claim they are supporting, by attacking me.
Another example that they arent actually concerned about the issue and are just virtue signalling.
7/7
-
@dbattistella no, usually video #AltTexts are to describe what's visually happening, not what's being said.
-
@dbattistella no, usually video #AltTexts are to describe what's visually happening, not what's being said.
-
@dbattistella no, usually video #AltTexts are to describe what's visually happening, not what's being said.
-
2/2
¹ As in for example disability
² Which might already be happening anywayI've noticed that some people can be unkind to those who did not add an alt text.
Some people don't know about it, some might not be able to, staying constructive & friendly is the best way to achieve more #alttexts :)
This post was inspired by:
https://mas.to/@mcdutchie/113993819929651241@autoperipatetikos & @mcdutchie
I hope this is helpful to you & others like you :) -
2/2
¹ As in for example disability
² Which might already be happening anywayI've noticed that some people can be unkind to those who did not add an alt text.
Some people don't know about it, some might not be able to, staying constructive & friendly is the best way to achieve more #alttexts :)
This post was inspired by:
https://mas.to/@mcdutchie/113993819929651241@autoperipatetikos & @mcdutchie
I hope this is helpful to you & others like you :) -
2/2
¹ As in for example disability
² Which might already be happening anywayI've noticed that some people can be unkind to those who did not add an alt text.
Some people don't know about it, some might not be able to, staying constructive & friendly is the best way to achieve more #alttexts :)
This post was inspired by:
https://mas.to/@mcdutchie/113993819929651241@autoperipatetikos & @mcdutchie
I hope this is helpful to you & others like you :) -
2/2
¹ As in for example disability
² Which might already be happening anywayI've noticed that some people can be unkind to those who did not add an alt text.
Some people don't know about it, some might not be able to, staying constructive & friendly is the best way to achieve more #alttexts :)
This post was inspired by:
https://mas.to/@mcdutchie/113993819929651241@autoperipatetikos & @mcdutchie
I hope this is helpful to you & others like you :) -
2/2
¹ As in for example disability
² Which might already be happening anywayI've noticed that some people can be unkind to those who did not add an alt text.
Some people don't know about it, some might not be able to, staying constructive & friendly is the best way to achieve more #alttexts :)
This post was inspired by:
https://mas.to/@mcdutchie/113993819929651241@autoperipatetikos & @mcdutchie
I hope this is helpful to you & others like you :) -
@kura @Natanox yes the edit post part is weirding me out.
I mean I know not every shitpost will get #AltText / #ImageDescription, but if the OP can't even edit & copypasta #AltTexts provided by someone in reply then that's really bad...
-
@kura @Natanox yes the edit post part is weirding me out.
I mean I know not every shitpost will get #AltText / #ImageDescription, but if the OP can't even edit & copypasta #AltTexts provided by someone in reply then that's really bad...
-
@kura @Natanox yes the edit post part is weirding me out.
I mean I know not every shitpost will get #AltText / #ImageDescription, but if the OP can't even edit & copypasta #AltTexts provided by someone in reply then that's really bad...
-
@Chloe Tse :BlobhajSadReach: @Konaburd That's because not few #Mastodon users, especially newbies, haven't understood what these hashtags mean. It's even worse when they think they have.
So for everyone out there:- #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
- #Alt4You is for replies with alt-text upon posts with pictures without alt-text.
Feel free to boost this like crazy so that at least a few more people get it. - #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
-
@Chloe Tse :BlobhajSadReach: @Konaburd That's because not few #Mastodon users, especially newbies, haven't understood what these hashtags mean. It's even worse when they think they have.
So for everyone out there:- #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
- #Alt4You is for replies with alt-text upon posts with pictures without alt-text.
Feel free to boost this like crazy so that at least a few more people get it. - #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
-
@Chloe Tse :BlobhajSadReach: @Konaburd That's because not few #Mastodon users, especially newbies, haven't understood what these hashtags mean. It's even worse when they think they have.
So for everyone out there:- #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
- #Alt4You is for replies with alt-text upon posts with pictures without alt-text.
Feel free to boost this like crazy so that at least a few more people get it. - #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
-
@Chloe Tse :BlobhajSadReach: @Konaburd That's because not few #Mastodon users, especially newbies, haven't understood what these hashtags mean. It's even worse when they think they have.
So for everyone out there:- #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
- #Alt4You is for replies with alt-text upon posts with pictures without alt-text.
Feel free to boost this like crazy so that at least a few more people get it. - #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
-
@Chloe Tse :BlobhajSadReach: @Konaburd That's because not few #Mastodon users, especially newbies, haven't understood what these hashtags mean. It's even worse when they think they have.
So for everyone out there:- #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
- #Alt4You is for replies with alt-text upon posts with pictures without alt-text.
Feel free to boost this like crazy so that at least a few more people get it. - #Alt4Me is for everyone, sighted or not, who can't write their own #AltTexts but who cares enough to want to have #AltText on their images.
-
@[email protected] How about you add some #AltTexts / #ImageDescriptions to your posts.
You certainly have the time to #watermark them, then you also have the resources to write #AltText / #ImageDescription for it!
#NoAltTextNoBoost #NoImageDescriptionNoBoost
:boost_declined:
-
@Radical_EgoCom How about you add some #AltTexts / #ImageDescriptions to your posts.
You certainly have the time to #watermark them, then you also have the resources to write #AltText / #ImageDescription for it!
#NoAltTextNoBoost #NoImageDescriptionNoBoost
:boost_declined:
-
@Radical_EgoCom How about you add some #AltTexts / #ImageDescriptions to your posts.
You certainly have the time to #watermark them, then you also have the resources to write #AltText / #ImageDescription for it!
#NoAltTextNoBoost #NoImageDescriptionNoBoost
:boost_declined:
-
(Follow-up to this post)
Professional Web designers would probably shake their heads at the atrocity that's a full-blown #ImageDescription in #AltText. Detailed #ImageDescriptions do not even belong into alt-text. The only reason why they're in alt-text on #Mastodon is because alt-text has enough room for them, and toots themselves don't. And the only reason why they're in alt-text elsewhere in the #Fediverse is because someone has learned all they know about alt-text and image descriptions from Mastodon. I'll get back to that.
Another issue with alt-text is that there are people who cannot access it. Some mobile apps have no way of displaying alt-text. Desktop Web browsers based on Chromium are lacking in this department, too, as far as I've read; I'm a Firefox user myself.
And there are Fediverse users with physical disabilities that render them incapable of, for example, hovering a mouse cursor over an image to access its alt-text. Others may still use older #ScreenReaders that can't handle alt-text longer than 200 characters. Or if their screen readers are newer, they can only rattle down alt-text in one go, but they can't, for example, go back to some specific point in the alt-text. In this regard, image descriptions in alt-text are the opposite of #accessibility, long and detailed ones even more so.
These Fediverse users, as well as professional Web designers, say that detailed image descriptions belong into the text body.
Now, all you Mastodon users who read this may say that this is just plain impossible with that 500-character limit. It's impossible on Mastodon because Mastodon is so limited. It'd take a thread of four, five, six or more toots to put a long image description into toots while the same image description would fit into alt-text perfectly well.
Absolutely everywhere else in the Fediverse, this doesn't matter. Only Mastodon has this extremely low and hard-coded limit. If an instance admin wants to change it, they have to essentially fork Mastodon and edit the source code.
#MissKey has a default limit of 3,000 characters; #Firefish, formerly known as #CalcKey, has at least that many. #Pleroma and #Akkoma have a default limit of 5,000 characters, and so does #GoToSocial. #Friendica, #Hubzilla and what resides in the #Streams repository have what amounts to an unlimited character count with actual limits way up in the tens of thousands of characters.
Also, on instances of these projects, the limits are not hard-coded but admin settings instead. They're likely to vary from instance to instance.
All these projects allow as long #AltTexts as Mastodon or even longer alt-texts. On Friendica, Hubzilla and (streams), alt-text is part of the post, so it's virtually unlimited itself. But with such high character counts for posts, it no longer makes sense to put image descriptions into alt-text if the post itself has twice as much space as the alt-text or even more.
There is no technical reason not to put image descriptions into the post body. If anything, it's a question of style; it isn't always elegant to shove a massive image description into a post. But otherwise, putting it into alt-text has no advantage over putting it into the post body where it actually belongs.
In fact, if it's longer than 1,500 characters, it should never go into alt-text, regardless of how much alt-text you can write on your instance. That's because all projects that limit alt-text to 1,500 characters cut off longer alt-texts at 1,500 characters. Posts that are longer than the limit, however, are never cut off. Even Mastodon can handle and display 15,000-character posts from Hubzilla without cutting off the last 14,500 characters. Trust me, I've tried that.
(To be continued...) -
(Follow-up to this post)
Professional Web designers would probably shake their heads at the atrocity that's a full-blown #ImageDescription in #AltText. Detailed #ImageDescriptions do not even belong into alt-text. The only reason why they're in alt-text on #Mastodon is because alt-text has enough room for them, and toots themselves don't. And the only reason why they're in alt-text elsewhere in the #Fediverse is because someone has learned all they know about alt-text and image descriptions from Mastodon. I'll get back to that.
Another issue with alt-text is that there are people who cannot access it. Some mobile apps have no way of displaying alt-text. Desktop Web browsers based on Chromium are lacking in this department, too, as far as I've read; I'm a Firefox user myself.
And there are Fediverse users with physical disabilities that render them incapable of, for example, hovering a mouse cursor over an image to access its alt-text. Others may still use older #ScreenReaders that can't handle alt-text longer than 200 characters. Or if their screen readers are newer, they can only rattle down alt-text in one go, but they can't, for example, go back to some specific point in the alt-text. In this regard, image descriptions in alt-text are the opposite of #accessibility, long and detailed ones even more so.
These Fediverse users, as well as professional Web designers, say that detailed image descriptions belong into the text body.
Now, all you Mastodon users who read this may say that this is just plain impossible with that 500-character limit. It's impossible on Mastodon because Mastodon is so limited. It'd take a thread of four, five, six or more toots to put a long image description into toots while the same image description would fit into alt-text perfectly well.
Absolutely everywhere else in the Fediverse, this doesn't matter. Only Mastodon has this extremely low and hard-coded limit. If an instance admin wants to change it, they have to essentially fork Mastodon and edit the source code.
#MissKey has a default limit of 3,000 characters; #Firefish, formerly known as #CalcKey, has at least that many. #Pleroma and #Akkoma have a default limit of 5,000 characters, and so does #GoToSocial. #Friendica, #Hubzilla and what resides in the #Streams repository have what amounts to an unlimited character count with actual limits way up in the tens of thousands of characters.
Also, on instances of these projects, the limits are not hard-coded but admin settings instead. They're likely to vary from instance to instance.
All these projects allow as long #AltTexts as Mastodon or even longer alt-texts. On Friendica, Hubzilla and (streams), alt-text is part of the post, so it's virtually unlimited itself. But with such high character counts for posts, it no longer makes sense to put image descriptions into alt-text if the post itself has twice as much space as the alt-text or even more.
There is no technical reason not to put image descriptions into the post body. If anything, it's a question of style; it isn't always elegant to shove a massive image description into a post. But otherwise, putting it into alt-text has no advantage over putting it into the post body where it actually belongs.
In fact, if it's longer than 1,500 characters, it should never go into alt-text, regardless of how much alt-text you can write on your instance. That's because all projects that limit alt-text to 1,500 characters cut off longer alt-texts at 1,500 characters. Posts that are longer than the limit, however, are never cut off. Even Mastodon can handle and display 15,000-character posts from Hubzilla without cutting off the last 14,500 characters. Trust me, I've tried that.
(To be continued...) -
(Follow-up to this post)
Professional Web designers would probably shake their heads at the atrocity that's a full-blown #ImageDescription in #AltText. Detailed #ImageDescriptions do not even belong into alt-text. The only reason why they're in alt-text on #Mastodon is because alt-text has enough room for them, and toots themselves don't. And the only reason why they're in alt-text elsewhere in the #Fediverse is because someone has learned all they know about alt-text and image descriptions from Mastodon. I'll get back to that.
Another issue with alt-text is that there are people who cannot access it. Some mobile apps have no way of displaying alt-text. Desktop Web browsers based on Chromium are lacking in this department, too, as far as I've read; I'm a Firefox user myself.
And there are Fediverse users with physical disabilities that render them incapable of, for example, hovering a mouse cursor over an image to access its alt-text. Others may still use older #ScreenReaders that can't handle alt-text longer than 200 characters. Or if their screen readers are newer, they can only rattle down alt-text in one go, but they can't, for example, go back to some specific point in the alt-text. In this regard, image descriptions in alt-text are the opposite of #accessibility, long and detailed ones even more so.
These Fediverse users, as well as professional Web designers, say that detailed image descriptions belong into the text body.
Now, all you Mastodon users who read this may say that this is just plain impossible with that 500-character limit. It's impossible on Mastodon because Mastodon is so limited. It'd take a thread of four, five, six or more toots to put a long image description into toots while the same image description would fit into alt-text perfectly well.
Absolutely everywhere else in the Fediverse, this doesn't matter. Only Mastodon has this extremely low and hard-coded limit. If an instance admin wants to change it, they have to essentially fork Mastodon and edit the source code.
#MissKey has a default limit of 3,000 characters; #Firefish, formerly known as #CalcKey, has at least that many. #Pleroma and #Akkoma have a default limit of 5,000 characters, and so does #GoToSocial. #Friendica, #Hubzilla and what resides in the #Streams repository have what amounts to an unlimited character count with actual limits way up in the tens of thousands of characters.
Also, on instances of these projects, the limits are not hard-coded but admin settings instead. They're likely to vary from instance to instance.
All these projects allow as long #AltTexts as Mastodon or even longer alt-texts. On Friendica, Hubzilla and (streams), alt-text is part of the post, so it's virtually unlimited itself. But with such high character counts for posts, it no longer makes sense to put image descriptions into alt-text if the post itself has twice as much space as the alt-text or even more.
There is no technical reason not to put image descriptions into the post body. If anything, it's a question of style; it isn't always elegant to shove a massive image description into a post. But otherwise, putting it into alt-text has no advantage over putting it into the post body where it actually belongs.
In fact, if it's longer than 1,500 characters, it should never go into alt-text, regardless of how much alt-text you can write on your instance. That's because all projects that limit alt-text to 1,500 characters cut off longer alt-texts at 1,500 characters. Posts that are longer than the limit, however, are never cut off. Even Mastodon can handle and display 15,000-character posts from Hubzilla without cutting off the last 14,500 characters. Trust me, I've tried that.
(To be continued...) -
(Follow-up to this post)
Professional Web designers would probably shake their heads at the atrocity that's a full-blown #ImageDescription in #AltText. Detailed #ImageDescriptions do not even belong into alt-text. The only reason why they're in alt-text on #Mastodon is because alt-text has enough room for them, and toots themselves don't. And the only reason why they're in alt-text elsewhere in the #Fediverse is because someone has learned all they know about alt-text and image descriptions from Mastodon. I'll get back to that.
Another issue with alt-text is that there are people who cannot access it. Some mobile apps have no way of displaying alt-text. Desktop Web browsers based on Chromium are lacking in this department, too, as far as I've read; I'm a Firefox user myself.
And there are Fediverse users with physical disabilities that render them incapable of, for example, hovering a mouse cursor over an image to access its alt-text. Others may still use older #ScreenReaders that can't handle alt-text longer than 200 characters. Or if their screen readers are newer, they can only rattle down alt-text in one go, but they can't, for example, go back to some specific point in the alt-text. In this regard, image descriptions in alt-text are the opposite of #accessibility, long and detailed ones even more so.
These Fediverse users, as well as professional Web designers, say that detailed image descriptions belong into the text body.
Now, all you Mastodon users who read this may say that this is just plain impossible with that 500-character limit. It's impossible on Mastodon because Mastodon is so limited. It'd take a thread of four, five, six or more toots to put a long image description into toots while the same image description would fit into alt-text perfectly well.
Absolutely everywhere else in the Fediverse, this doesn't matter. Only Mastodon has this extremely low and hard-coded limit. If an instance admin wants to change it, they have to essentially fork Mastodon and edit the source code.
#MissKey has a default limit of 3,000 characters; #Firefish, formerly known as #CalcKey, has at least that many. #Pleroma and #Akkoma have a default limit of 5,000 characters, and so does #GoToSocial. #Friendica, #Hubzilla and what resides in the #Streams repository have what amounts to an unlimited character count with actual limits way up in the tens of thousands of characters.
Also, on instances of these projects, the limits are not hard-coded but admin settings instead. They're likely to vary from instance to instance.
All these projects allow as long #AltTexts as Mastodon or even longer alt-texts. On Friendica, Hubzilla and (streams), alt-text is part of the post, so it's virtually unlimited itself. But with such high character counts for posts, it no longer makes sense to put image descriptions into alt-text if the post itself has twice as much space as the alt-text or even more.
There is no technical reason not to put image descriptions into the post body. If anything, it's a question of style; it isn't always elegant to shove a massive image description into a post. But otherwise, putting it into alt-text has no advantage over putting it into the post body where it actually belongs.
In fact, if it's longer than 1,500 characters, it should never go into alt-text, regardless of how much alt-text you can write on your instance. That's because all projects that limit alt-text to 1,500 characters cut off longer alt-texts at 1,500 characters. Posts that are longer than the limit, however, are never cut off. Even Mastodon can handle and display 15,000-character posts from Hubzilla without cutting off the last 14,500 characters. Trust me, I've tried that.
(To be continued...) -
(Follow-up to this post)
Professional Web designers would probably shake their heads at the atrocity that's a full-blown #ImageDescription in #AltText. Detailed #ImageDescriptions do not even belong into alt-text. The only reason why they're in alt-text on #Mastodon is because alt-text has enough room for them, and toots themselves don't. And the only reason why they're in alt-text elsewhere in the #Fediverse is because someone has learned all they know about alt-text and image descriptions from Mastodon. I'll get back to that.
Another issue with alt-text is that there are people who cannot access it. Some mobile apps have no way of displaying alt-text. Desktop Web browsers based on Chromium are lacking in this department, too, as far as I've read; I'm a Firefox user myself.
And there are Fediverse users with physical disabilities that render them incapable of, for example, hovering a mouse cursor over an image to access its alt-text. Others may still use older #ScreenReaders that can't handle alt-text longer than 200 characters. Or if their screen readers are newer, they can only rattle down alt-text in one go, but they can't, for example, go back to some specific point in the alt-text. In this regard, image descriptions in alt-text are the opposite of #accessibility, long and detailed ones even more so.
These Fediverse users, as well as professional Web designers, say that detailed image descriptions belong into the text body.
Now, all you Mastodon users who read this may say that this is just plain impossible with that 500-character limit. It's impossible on Mastodon because Mastodon is so limited. It'd take a thread of four, five, six or more toots to put a long image description into toots while the same image description would fit into alt-text perfectly well.
Absolutely everywhere else in the Fediverse, this doesn't matter. Only Mastodon has this extremely low and hard-coded limit. If an instance admin wants to change it, they have to essentially fork Mastodon and edit the source code.
#MissKey has a default limit of 3,000 characters; #Firefish, formerly known as #CalcKey, has at least that many. #Pleroma and #Akkoma have a default limit of 5,000 characters, and so does #GoToSocial. #Friendica, #Hubzilla and what resides in the #Streams repository have what amounts to an unlimited character count with actual limits way up in the tens of thousands of characters.
Also, on instances of these projects, the limits are not hard-coded but admin settings instead. They're likely to vary from instance to instance.
All these projects allow as long #AltTexts as Mastodon or even longer alt-texts. On Friendica, Hubzilla and (streams), alt-text is part of the post, so it's virtually unlimited itself. But with such high character counts for posts, it no longer makes sense to put image descriptions into alt-text if the post itself has twice as much space as the alt-text or even more.
There is no technical reason not to put image descriptions into the post body. If anything, it's a question of style; it isn't always elegant to shove a massive image description into a post. But otherwise, putting it into alt-text has no advantage over putting it into the post body where it actually belongs.
In fact, if it's longer than 1,500 characters, it should never go into alt-text, regardless of how much alt-text you can write on your instance. That's because all projects that limit alt-text to 1,500 characters cut off longer alt-texts at 1,500 characters. Posts that are longer than the limit, however, are never cut off. Even Mastodon can handle and display 15,000-character posts from Hubzilla without cutting off the last 14,500 characters. Trust me, I've tried that.
(To be continued...) -
👆Do you read #AltTexts? (well, I do!)
If you said no, check out this one above. I try to make it enjoyable for all. 😂❣️(it’s nothing too special, but I add details in there often. also, I’m promoting others to write good ones, not just “a forest” sort of description.😉) -
👆Do you read #AltTexts? (well, I do!)
If you said no, check out this one above. I try to make it enjoyable for all. 😂❣️(it’s nothing too special, but I add details in there often. also, I’m promoting others to write good ones, not just “a forest” sort of description.😉) -
👆Do you read #AltTexts? (well, I do!)
If you said no, check out this one above. I try to make it enjoyable for all. 😂❣️(it’s nothing too special, but I add details in there often. also, I’m promoting others to write good ones, not just “a forest” sort of description.😉) -
👆Do you read #AltTexts? (well, I do!)
If you said no, check out this one above. I try to make it enjoyable for all. 😂❣️(it’s nothing too special, but I add details in there often. also, I’m promoting others to write good ones, not just “a forest” sort of description.😉) -
👆Do you read #AltTexts? (well, I do!)
If you said no, check out this one above. I try to make it enjoyable for all. 😂❣️(it’s nothing too special, but I add details in there often. also, I’m promoting others to write good ones, not just “a forest” sort of description.😉) -
hey
people that needs or find #alttexts usable
how in depth should they be?
like, is adding *a picture of a meme* useful, or just plain wasted text when you can understand it from context?
is there anythings else that would improve your experience?
-
CW: How I approach my #AltText game.
@dgar 1 ...
For a few days now I am contemplating a toot about this topic.
I usually take the effort to describe in detail what is in a photo. Once on the Bluebird site I read a tweet from a blind person who asked for better descriptions in #AltTexts and explained also what screen readers are capable of and what not - for example, if there are only emojis in the handle/nickname of the tweeter, the screen reader cannot say what it means.
... 2
-
CW: How I approach my #AltText game.
@dgar 1 ...
For a few days now I am contemplating a toot about this topic.
I usually take the effort to describe in detail what is in a photo. Once on the Bluebird site I read a tweet from a blind person who asked for better descriptions in #AltTexts and explained also what screen readers are capable of and what not - for example, if there are only emojis in the handle/nickname of the tweeter, the screen reader cannot say what it means.
... 2
-
CW: How I approach my #AltText game.
@dgar 1 ...
For a few days now I am contemplating a toot about this topic.
I usually take the effort to describe in detail what is in a photo. Once on the Bluebird site I read a tweet from a blind person who asked for better descriptions in #AltTexts and explained also what screen readers are capable of and what not - for example, if there are only emojis in the handle/nickname of the tweeter, the screen reader cannot say what it means.
... 2
