When I close the lid of my MacBook and it goes to sleep, when I open the lid again, VoiceOver is disabled and I have to reenable it manually, however, VoiceOver was still on when I closed the lid, so it should still be on when opening it again. Can anyone else confirm this bug? Or am I missing a setting?
By Igna Triay, 22 July, 2022
Forum
Apple Beta Releases
Your Feedback is Important to Improving Accessibility on Apple platforms
Don't assume that Apple is aware of a bug or that your report won't make a difference - submitting bug reports directly to the company helps them reproduce and resolve the issue faster. Your report may provide crucial information. The more reports they receive, the higher the priority they give to fixing the bug.
If you're using a beta version, use the Feedback Assistant on your device to submit feedback and bug reports. If you're using a public release, follow the instructions on this page.
Comments
similar issue, but even worse.
Hi.
I can't use VoiceOver in the login screen, but after that it begins to speak.
Not seeing this here
I'm not seeing the specific issue that you describe.
However, for the past couple of years I typically find that if I open my MacBook's lid a few seconds after closing it, VoiceOver can take more than a minute to become responsive again.
This doesn't happen if the lid has been shut for anything more than 10 seconds or so, but it's darn irritating behaviour on those times when you close the lid and immediately think of something that you meant to do before leaving your computer🤷♂️
VoiceOver drastically changes in pitch
Hi all,
I haven't seen any of the behaviors described so far, but VoiceOver is drastically cnaging in pitch while reading text in Pages, TextEdit, websites etc. It's very low, but hwen reading items on the dock it's just fine. It's almost like it's unable to maintain pitch. I was using Fiona, my favorite voice, but I decided to use Alex to see if I'd experience the same issue, I am and it's almost worse. If anyone has a workaround please let me know. Restarting VoiceOver doesn't help.