Blind and Visually Impaired Community
↑
8
↓
Report any voiceover bugs two Apple (self.Blind)
submitted by Individual-Fan1639
I have been quite impressed with Apple responding to feedback or bug reports regarding the accessibility of voiceover. make sure that if you encounter a bug with voice over or you are not able to do something that someone else with vision can on their iPhone, then contact Apple and let them know. I would highly suggest to not just give a bug report, but also explain alternatives that are accessible or a better way you think things would work.
Contact them here: accessibility@apple.com
Contact them here: accessibility@apple.com
TTV_RosieRed99 6 points 1y ago
Apple been great with accessibility!
Individual-Fan1639 [OP] 3 points 1y ago
The best. I will be a customer for life with the new edition of voiceover recognition.
Fridux 0 points 1y ago
In my experience they do respond to E-mails but don't actually care about fixing the bugs. I've reported lots of bugs in Safari for MacOS 6 years ago that are yet to be fixed, and two years ago I reported a bug in every US MacOS voice except for Alex with long words in camel case that is also not fixed. Not only that but VoiceOver on the Mac seems to be getting worse, as now it doesn't even announce when your computer wakes up, and crashes if I try to interact with the terminal after resuming from sleep in Monterey.
Individual-Fan1639 [OP] 1 points 1y ago
With the last bug,
you have the terminal up, the screen goes to sleep, but then after you come back to it and enter your password to login, then you are saying it crashes upon login? Just VoiceOver crashes or what?
You have to be extremely specific when it comes to this. This is why I really would recommend you use screen recording and also your microphone to describe the issue as you are having it.
you have the terminal up, the screen goes to sleep, but then after you come back to it and enter your password to login, then you are saying it crashes upon login? Just VoiceOver crashes or what?
You have to be extremely specific when it comes to this. This is why I really would recommend you use screen recording and also your microphone to describe the issue as you are having it.
Fridux 1 points 1y ago
It wakes up from sleep, either with the password or with the fingerprint, and if I interact with the terminal in order to read character by character VoiceOver crashes and restarts. If instead I'm on a text editor like TextMate 2, the text cursor moves word by word instead of line by line when I press up and down and I have to manually restart VoiceOver.
There's also an annoying bug since at least Mojave where sometimes one of the arrow keys gets stuck; for over two years I thought this bug was a keyboard problem, but after buying an M1 Mac recently I realize that it's an actual bug since it also happens on this laptop.
There's also an annoying bug since at least Mojave where sometimes one of the arrow keys gets stuck; for over two years I thought this bug was a keyboard problem, but after buying an M1 Mac recently I realize that it's an actual bug since it also happens on this laptop.
Individual-Fan1639 [OP] 1 points 1y ago
So you are saying that you have the rotor set to read by, “word” and it is reading by, “line” instead? Odd..
Use of terminal is the least impressive when using voice over for me. I actually just read of another terminal based screen reader created by someone visually impaired, but have not yet used it. It is called, “tdsr”. You might want to try that!
If you could try to get a screen recording, then I will see if there is anything else I can do, but I will at least additionally pass it on to Apple with a completed bug report. The more reports that they receive on any given issue, the more serious they take it as it is impacting more and more users.
Use of terminal is the least impressive when using voice over for me. I actually just read of another terminal based screen reader created by someone visually impaired, but have not yet used it. It is called, “tdsr”. You might want to try that!
If you could try to get a screen recording, then I will see if there is anything else I can do, but I will at least additionally pass it on to Apple with a completed bug report. The more reports that they receive on any given issue, the more serious they take it as it is impacting more and more users.
Fridux 1 points 1y ago
No, in the case of editors like TextMate 2, the rotor has nothing to do with it, but for the record it's always set to Symbols so that I can quickly jump from function to function, and QuickNav is disabled.
Regarding the terminal, when the computer comes out of sleep and you interact by pressing Control+Option+Shift+Down all the way to the innermost element (which is a word), and then press Control+Option+Shift+Left or Right to read character by character, VoiceOver reads nothing, then if you press Control+Option+Left or Right to read word by word, VoiceOver simply crashes and restarts, resuming the expected behavior afterwards. I don't really have any other issues with Terminal that would justify downloading a third-party app; my only annoyance is with long output which I just pipe to TextMate.
The biggest problems for me are the navigation in Safari that makes reading and selecting code from technical documentation such as from Rust's standard library and crates a nightmare, which are long standing bugs that have never been fixed, and the issue with a random arrow key getting stuck sometimes.
Finally, as I said I don't think reporting obvious bugs to Apple is worth my time since they don't fix them anyway. When I reported the problem with the US voices I did like you said and sent a recording of the bug as well as some Swift code to demonstrate the problem wasn't specific to VoiceOver and they did absolutely nothing.
I can record a video of these things if you really want and post it to Youtube, but based on my experience I doubt that reporting these bugs again will lead to a useful outcome.
Regarding the terminal, when the computer comes out of sleep and you interact by pressing Control+Option+Shift+Down all the way to the innermost element (which is a word), and then press Control+Option+Shift+Left or Right to read character by character, VoiceOver reads nothing, then if you press Control+Option+Left or Right to read word by word, VoiceOver simply crashes and restarts, resuming the expected behavior afterwards. I don't really have any other issues with Terminal that would justify downloading a third-party app; my only annoyance is with long output which I just pipe to TextMate.
The biggest problems for me are the navigation in Safari that makes reading and selecting code from technical documentation such as from Rust's standard library and crates a nightmare, which are long standing bugs that have never been fixed, and the issue with a random arrow key getting stuck sometimes.
Finally, as I said I don't think reporting obvious bugs to Apple is worth my time since they don't fix them anyway. When I reported the problem with the US voices I did like you said and sent a recording of the bug as well as some Swift code to demonstrate the problem wasn't specific to VoiceOver and they did absolutely nothing.
I can record a video of these things if you really want and post it to Youtube, but based on my experience I doubt that reporting these bugs again will lead to a useful outcome.
Individual-Fan1639 [OP] 1 points 1y ago
I’m not following you about the bug with the voice. Could you explain it in more detail so I can try to replicate?
The last part about voiceover needing to announce when waking is exactly some thing you should email the accessibility team about.
Look, I am not saying that they are perfect, I am actually seeking help with litigation against them directly for accessibility just to speed things up.. but they are receptive, they will fix things. It helps though if they have an actual backlog of accessibility bugs or feedback.
The last part about voiceover needing to announce when waking is exactly some thing you should email the accessibility team about.
Look, I am not saying that they are perfect, I am actually seeking help with litigation against them directly for accessibility just to speed things up.. but they are receptive, they will fix things. It helps though if they have an actual backlog of accessibility bugs or feedback.
Fridux 1 points 1y ago
The voices bug is pretty simple: switch to a US voice other than Alex, such as Samantha or Samantha Compact, and have it read the following: "UIDocumentBrowserViewController". I didn't separate the characters, it's the speech synthesizer that, for some reason, decides to spell words longer than 30 characters, and this behavior has been happening since Mojave at least. If you do remove some characters like in "UIDocumentBrowserView" the bug doesn't happen. This is quite annoying because Apple's APIs tend to have extremely long identifiers, so every time I encounter one of those I either have to switch to Alex or move the cursor character by character, because even if spelling the identifier wasn't bad enough, it also ignores all the characters beyond the 30th.
Individual-Fan1639 [OP] 1 points 1y ago
Odd that Alex changes the behavior. Will email about this.
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.