Also related to the Lemmy software: good support of the Markdown language means everyone can add alt-text to images (which wasn't possible on Reddit, Reddit was by design not blind friendly).
this post was submitted on 01 Jul 2023
85 points (97.8% liked)
Blind Main
479 readers
5 users here now
The main community at rblind.com, for discussion of all things blindness.
You can find the rules for this community, and all other communities we run, here: https://ourblind.com/comunity-guidelines/ Lemmy specifics: By participating on the rblind.com Lemmy server, you are able to participate on other communities not run, controlled, or hosted by us. When doing so, you are expected to abide by all of the rules of those communities, in edition to also following the rules linked above. Should the rules of another community conflict with our rules, so long as you are participating from the rblind.com website, our rules take priority. Should we receive complaints from other instances or communities that you are repeatedly, knowingly, and maliciously breaking there rules, we may take moderator action against you, even if your posts comply with all of the rblind.com rules linked above.
founded 1 year ago
MODERATORS
good support of the Markdown language means everyone can add alt-text to images
Nice! I want to try an experiment to see how it sounds:
What is above should be the rBlind.com logo. I am curious how different screen readers will pick it up. Below is the markdown I used:
For me it just says "unlabeled" :(
I'm using Android TalkBack on Thunder, which is very much still in beta. It would be wonderful if the internet was more accessible.
I'm not actually visually impaired, but I find tts much more comfortable for reading in bed. Accessibility features improve things for everyone!
For me it just says “unlabeled”...I’m using Android TalkBack on Thunder
Might just be Thunder. Jerboa seems to read it okay with TalkBack on Android, for me at least, as does Jaws with Chrome on Windows
Works on iOS with Safari as well.
Absolutely. While alt text for image posts is still necessary, you can add it in images in text posts.
For transcriptions, do you think it would be a best practice for users to add them to the alt text, the post body, or post comments? I'm guessing alt text would be most salient for screen reader ergonomics, but not as widely noticeable for errors, bias, or omissions, like with titles. Body text would be more commonly viewed, and thus held to more scrutiny and correction. Comment text would be easiest to track corrections or revisions on transcriptions, but not as discoverable if buried in the comments.
Given the facilities we have here, I’d go with short alt text and a longer description in the body. That way, screen reader users know what’s in the image, but everybody gets the explanation and context.
Welcome to the fed guys. Out of interest, how do you guys consume content? This big app war made gave awareness of how bad reddit was for you guys, so i'm just interested in learning.
Are you able to have text posts be read out to you and such? Glad you have the tools here to enjoy the content! Welcome.
Are you able to have text posts be read out to you and such?
I cannot tell you what they use for administration and moderation but for reading Jerbao has been working great with TalkBack on Android, Chrome has been doing well with JAWS on Windows, and Orca okay with Firefox on Debian...but Orca can often be more of a stretch for a lot of things.
The only thing that would be on my wish list would be better defined key bindings/shortcuts for the web UI...maybe even have the bindings listed in the labels of controls...they are absent for me when using carat browsing on Chrome Canary
The apps have to properly support accessibility APIs, but the text to speech (or Braille!) part is handled by software called screen readers. All OSs have them built in.