komadori: Kisa from Fruits Basket with the caption "I'll turn my courage into wings." (Default)
[personal profile] komadori
Hey everyone, I am a screen reader user, and I would love to know if there's anyone making icons and posting them with image descriptions. I know a lot of people add image descriptions to their personal icons, and I am grateful for that. Please keep doing that or start if you don't already. I was just wondering if there are creators or communities that regularly make icons with image descriptions because I would like to have some options for finding new icons aside from looking through ones used by my flist.

Also, I realize that this request is somewhat hypocritical since I don't have image descriptions for my icons currently. Would any sighted fans mind describing them for me? I found them many years ago when I had more vision, so I know roughly what they look like, but I thought it might help to have them described more precisely. If no one is able to do it, I can always ask a sighted person in real life.

(no subject)

Tue, May. 14th, 2019 02:04 am
soc_puppet: Miraculous Ladybug; the design from the Cat Miraculous: A green cat pawprint on a black field (Cat Noir)
[personal profile] soc_puppet
My current fandom, Miraculous Ladybug, originated in France and takes place in Paris. While there is an English dub available, the majority of the fandom uses the French name for one of the main character's superhero identity - most likely because the French version was available before the English dub was, and fandom adopted the French name early on. (The other superhero's name was always in English.)

The problem with this? The superhero's French name is Chat Noir; in French, it's pronounced shah.

Is there a way to indicate to screenreaders how a specific word is supposed to be pronounced? Or that it's in a different language? A bit of HTML or something? A possible skin on AO3, or a way for me to make one myself? I personally am planning to stick to the English name either way, but I'd love if there was at least an option to give the rest of the fandom.

Edit: To clear things up a bit: I wanted to know if there's a way to indicate for other people's screenreaders how a specific words is pronounced, or if it should be considered in a different language. So someone posting something here to Dreamwidth, or on AO3, can write it "Chat", but a screenreader will either read it as the French pronunciation or as "Cat".

It's entirely likely that I'm looking for a difficult solution when an easy one will do, or where one isn't needed (I'm sure most folks using screenreaders figure out what's what pretty quick, and again, I'm sticking to the English name myself), but I thought it might be worth asking.
runpunkrun: portion of koch snowflake fractal, text: snow fractal (Default)
[personal profile] runpunkrun
Hi folks, I need some help with making the author commentaries I've written compatible with screen readers. Author commentaries are story texts that have paragraphs of commentary inserted into them. In the two I've written, the only way to differentiate between story and commentary is visually and I'd like to fix that. Here's how my commentary for "Meanwhile, Back in Metropolis" is currently formatted using css. Paragraphs of commentary are set off from the story by a blue background, which I'm sure a screen reader couldn't care less about. I could easily create a div class "commentary" for those sections, but I don't know if screen readers typically announce that sort of information.

So my question is: How can I set apart the commentary sections in a satisfactory way for fans with screen readers?

Googling, I found Designing for Screen Reader Compatibility, which describes how to hide content visually while still making it available to screen readers. I could add "Commentary:" in hidden text in front of every section of commentary. But would it have to be in front of every paragraph, or is once a div enough? Would it be helpful to have a hidden "end commentary" text as well?

I only have a basic understanding of how screen readers work, so if there's a simple solution that I've overlooked, it's probably because I didn't realize it was an option. I'd appreciate your input and any suggestions you might have. I know that not everyone uses their screen reader in the same way.

Thank you for your help.

November 2025

S M T W T F S
       1
2 345678
9101112131415
16171819202122
23242526272829
30      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags