Everything is labeled.

  • AlmightySnoo 🐢🇮🇱🇺🇦@lemmy.world
    link
    fedilink
    English
    arrow-up
    23
    ·
    edit-2
    1 year ago

    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).

    • NoConfidence_2192@rblind.com
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      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:

      rBlind.com logo

      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:

      ![rBlind.com logo](<https://rblind.com/pictrs/image/3c46ae70-6ceb-4e6d-bb6e-5822e9426176.png?format=webp&thumbnail=96> "rBlind.com logo")
      
      • poweruser@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        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!

        • NoConfidence_2192@rblind.com
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          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

      • ruffsl@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        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.

        • MostlyBlindGamer@rblind.comM
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          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.

  • simo@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    1 year ago

    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.

    • NoConfidence_2192@rblind.com
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      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

    • MostlyBlindGamer@rblind.comM
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      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.