Voiceover quite slow to respond

By Yves Seguin, 24 January, 2023

Forum
iOS and iPadOS

After updating to IOS 16.3, I note the following behaviour; VoiceOver is quite slow to respond after a finger swipe (several seconds, up to 3). Anyone else experiencing this annoying behaviour? Needless to say that prior to the update, swiping would produce an immediate response from VoiceOver. Any help to remedy the situation will be greatly appreciated.
Thanks in advance.

Options

Comments

By Jo Billard on Tuesday, January 24, 2023 - 05:07

I haven't tried with other voices,, but I'm wondering if that may be the problem. Try using different voices. The only other thing I can think of is maybe your phone might be an older one. I've never had a phone at the very lowest model of support so I don't know if they do that, but computers can.

By Josh Kennedy on Tuesday, January 24, 2023 - 05:07

I just updated my iPhone 13 mini and voiceover is still nice and fast. Did you try turning off the phone and turning it back on? What model iPhonoe do you have?

By Yves Seguin on Tuesday, January 24, 2023 - 05:07

Thanks to Jo and Josh; I have an iPhone 13 Pro and to add to my original comment, swiping when Voiceover is off, the screen refreshes immediately as it should. When Voiceover is on, the screen also refreshes right away, but voiceover only speaks 2 to 3 seconds after swiping. I did turn the phone off and back on several times.

By Josh Kennedy on Tuesday, January 24, 2023 - 05:07

Maybe try using espeak or eloquence and see if it is faster? I am not having this issue.

By Aiutante_aiuta… on Tuesday, January 24, 2023 - 05:07

I had the same problem with Voice Over, to solve it, just turn off the Caption panel in the Voice Over settings

By ming on Tuesday, January 24, 2023 - 05:07

yeah I found it after updated to 16.3
I am using IPhone 12

By Patrick Hurst on Tuesday, January 24, 2023 - 05:07

Hi #Aiutante_aiutatore cieco:

Thank you for your useful tip! I tried the settings change you suggested and the problem seems to be gone!
So everyone in this discussion should try this workaround before considering contacting Apple Accessibility!