Podcast: Play in new window | Download
Subscribe: RSS
I recently discovered an article about speeding up audio messages, a feature that seems quite useful. Unfortunately, for those of us who rely on VoiceOver, this option is unavailable, as VoiceOver cannot access the control to adjust playback speed. You’re supposed to tap and hold the “play” button to bring up these options, but this doesn’t work with VoiceOver. We need to urge Apple to address this issue, as it remains unresolved in iOS 18.1.
The article also mentions the ability to rewind and fast forward through audio messages. Does anyone know if this is possible with VoiceOver? Please share your feedback or any workarounds you might have. You can find the referenced article here.
00:00:00,000 –> 00:00:01,464
By Jessica Dail.
2
00:00:01,464 –> 00:00:05,904
I read an article recently, outlining how to speed up audio messages.
3
00:00:05,904 –> 00:00:08,856
I didn’t even know that such a task was possible.
4
00:00:08,856 –> 00:00:14,064
However,for those,like myself,who rely entirely on VoiceOver,
5
00:00:14,064 –> 00:00:18,840
this feature is nonexistent,as VoiceOver doesn’t even see such control.
6
00:00:18,840 –> 00:00:23,256
You’re supposed to tap & hold the, “play” button to bring up these options.
7
00:00:23,256 –> 00:00:28,680
What can we do, to urge Apple to fix this, as its still broken under iOS 18.
8
00:00:28,680 –> 00:00:29,496
1.
9
00:00:29,496 –> 00:00:36,408
Another thing which the below,article mentions,is the ability to rewind & fast forward through audio messages.
10
00:00:36,408 –> 00:00:40,176
Any ideas on if or how this can be done with VoiceOver?
11
00:00:40,176 –> 00:00:47,616
The article I referenced for this can be found at: https://9to5mac.
12
00:00:47,616 –> 00:01:08,904
com/2024/06/19/adjust-playback-speed-imessage-audio/#:~:text=And%20here%E2%80%99s%20how%20to%20do%20it%3A%201%20Open,
13
00:01:08,904 –> 00:01:19,104
button%204%20Choose%20the%20playback%20speed%20you%20want Comment below,
14
00:01:19,104 –> 00:01:22,944
if you have any feedback,or if there is a workaround for this issue.