With the recent news that the r/blind community has migrated to a lemmy instance, I thought now would be a good time to post a quick PSA on image descriptions.

Blind and low vision computer users often rely on screen readers to navigate their computers and the internet. These tools work great on text-based platforms (when the backend is coded correctly to make buttons and UI elements visible to the screen reader), but they struggle a lot with images. OCR and image recognition have come a long way, but they’re still not reliable.

On Lemmy, there’s no way (yet) to add alt text to image posts, but one thing that we sighted folk can do to make the website a more accessible place for the blind/low vision community is to describe the contents of the image in text, so screen readers (or braille displays) can interpret the text for the user. This doesn’t need to be anything fancy - you can see an example of me doing so in this post here - simply indicate somewhere that you are describing the contents of the image, and then do so in text. If you’re transcribing text, it’s best to do so as exact to the text in the image as you can (including spelling errors!). If you’re describing something visual, it’s best to keep it about the length of a tweet, but be as detailed as you need to be to give context to what you write about in the post.

If you’d like a more detailed guide on how to best do image descriptions and alt text, here’s a site that describes more specifics - https://www.perkins.org/resource/how-write-alt-text-and-image-descriptions-visually-impaired/

Edit: You are able to add alt text to embedded images, as noted by @sal@mander.xyz here. This would only work for images within the text of your comment, not for image posts (topics which link to images).

Edit 2: @retronautickz@beehaw.org wrote a post on kbin on best practices in writing image descriptions and alt text.

  • Retronautickz@beehaw.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Apart from adding alt text (which someone in another comment has already explained how), I want to add other ways to help Blind and visually impaired people and other people that require the use of screen readers and text to speech apps (like myself)

    • When using tags with more than one word, always write the first letter of each word in uppercase so the screen readers and text-to-speech apps can read them as separate words

    #/LikeThis and not #/likethis

    • Avoid special fonts as they cannot be detected by screen readers and TTS software. Most of the time the letters are actually phonetic or mathematical symbols and the software interpret them as such.
  • Retronautickz@beehaw.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’ve written a microblog post explaining how to describe images on my kbin account for those who aren’t sure/don´t know how to write image descriptions.

    Be free to ask any question you may have.

  • techno156@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    If it’s not already there, it might also be worth raising the issue on the lemmy-ui github, just so the developers can see it, and can add to the list of features to implement. If it’s important enough, they can bump it up the list as needed.

  • Salamander@mander.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I think that you can add captions to images, like this:

    ![image caption](image url)

    I wonder whether these tools would identify and read out the caption.

  • Nepenthe@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    If anyone here has some info on how to adequately include conversational dialogue, I’d really appreciate it.

    I’ve done some reading on it once I realized kbin, at least, has that option, but I can’t find anything on this topic apart from “Try not to repeat information.” Which I think is implying I shouldn’t mention the speakers’ names more than once? I’m kind of winging it here as best I can.

    • retronautickz@fedi196.gay
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago
      • Transcribe all text.

      • Explain differences in font, size, style, and case.

      • Explain the direction/order of the text.