Follow

Linux folks, if you're writing documentation and stuff, consider how screen readers will pronounce the terms you use? Who's heard of ini tramps? That's as close as I can get to how screen readers pronounce initramfs. I had no idea what it meant until recently. Have espeak or espeak-ng(1) read out your docs. Yes, it sounds awful. Wanna help with that too?

@devinprater Yes lets change the names of everything to please the small number of people that use screen readers

@asa Did I say change the name? Nope. For the initramfs case, just capitalize each subword. InitRamFS.

@devinprater I like it the way it is, u guys that use screen readers could make a dictionary plugin kinda thing where X string is pronounced as Y
@devinprater I hope so too, not trying to be rude is just that the amount of people that need that is really really small and I think software could solve the issue very well for those that need it, instead of changing the text for everyone else, by the way are you listening to this text?

@asa Yes, I am. Also software can fix the issue, but the user would have to know what something means before they can fix it. Like I didn't understand initramfs until I figure out the three things that make up the word. Also not all screen readers have pronounciation dictionaries. Yes that's the screen readers' fault, but it's how it is.

@devinprater It's an interesting thing I never thought about, I guess it doesn't hurt to capitalize words differently.

I don't know how you type but your grammar and punctuation is better than most people here, we tend to be sloppy about it.

Also It's cool to know that the words I'm writing are being spoken by a robotic voice somewhere, I hope I sound good.

@asa You sound okay, pretty articulate. I learned to touch type in like middle school, and read a lot.

Do ereaders include a translation database? Can’t really change the name of initramfs but could you include a translation table if ereaders support them that initramfs is pronounced “init ram eff ess” instead?

@gme Some of them do. one pronunciation dictionary I use now just capitalizes the subwords, so it uses InitRamFS.

Since UNIX/Linux is case-sensitive though unfortunately documentation can't employ CamelCase or other capitalization strategies. `InitRamFS` doesn't exist on a Linux filesystem unfortunately. Sounds like a good open-source project would be for the community to come up with a pronunciation table for screen readers to correctly pronounce nouns and words that aren't in a standard dictionary.

@devinprater But an initramfs is actually a thing, so it’s not unusual to have it in a doc, and totally legit. The issue is more on espeak side, than on the doc.

@devinprater Funnily enough, _humans_ often can't pronounce these terms either! I wouldn't know how to vocalize 'initramfs' unless someone told me.

@devinprater I just go letter by letter and add it to my orca pronunciation settings if I feel like it. More often, I don't add it and this happens: https://pleroma.envs.net/notice/AIvWzBN27WNT0p9Hs0

@Seirdy Oh, looked at your bio. Fedora? It's not unstable for you? Hmm, maybe it's my system. Maybe Linux doesn't support the AMD 5500?

@devinprater quite the opposite, it's too stable. which is why i sometimes mess around with rawhide.

@Seirdy Wow. For me, Chrome would crash out of nowhere, and Pidgin would crash when I'm writing a message more than like 50 chars long.

@devinprater Yeah. I used to have a number of emojis in my name until I had a conversation with someone using a screenreader. I got to hear what it told them every time I sent a message, and it was just painful hearing it read aloud half a dozen emoji names, every. single. message. Over and over.

My suggestion:
If your user name has a ton of emojis/special characters, remove them and replace with a simple word or two that can actually be pronounced by a screen reader.

#accessibiity

@Blort @devinprater Emoji's in nicknames/display names should be forbidden anyway 😅

@devinprater One potential sollution could be an HTML tag that allows documentation authors (and anyone else who wants to use it) to write how it should be pronounced by screen readers, while also displaying how it should be written. This is kinda like what Microsoft Agent allows people to do to force Agent to use the correct pronunciation of a word it might not recognize.

Sign in to participate in the conversation
Light space

A home where one can be themselves.