So, I know generative AI is supposed to be just the most incorrect thing ever, but I want you to compare two descriptions. "A rock on a beach under a dark sky." And: The image shows a close-up view of a rocky, cratered surface, likely a planet or moon, with a small, irregularly shaped moon or asteroid in the foreground. The larger surface appears to be Mars, given its reddish-brown color and texture. The smaller object, which is gray and heavily cratered, is likely one of Mars' moons, possibly Phobos or Deimos. The background fades into the darkness of space. The first one is supposed to be the pure best thing that isn't AI. Right? Like, it's what we've been using for the past like 5 years. And yes, it's probably improved over those years. This is Apple's image description. It's, in my opinion, the best, most clear, and sounds like the ALT-text that it's made from, which people made BTW, and the images it was made with, which had to come from somewhere, were of very high quality, unlike Facebook and Google which just plopped anything and everything into theirs. The second was from Be My Eyes. Now, which one was more correct? Obviously, Be My Eyes. Granted, it's not always going to be, but goodness just because some image classification tech is old, doesn't mean it's better. And just because Google and Facebook call their image description bullshit AI, doesn't mean it's a large language model. Because at this point in time, Google TalkBack does not use Gemini, but uses the same thing VoiceOver has. And Facebook uses that too, just a classifier. Now, should sighted people be describing their pictures? Of course. Always. With care. And having their stupid bots use something better than "picture of cats." Because even a dumb image classifier can tell me that, and probably a bit more, lol. Cats sleeping on a blanket. Cats drinking water from a bowl. Stuff like that. But for something quick, easy, and that doesn't rely on other people, shoot yeah I'll put it through Be My Eyes. #accessibility#AI#LLM#BeMyEyes#blind
@mutualaid I'm £0.10 short of my £9.49 phone bill this month, and it's due in 5 days. I'm trying to get some help to find a job, but until then, #MutualAid is all I can rely on.
Hey, if you don't like the fact that many #blind people have to rely on AI to describe images for them, you can help by, you know, describing images for them.
So fellow #blind#Android folks. I'm not as impressed with my Google Pixel Watch as I thought I would be, and am contemplating switching to a Samsung one. How #accessible are they with #Talkback? I have a #Pixel phone, in case that matters. Thanks in advance!
New instance, new introduction. Hello, I am Adam from Ottawa Canada. I am a totally blind man, identifying as he/him.
My primary interests are technology and music. I was a former professional drummer, playing the bar stages of Ottawa and the ocasional out-of-town show.
I've always been rhythmical, annoying the heck out of my parents at the tendor age of four on up banging on pots, pans, spoons, and whatever else I could get my grubby little hands on.
I got my first drum kit when I was 12, back in 1999. I got a couple of upgrades over the years, and then switched to electronic kits in 2007 when I managed to save and purchase a Roland TD-12 kit with my own money. That was like buying a car for me, LOL.
I was professionally active from 2007 until 2019.
Some hearing issues with extended loudness causing anxiety and unease started my issues with playing live shows, and then COVID19 really finished that career.
I've been interested in technology from a young age as well, receiving my first electronic note taker for the blind, a Blazie Engineering Braille Lite in 1996 at the age of 9.
I then got my first computer in the summer of 1998, learned DOS, then eventually Windows 3.1, 95, and on up.
I've had many, many, many computers and other technological devices since those days, and I have done any serious compute work in Linux, where in I am mostly referring to running servers, hosting things, and distributed compute projects.
Professionally, I am currently a systems/server administrator, backend web developer, database administrator, and infrastructure administrator.
Other interests include animals, documentaries, listening to most kinds of music, having deep intellectual conversations, and pondering the meaning of life. #Mastodon#Introduction#Ottawa#Canada#Blind#Music#Technology
Alright. Here's how it is. Once you appoint yourself as gatekeeper, you become part of the problem. We as #disabled people have precious few allies as it is, without actively alienating the ones we have. You can stand up and offer to help, stand up and provide constructive feedback on how to improve, stand up and show appreciation, or just sit your ungrateful self down. Just stop. Thanks @stefan for raising awareness of #AltText. #blind#accessibilityhttps://stefanbohacek.online/@stefan/112451222240570433
@stefan It occurrs to me that the #AltText hall of fame is not run by a #Blind or #VisionImpaired person because in the decades that alt text has been a thing, nobody from within this community has stopped to think that demonstrating how to do it well might be helpful for our cause. When an ally does it, we treat them like an intruder. Whatever. Enjoy your internet full of suboptimal alt text.
Just listened to my second podcast of the day 🎧, where the hosts are puzzled about who wants all this AI vision stuff they've seen this week. All they can come up with is blind people. Yes! Yes! Yes! We do! 🙌✨ #Blind#AI#TechForGood#Inclusion#Accessibility#ThisDayInAI#Verge
It's June 10, 2024, at 4:00 PM Central US time. Almost every blind person that owns an iPhone has installed the iOS 18 beta. Some are playing retro games with the new, AI driven screen recognition. Others are gladly using DecTalk as their main voice, the Enhanced Siri voices that use ML to speak using emotion and context, as their reading voice, Eloquence as their notification voice (sent to one ear to minimize distractions), and finding it amazing that VoiceOver emphasizes italic text, and emboldens bold text. Others are finding it amazing that they can navigate their whole phone using Braille screen input, searching to find things by typing a few letters, or just swiping down through everything. A few are connecting their multi-line Braille displays, and feeling app icons and images, made much more understandable through touch, using an AI filter.
The next day, when news of all these features filters down to Android users, they quickly begin hammering Google, wanting DecTalk and Eloquence on their Pixel phones, like iOS users have. But Google is silent as always, only just now having given Chromebook users high quality Google TTS voices.
Note: great liberty has been taken to imagine the coolest outcome for the vague feature announcements Apple gave for VoiceOver users. We'll see just how cool, or not, they actually are on June 10.
Chromebooks already have great screen reading capabilities built in...
Awww Google, how cute of you. Great? Nope. Next time, remember. Nothing about us, without us. ChromeVox has barely been updated in years, just like VoiceOver for Mac, and Narrator. ChromeVox barely has any options for fine-tuning verbosity, keyboard commands, pronunciation, and some keyboard commands, like Search + Control + A for accessibility actions, aren't even well-documented. I should know. I had to use an Acer Spin 713 for a good 3 months as my primary laptop. So kindly stop talking, then ask, then act before you speak further.
"Updated keyboard shortcuts and first-letters navigation in Google Drive"...
First letters navigation? Come on. Any blind person can tell that this wasn't written by anyone who uses these technologies.
And nowhere in this article is anything new for ChromeVox. See? This is the kind of, frankly, bullshit that I hate on GAAD. Just shut your mouth and listen for once.
Today is Global Accessibility Awareness Day (#GAAD). Today, I want you to ask yourself, then act, before you speak. Do you have an app you're maintaining? Look at some #accessibility resources for the framework you use for the user interface. Do you know if it's accessible or not? If it's not accessible, are you doing anything about it? Do you tell disabled visitors to your app/site that it's not accessible, and give them a timeframe, if any, when it will be? Do you have a website? If so, do you know if it's accessible or not? Are you an artist of any kind? Is your media accessible? Are you a writer? If so, are the images in your book described with #AltText?
If you're a part of a company that has anything to do with accessibility, including proudly posting about it, do you have any disabled employees? If so, do you show them that they're appreciated? If not, why don't you have any? If you create art about people with disabilities, do you have disabled people take a look at it before you share it? If you write books that have images in them, have any disabled people checked to make sure the Alt-text makes sense, and that the book is accessible otherwise? If not, why not? And when you get disabled people to check out apps, books, sites for your professional needs, do you pay them for it?
Please do remember us on every other day of the year, but particularly today, please remember: nothing about us without us.
I'd actually love to hear from actual #deaf or #hardOfHearing folks about what they think of this. It kinda looks gimmicky in a " who asked for this?" kind of way to me, but I'm a #blind person. I don't know if people have been looking for this but I'd really love to learn more :)
How do you feel about duplicate links in articles, blogs, whatever? Meaning: A certain word is a link (let's say "HEALTH") leading to an external website.
Would it annoy you if this word was always a link and it's mentioned for example 20 times in an article? Or would you rather have it only once to make it easier to scan for links?
I’m asking because it is really difficult to find a place for discussing accessibility in Fediverse posts beyond the limits of any one Fediverse server application....
I think a good approach could be to think about how you could reach users of different platforms.
A lot of Mastodon users follow hashtags, so including relevant hashtags (#accessibility and #blind seem like good starting points) might be a good idea. Tagging groups, such as @accessibility, might also help.
I think Kbin/Mbin might be better suited for this than Lemmy, as it integrates better with other federated networks. You can follow microbloggers and boost content, which in turn makes them likely to follow you back and creates a community beyond which Lemmy community you choose to post in. Your Mastodon followers will see your posts, but it won't matter to them which community you post it in.
It's hard for content to make the jump from Lemmy to Mastodon as Lemmy does not make itself discoverable, but as soon as content reaches Mastodon users nothing stops them from interacting with it (by boosting or replying).
Sadly Kbin.social lacks sufficiently active moderation these days, so you might be better off with an mbin instance. I also have no idea how accessible Mbin is to blind users.
Edit: I over-emphasized the point about reaching a broader audience. If you want to discuss a narrow topic but you don't want most ActivityPub users to see it because you don't value their input, I guess Lemmy is as good as it gets.
A lot of Mastodon users follow hashtags, so including relevant hashtags (#accessibility and #blind seem like good starting points) might be a good idea. Tagging groups, such as @accessibility, might also help.
As I’ve already said, for someone who is not on Mastodon, it’s pretty much worthless to try and discuss Fediverse post accessibility as applied on something that isn’t Mastodon with people who are on Mastodon. And Guppe is practically exclusively used by Mastodon users.
One example: Many Mastodon users have stuck in their heads that you can’t post more than 500 characters in the Fediverse. For even more Mastodon users, “alt-text” and “image description” are 100% mutually synonymous and mean the exact same thing. Image descriptions, no matter what they contain, always go into the alt-text. It’s like a law of physics, deviating from which is unimaginable.
If you talk about describing or explaining something in the post text body, whoosh, it flies over their heads. No matter how much sense that’d actually make.
Not to mention that you have to keep every post and every comment at 500 characters or below, otherwise a large number of Mastodon users will pretend you aren’t even there or mute or block you outright. I know that from personal experience. And there are things that simply can’t be discussed in glorified tweets.
Also, Mastodon seems to only know two kinds of pictures. One, screenshots of social media posts. The stuff that requires transcripts. Two, simple real-life photographs, especially cat pictures.
Edit: I over-emphasized the point about reaching a broader audience. If you want to discuss a narrow topic but you don’t want most ActivityPub users to see it because you don’t value their input, I guess Lemmy is as good as it gets.
Ideally, I’d discuss this topic with people from all over the Fediverse. And I want these people to discuss it with each other within the comments section. Mastodon users who really care a lot for accessibility, who want everyone’s needs to be catered to, and who are shooting for WCAG level AA, just as well as users of Pleroma, Akkoma, Misskey, Firefish, Iceshrimp, Sharkey etc. etc. who have much higher character limits in their post and users of Friendica, Hubzilla and (streams) who do not have a character limit.
I don’t just want a bunch of one-on-one discussions between myself and someone else. I want to discuss such matters with Mastodon users and non-Mastodon users, and I want the Mastodon users and the non-Mastodon users to read and reply to what the other side has written.
I want people on non-Mastodon projects to tell Mastodon users who only know Mastodon what things are like on other projects. I want Mastodon users to tell non-Mastodon users how important accessibility is and which aspects of accessibility is how important. And I want to learn from this discussion.
I want to read opinions and ideas from all over the Fediverse. And I want users from all over the Fediverse to read these opinions and ideas.
And in particular, I want to discuss with them edge-cases in accessibility that go far, far beyond Twitter/Mastodon screenshots and cat photographs.
A few more notes about video games and VoiceOver Recognition: the story mode of Blazblue reads very well with screen recognition, even better than Windows OCR! In some games, when menus have descriptions, you can tell which menu item you're on by the description of the item at the bottom. With the Provinence app, audio latency is amazingly low with my AirPods Pro 2. So, playing games using those is really, really amazing! No game mode needed! I can't wait for more blind people to get into this! #accessibility#blind#gaming#Provinence#iOS#RetroGames#emulation#emulators
I see a lot of #Blind people ‘apologizing’ for using #AI – I am not going to be doing that. Not now and not ever.
We need to have a conversation about how these models have been trained and how they are used going forward, but shaming disabled people for taking any chance they can to mitigate some of the challenges they face in their lives every day, is a ‘privilege’ we don’t all enjoy.
When you post an image and choose not to add alt text, publish an inaccessible PDF, release an inaccessible app - these are all choices! Maybe a tiny part of the righteous outrage that some of these people are spewing could be aimed at that?
For discussing Fediverse accessibility, where would you recommend me to go? Or stay here?
I’m asking because it is really difficult to find a place for discussing accessibility in Fediverse posts beyond the limits of any one Fediverse server application....