Blind and Visually Impaired Community
↑
8
↓
[deleted by user] (self.Blind)
submitted by [deleted]
[removed]
Criptedinyourcloset 2 points 1y ago
It usually handles line breaks, periods, and things like that pretty well. Parentheses is where it gets a little bit choppy. It really will not acknowledge them. With jaws the most you’ll get is it speaking the parentheses out loud. With voiceover I don’t even think it does that. I think if you want to give natural sounding speech. You should just use a more line breaks and things like that. If you used to many punctuation marks. Especially with drawls speaking every single punctuation. It’s way too hard to listen to and makes me wanna jam pencils up my ears because it’s too much information at once. also, both screen readers will acknowledge? So that’s fine. If you want to emphasize something. Just capitalize a few letters here and there. Punctuation points will not be acknowledged at all. Unless you put multiple after a sentence.
[deleted] [OP] 2 points 1y ago
[deleted]
Criptedinyourcloset 1 points 1y ago
No. It usually will not say the sentence any differently unless you capitalize the entire word. In which case, Josh will see the word a little bit higher pitched. Most of the blind people I know do not really mind if punctuation is emphasized or not. The only ones we really care about are?‘s. And besides, how many times are you going to be putting!‘s in business emails?
Marconius 1 points 1y ago
Using title case anywhere in a sentence doesn't have any effect on the overall way it is read, unless a user navigates through it character by character. Screen readers will tend to change the voice pitch when encountering a capital character, but only in character navigation. Do not use all caps at all. Screen readers can get confused between all caps words and initialisms/abbreviations, so sometimes it will spell out a capitalized word rather than reading it normally.
Also, if you happen to write about variable names and such in code, camel case is wonderful and is read clearly by screen readers, whereas the older convention of putting underscores between multi-word variable names gets super annoying and tedious to listen to.
Also, if you happen to write about variable names and such in code, camel case is wonderful and is read clearly by screen readers, whereas the older convention of putting underscores between multi-word variable names gets super annoying and tedious to listen to.
Criptedinyourcloset 1 points 1y ago
My gosh yes. It’s the absolute most annoying thing on earth. You end up listening to a name that should take a few seconds to listen to. It takes more than 10 seconds and can be really annoying. I’ll be on YouTube or some thing and some guy in the comments will have a bunch of little letters made a really weird. For example, some will be circumflex, some will be in Greek, things like that. And it ends up taking forever just to read the name.bMy gosh yes. It’s the absolute most annoying thing on earth. You end up listening to a name that should take a few seconds to listen to. It takes more than 10 seconds and can be really annoying. I’ll be on YouTube or some thing and some guy in the comments will have a bunch of little letters made a really weird. For example, some will be circumflex, some will be in Greek, things like that. And it ends up taking forever just to read the name
retrolental_morose 1 points 1y ago
as kind an impulse as this is, realistically its not on you to change the way you write. Obviously if you pepper your emails with emoji which may be open to interpretation things would be different, but the way in which a screen reader user chooses to interpret punctuation is a very personal choice. Stick to culturally accepted norms for written business communication and satisfy the majority.
blind_cowboy 1 points 1y ago
It’s also going to depend on each person’s screen reader settings. For example, when I am proof reading, I’ll set JAWS to read all punctuation and caps during a say all. I usually have punctuation on some and caps off.
This nonprofit website is run by volunteers.
Please contribute if you can. Thank you!
Our mission is to provide everyone with access to large-
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
©2023 HumbleCat Inc • HumbleCat is a 501(c)3 nonprofit based in Michigan, USA.