Apple will publicly release iOS 17 and iPadOS 17 on Monday, September 18, 2023. This post contains a summary of new bugs impacting VoiceOver, Braille support, and low vision features that we have identified during testing of these upcoming releases. We have also included details on previously reported bugs that appear to be fixed in iOS 17 and iPadOS 17 based on our testing.
As is our routine practice, each newly identified bug has been given a severity rating. These ratings are based upon what we believe to be the implications for accessing and using features and functionality for the average user, the level of impact on the overall user experience, and whether or not there is an effective workaround for the issue. However, as these ratings are subjective, it is possible that they may not reflect your own opinion or use case.
With our small team, it's impossible to test every device, configuration, app, and use case. We can't claim our bug list is comprehensive or that our assessments are infallible. Some issues may manifest only under specific conditions. You likely won't experience every bug. Also, expect to encounter problems not listed that we missed in our testing.
We strongly recommend reading this full post and replies before updating. This will help you make an informed decision on whether to install iOS 17 and iPadOS 17 when they become available or to wait for a future release.
To ensure the information here is as complete and accurate as possible, we welcome comments below from those who have installed iOS 17 or iPadOS 17. Please confirm if you are encountering the same problems listed or if you have found workarounds. Please also let us know about any additional issues not mentioned here. Of course, it's even more important that you report any new bugs directly to Apple - they are already aware of the ones listed here. [For an explanation of why and how to report bugs to Apple, see this post.
With all of the preamble out of the way, here are the new bugs for blind and low vision users which we believe to be present in iOS 17 and iPadOS 17:
Serious Bugs
Some users may encounter an intermittent issue that affects the operation of the VoiceOver double-tap gesture on iOS 17. When attempting to double-tap an actionable interface element, the resulting behaviour experienced is as if the user touched with 1 finger the area of the screen where they performed the gesture, rather than performed a double tap on the element that VoiceOver focus was on.
For instance, with VoiceOver focus on a button within Safari's toolbar, performing a double tap might result in VoiceOver speaking the text content of the webpage that was under your finger at the time you performed the gesture, instead of activating the intended button in the toolbar.
When this behaviour occurs, VoiceOver focus typically moves to the interface element that was spoken. It's necessary to relocate focus back to the intended element before attempting the double-tap again. While this movement of focus may sound similar to the longstanding issue for many users involving VoiceOver focus, the issue described here is new and noticeably different when experienced.
This issue is not limited to specific apps; it occurs across native and third-party applications. It impacts various types of actionable interface elements, including activating items on the VoiceOver rotor's action menu.
In some cases, the double tap might function correctly on the second attempt, while in others, it might require multiple tries before registering accurately.
The underlying issue can also cause problems with the operation of the 1 finger triple-tap gesture and the 1 finger double-tap and hold.
It is important to note that this behaviour is not consistentâit doesnât happen every time. Based on our testing, there is no discernible pattern to predict when it will occur or how frequently. But based on experience, it likely won't be highly frequent for impacted users.
While serious, this issue does not appear to be widespread Based on our tracking of user experiences during the beta cycle. It has been encountered by five members of our Editorial Team. Additionally, A few other users across the wider community have reported experiencing this behaviour, including Jonathon Mosen and a listener to his Living Blindfully podcast. Beyond these known cases, there has been no indication that a significant portion of users are affected. Overall, current evidence suggests this is an intermittent issue impacting a small subset of users rather than something everyone should expect to encounter.
Adjusting the Double-Tap Timeout in Settings > Accessibility > VoiceOver has been suggested as a partial workaround for the issue. However, based on limited testing, changing this setting does not appear to resolve the underlying problem. While you may want to experiment with adjusting the Timeout interval, keep in mind that this could disrupt your natural double-tap muscle memory which is accustomed to the default timing. Any benefits in reliability would need to outweigh the effort required to learn the new timing. At this point, the setting change seems unlikely to provide a sufficient or permanent fix.
We chose to rate this issue as serious because of the importance of the double-tap gesture and its frequency of use. Moreover, our assessment has taken into account the potential impact of this behaviour on individuals who are new to or less familiar with iOS. These users might reasonably assume that the behaviour is due to them not correctly performing the double tap gesture, possibly leading them to conclude that using an iPhone is more difficult than it actually is.
Moderate Bugs
- When using VoiceOver to navigate the main screen of the native Weather app, the movement of focus is inconsistent and unreliable. Specifically, focus can become stuck on an interface element, falsely suggesting there are no further elements to the right or left. Or focus may unexpectedly jump over elements as if they don't exist on the screen. As a workaround, you will need to explore the screen by touch in order to locate all weather data.
- Using the "drag" action in the VoiceOver rotor to rearrange app icons on the Home Screen often does not work as expected. Specifically, when attempting to drag an app icon to a new position and place it before or after another app, the dragged app frequently ends up in a folder with the target app rather than moving to the desired location. It's also been reported that on occasions some drag action options, such as âdrop beforeâ or âdrop afterâ, may not always be available.
- An intermittent bug can cause VoiceOver speech to stop after ending a phone call, while sound effects remain. There is no clear pattern as to when this issue occurs. Similar behaviour has also been reported when using WhatsApp.
- Incoming banner notifications interrupt VoiceOver speech when the âSpeak Notificationsâ accessibility setting is enabled. Specifically, any time a new notification banner appears, VoiceOver will immediately stop reading the current on-screen text or menu to announce the notification. This interrupts VoiceOver mid-sentence or mid-menu in a disruptive manner. In previous iOS versions, VoiceOver would finish reading the current paragraph, sentence, or menu before speaking a new notification. This prevented jarring mid-sentence interruptions.
- The new predictive text feature in iOS 17 provides recommended words inline as you type using the onscreen keyboard. There are verbosity settings that allow VoiceOver users to control what happens when predictive text appears and when predictive text feedback is entered. However, some users report that these verbosity settings are not being applied consistently across different apps. When the predictive text verbosity setting is set to speak recommendations, some VoiceOver users report that recommendations are silent in certain apps, even though they expect them to be spoken. Conversely, other users have found that with the predictive text setting configured to not speak recommendations, VoiceOver will still read out the recommendations in some apps like Mail.
- It is not possible to mark certain actions as favourites in the system share sheet due to the âInsertâ button and checkbox being recognised as part of a single element. Specifically, when editing the list of actions to be shown in the Share sheet and focusing on an action that can be enabled/disabled via a checkbox, VoiceOver announces the checkbox state and "Insert" together rather than separately. Double tapping toggles the checkbox but does not allow inserting the action as a favourite.
Minor Bugs
- VoiceOver no longer announces the time when the device wakes if there are pending notifications. Instead, it states the number of notifications present.
- When using VoiceOver Find with a braille display, searching does not function as expected. Specifically, pressing dot 8 does nothing after typing in a VoiceOver Find query with a connected braille display. The search is not carried out. As a workaround, prior to pressing dot 8 to execute the find function, press dots 2-7 followed by space with dot 8. Your search will now work as expected.
- When using the VoiceOver rotor to mark an email as read in the native Mail app, VoiceOver fails to provide clear confirmation feedback. Instead of announcing "read" to confirm the action, VoiceOver speaks an unclear and incomprehensible word or phrase.
- When you adjusts the volume slider in Control Center using the flick gesture, VoiceOver announces the previous volume level rather than the new level after the adjustment. Specifically, when a user focuses on the volume slider in Control Center with VoiceOver enabled, then performs a 1 finger flick up or down to change the volume, VoiceOver speaks the volume percentage. However, instead of announcing the new volume level, VoiceOver reads out the volume level prior to the flick gesture adjustment.
- When editing Safari bookmarks, the bookmark names and reorder icon label are incorrectly announced with "remove" prepended.
- Double tapping on a bookmark or folder title in Safari's edit bookmarks screen incorrectly activates a delete button rather than opening the edit view. As a workaround, the contextual menu for actions includes an Edit option.
- Some users may experience inconsistent and less descriptive labelling of Control Center toggles. For example, the toggle for locking device screen orientation may simply be announced as âLockedâ or âUnlockedâ rather than using the more descriptive label âLock Rotationâ that was present in previous iOS versions. This degraded labelling does not appear isolated to any specific VoiceOver voice. Users of the Alex voice have reported experiencing the unclear labels, while others using Alex still hear the expected descriptive labels. Additionally, isolated reports indicate similar degraded labelling for other Control Center toggles beyond just the orientation lock. This bug seems to manifest unpredictably, affecting only a small subset of iOS 17 users. The inconsistent experience suggests an underlying issue, rather than a deliberate change in labelling.
Other Reported Issues
The Messages app will now automatically transcribe audio messages into plain text, a valuable addition for deaf-blind users. However, some users report the transcript preview and âShow Moreâ button appear visually but cannot be accessed through Braille commands, VoiceOver gestures or menus. Our testing could not reproduce this inaccessibility - VoiceOver consistently announced no transcription available for our audio messages. As we were unable to independently validate the issue, we have not filed a formal bug report yet. We will continue investigating this issue to clarify its specific behaviour.
Additional user-reported issues that we have not independently validated are discussed in these forum threads. While our team has not personally reproduced or confirmed these bugs, the threads are worth reading to potentially identify other problems you may encounter:
- RC's are now available for iOS 17, macOS 14, watchOS 10, and more!
- Braille Screen input not reporting deleted word if cursor not at end of text
- While using Voiceover and a bluetooth keyboard, unable to review or edit text in notes
If you know of any other VoiceOver, Braille, or low vision issues in iOS 17 or iPadOS 17 that aren't already listed here, we encourage you to share details below to help fellow community members. When reporting a new bug or problem, please include as much helpful context as possible - describe exactly when and where the issue occurs, the steps to reproduce it, and any workarounds you've found to bypass or resolve it.
Accessibility Improvements in iOS 17 and iPadOS 17
We know that there will be considerable interest in discovering whether the longstanding VoiceOver focus jumping bug has been addressed in iOS 17. This particular bug has presented challenges in checking and documenting due to its varying impact on different users. While some have been unaffected by this issue on iOS 16, others encounter occasional instances or, in more severe cases, frequent occurrences rendering their device nearly impossible to use at times. A further complication is that no consistent pattern has emerged regarding the circumstances under which this behaviour manifests. For some people, the issue exclusively occurs within Safari, while for others, it can present itself across any application. Similarly, the focus might jump to the top of the current screen for some, whereas for others, it will jump anywhere within the same screen.
The purpose of outlining these complexities is to underscore the challenge in accurately determining the status of this bug in iOS 17. Reports from the iOS 17 beta cycle have been mixed. Some users say that they have seen a end to this behaviour, while others note a reduction in its occurrence or no improvement.
Our Editorial Team's experience is similarly mixed. Given the inconsistent experiences, it's impossible to forecast post-update results for each user. You may be among the lucky subset that sees this issue fully resolved or observes some level of improvement, but we recommend regarding either outcome as a bonus rather than something to be expected after installing iOS 17.
Our testing suggests that the following pre-existing accessibility bugs have been resolved or significantly addressed in iOS 17 and iPadOS 17:
- When composing a lengthy email with the native Mail app using a Braille display, random words are no longer inserted in the incorrect place.
- The VoiceOver rotor's action menu no longer contains two separate Share actions in the Notes app.
If you encounter any additional fixes or improvements during your own use of iOS 17 or iPadOS 17, please let us know by posting a reply below.
In Closing
Our team has compiled lists of new accessibility bugs for every major iOS and iPadOS release since iOS 7. Based on our testing, iOS 17 and iPadOS 17 have introduced fewer critical VoiceOver and Braille bugs compared to previous major updates. Overall, these seem to be the most stable and usable major releases for blind and low vision users in recent years. However, if you haven't already upgraded, we would strongly recommend that you take a few moments to read through any replies to this post before doing so in case other users' experiences differ from our own. Also consider that historically Apple has delivered fixes for many accessibility bugs within the first few x.x.1 updates following major releases. Upgrading to iOS 17 or iPadOS 17 appears low risk for most use cases, but waiting briefly may allow Apple to resolve initial problems reported after the public release.
"It's not uncommon that simply toggling VoiceOver off and on again or restarting your device can resolve some issues that may arise following an OS update. Therefore, we highly recommend including these steps as part of your standard troubleshooting process. If, despite these actions, you continue to encounter new problems that haven't been reported by others, it might be worth considering a reset of your device's OS settings to their original defaults.
While this approach requires manually restoring your customised settings, including those related to accessibility, it's worth noting that a reset has proven effective for numerous individuals in resolving various issues. This suggests that occasionally, problems can be attributed to local factors rather than being OS bugs. If you choose to perform a reset and find that it doesn't address the problems, you have the option to restore your device from an iCloud backup, eliminating the need for manual reconfiguration of your settings."
When commenting below, please keep the discussion focused on accessibility issues specifically introduced or fixed in iOS 17 and iPadOS 17. These posts tend to garner helpful responses, so it's important readers can easily find relevant details. Also, remember upgrade decisions are personal with each user's situation unique - there is no right or wrong choice. Comments criticising others' decisions are not constructive and do nothing to add to the discussion. Furthermore, not experiencing an issue yourself does not mean it doesn't exist for others, as bugs can be configuration-specific. Stating an issue doesn't exist simply because you haven't encountered it is unhelpful. Our aim is constructive exchange of experiences to inform decisions.
In closing, we thank Apple's Accessibility team for their prompt response in fixing many of the bugs reported during the iOS 17 and iPadOS 17 beta period. Their dedication to addressing the issues raised by our team shows that Apple continues to prioritise accessibility. However, some problems remain unresolved. We encourage Apple to promptly address the outstanding accessibility issues discussed in this post and the comments below so that iOS and iPadOS can be as accessible, usable, and enjoyable as possible for all users.
Comments
An even better double tap workaround
Taps seem to be a problem generally with IOS 17. Have you noticed?
I monkeyed with tapping different ways, and in the end I gave it up as a waste of time.
Then, duh, it occurred to me to redefine some touch gestures to substitute for double tap etc. Now, I swipe right with two fingers instead of double tapping to activate. Big happy smile.
There seems to be enough swipe gestures capable of being redefined to meet our tapping needs until Apple gets that paper bag off its head. At the moment, unfortunately, Apple is lost inside it and is unable to find its way out. Amazing how a megalithic corporation of such gigantic proportion can get lost inside a paper bag, isn't it?
Speach
This happened in the developer beaters as well ever since beta one . Apple can fix the folkis issue but canât fix the stuttering problem issue
Changing double-click time
First, in addition to 1-finger double-tap, I found that 2-finger double tap was also an issue, making it difficult to answer calls, hangup, and play or pause media.
I finally had the opportunity to play with setting. My double-tap speed was set to 0.4 seconds. I changed this to 0.55 and haven't seen the issue since for either1- or 2-finger double-tap.
I wish this worked for everyone.
Braille display bugs found in latest update
hello everyone, I have found the following noticeable bugs on my latest iPhone software release. When you open the Messages app, you cannot read messages at all. The display is blank. Also, in the Podcasts app, braille does not work properly either. Is anyone noticing this? by the way, I am using the display from NLS. It finally works in this update. For a few versions, it was not though. The last update was iOS 16. this is the Zoomax eReader. Note, typing on it now, and it seems to be working fine. before,, I was using dictation.
Also with phone app
Hi, this is also with the phone app too. So basically it's like half-way usable, but not by much. Also, noticing, seeing when showing numbers they show in lower numbercase, for example the number 3 shows up as "numbersign, followed by dot's Two-+Five instead of Dot's 1-4. Is it just me seeing this? P.S: Also had to pull out my Apple Magic keyboard to edit this post after posting⊠Thanks!
Can't find podcast app controls
I am unable to find the podcast app player controls by dragging my finger on the screen. To reproduce:
1. Start playing a podcast. Pause if necessary so you can hear VoiceOver.
2. Find the mini-player near the bottom and open it.
3. Drag your finger around the screen. I expect to find controls for skipping back or forward, play/pause, time remaining, and playback speed. Instead, all I find is, "dismiss now playing screen button," and "media artwork image."
To workaround, find the media artwork image and swipe right, then VoiceOver focus moves to the player controls. But after doing so, I am still unable to find the player controls by dragging my finger. As a result, I'm unable to use the split-tap gesture to activate them.
re: sockhopsinger
To send messages, you have to swipe up with 3 fingers. This can be changed in accessibility>voiceover>commands>braille screen input. The one for this is called quick action.
@PaulMartz
Question:
Would opening Control Center and using the media controls be a good work-around?
podcast player controls
Control center lacks a playback speed and time remaining control, but yes, I can drag in the control center to find skip back/forward and play/pause.
You know how when you first open a recently updated app, and it displays a box describing all the changes? Well, after upgrading to iOS 17, when I first opened the Podcast app, it displayed one of those boxes. And it mentioned how it had now made it easier to play podcasts or something to that effect. So I was surprised that the new version actually made it harder, not easier, to find the playback controls.
This change doesn't feel like an enhancement or improvement, so I thought it was worth mentioning.
Moving icons on a home screen
iOS 16 brought a new problem that when you move the icons on the homepage and you wanted to place an icon after one that was already there then it would create a folder with that icon the way rounded it was to tell the icon you are moving to place it out before the icon that you Had on your home screen in iOS 17 unfortunately it doesnât matter whether you move an icon and place it before or after an icon thatâs on the screen it creates a folder with it so the problem is actually worse in iOS 17 what it was in iOS 16
I originally reported this problem to Apple almost a year ago and of course nothing has happened to solve this problem although it is not anything really to do with voiceover because other people who donât even use voiceover are encounter in this issue
Websites becoming unusable in Safari with Voiceover
I donât know how or why this happened but as of yesterday Google in Safari doesnât work with Voiceover. It doesnât acknowledge thereâs a website there at all. Screen reader helps but we all know how buggy and unreliable that is. It really feels like iOS 17 is unfinished and untested in terms of accessibility in spite of how much work beta testers put into it.
Also beware the customized accessibility experience. I opened it just to see what it was like and it messed up some of my iMessage settings with no way to reset or change them no matter what options I select.
TO: Quentin Williams
Thanks, Quentin for that tip. I can't believe I never even knew that was a thing.
Banner notifications interupting speech.
Has anyone found a workaround or fix for this? I feel like I read something on here a day or 2 ago about a possible solution but can't seem to find it.
Find bug workaround
When doing the find feature with braille just do space with dots 2-7 to do option then quickly press enter. It'll work (At least it does for me). Man, I miss the days where I didn't even have to recognize the existence of the option key and have a smooth braille display experience.
Status bar?
When on the status bar and going to battery, when doing the gesture (On ios or with braille ) to exit the status bar, it just goes back to the first element, then I press it again and it goes back to battery. It's as if battery isn't part of the status bar although I know it is. This also happens if VO jumps to the status bar automatically.
The Two Annoying Issues I have found
To me, there are two extremely annoying issues I have found since upgrading to iOS 17. Actually, I didn't have one of the issues on my old 13, but it sure reared its ugly head when I upgraded to the 15 pro. I am still amazed at the ridiculous Weather app bug that randomly switches to another city when you are browsing through the hourly forecast. I find it hard to believe that Apple Accessibility did not know about that issue long before the release and have a fix for it. However, that can be gotten around by using another weather app, so PFFFFFFFT to the native app.
The one that is really baffling, and I am not sure if it is an accessibility issue or not, is that when my alarm goes off and I hit snooze, if I then go into the notification center, I am given the option to turn the alarm off there. If I do so, the notification of the active alarm goes away, but still after 9 minutes, the alarm goes off again. I hope that makes sense.
Set Notifications When Locked and Banner Notifications to...
Do Nothing.
You can do this by going to Settings > Accessibility > VoiceOver > Verbosity > System Notifications. Set both of those options to Do Nothing and you're golden.
Voiceover stopping at random
Since updating I have had an issue with Voiceover just going silent at random times. It happens while I'm reading long texts but sometimes when doing other things. No warning or commonality in the things that make it stop. It just goes quiet about once or twice a day, requiring a restart of Voiceover to get it talking again. Very tedious.
SIRI Cutting Off, Have Reported Possible Cause, Update
Ever since I upgraded to iOS 17 last Monday and have installed the latest upgrades to 17.0.1 and 17.0.2, there is a most frustrating and annoying SIRI issue. I have reported this to Apple and included a screen recording of it happening. When SIRI is reading information, it will suddenly stop speaking. About the fifth time it happened, I noticed it was tied to a background noise in the room. So I tested this by having it read football scores, then I intentionally said in a clear voice, current weather. Siri stops reading the scores, then tells me the weather conditions. Now, for the record, this is why I hate features like Hey Siri and why I have always had it turned off. I checked my settings, Hey Siri is off, have spoken responses is set to always, though I tested and had this same issue when set to when possible. I tried switching to type to SIRI and then back, this did not resolve the issue. So based on this, SIRI is not releasing the microphone when it is speaking information and thus any perceived command or sound interrupts the speech, making the use of it in any setting with any degree of noise all but impossible. Siri is also not a baseball fan, often when I ask for scores I'm being told I can't do that, but some times Siri begins reading them until something interrupts.
have others encountered this? Apple at first said they could not reproduce this, after I sent in my theory with video to back it up, Apple replied Wednesday saying they were able to reproduce this same issue and that they have forwarded this information to the tech development team for review. I will post a new update on this when I know more. Curious about others observations.
I can also confirm that the issues with the screen not responding properly when trying to tap on it have been a major bug, fortunately my Apple style Bluetooth Keys to Go keyboard is handling things quite well as a reliable alternative in that situation.
Problems using Siri to create appointments
This problem is probably only with a phone that has a home button
When ptapping the home button to activate Siri and asking it to create an appointment. After Siri has done this then intermittently pushing the home button to go back to the home screen does not work And the only way to get out of this lock up is to either ask Siri verbally to go to home screen or to do a hard reset by pushing up volume momentarily down volume momentarily and then the power button for 10 seconds
I have reported this to Apple accessibility
Are use the iPhone SE 2022.
Camera shutter noise missing
When taking a photo with the camera using iOS 17 I do not get the shutter noise
This problem I have found on an iPhone SE 2022 and apparently other people are experiencing the same problem
The photograph gets taken is just you donât have an indication that it has done that
@Reggie
Possible work-around for you. Try the following:
1. Go to Settings > Accessibility > Siri.
2. Flick right until you find "Siri Pause Time".
3. There are 3 settings for me; Default, Longer, and Longest. Your mileage may vary.
4. Try adjusting these and see how things go with Siri?
HTH. đ
Safe update for me
Look, it was the first time since I started using an iPhone that I had the courage and I don't regret having updated to the first public version of a major update, in this case iOS 17. There are some bugs, but nothing that gets in the way of my use... Very happy!
The only annoying, so I have iPadOS 17 is battery life seems to
Battery life seems to be a bit worse for wear on my iPad. To mention, one other thing thatâs annoying, is how quiet the Safari tick tick tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick, tick tick:; loading sounds on Safari. I hater of quiet. Itâs way more louder when I have headphones connected. I donât know why.
Podcast app â VO not speaking name of podcast
In the native podcast app, from library go to either latest episodes or saved. while navigating through the list of your episodes to try to find one to listen to, voiceover is not saying the name of the podcast. So you hear the name of the episode but have no idea what podcast it is associated with. A sighted user gets this information prominently via the Podcast's artwork. (bug introduced in iOS 17)
My Experience with 17
I updated to iOS17 on Tuesday and my thoughts are as follows:
1. I actually find the focus on the weather app greatly improved. For several versions now, it would put me in the last city in my list if the top of the screen is touched, but I tried this the other night and I couldn't get it to change.
2. I actually appreciate that VoiceOver is once again reading episode descriptions in the podcasts app. You could find them previously, but you had to pull up the episode itself, now descriptions are back on the listen now screen.
3. This is probably not useful if you can't find your phone and want to know if it's listening, but when I hold down my home button to activate Siri, I get a haptic instead of the chime.
4. I am experiencing the notification instead of time issue. Additionally, I started a forum thread last week about how notifications were always being read when the phone was locked. I turned off the speak count then turned it back on and it seems to be working normally. I am experiencing the speech interrupting issue. I kind of wish there was a way to change the way things were read though even with this fixed. For instance, VO will say "actions available" and won't read the notification until it has read that. I wish in those instances it would skip speaking the system hints.
5. Although I'm not having the double tap issue described here, I am having an annoying issue particularly with messages. If I use the dictate button located a right flick from the text box, I have a hard time ending my message. I double tap the screen when I'm done, but the microphone isn't released, and speech is silent so I have an incredibly hard time finding the button to stop dictation. Is anyone else having this issue?
6. I haven't used Alex, but I do use Tom enhanced. I've had that occasionally switch to Samantha on me at completely random times. Samantha will usually speak one or two words, then Tom is back. This happens to me maybe once every other month dating back to iOS16 at least, maybe earlier.
7. My focus issues overall seem to be a bit worse, but it's still not bad. It usually jumps around on me in the following circumstances:
A. I have been focused on a particular app on the home screen, then plug my headphones in.
B. When on Facebook, if I've just left a comment then quickly touch the top left of the screen to go to the back button, I'm instead thrown back to the comment I just left.
C. If I unlock the phone then quickly touch the screen close to an app I want, it will go back to the top of the screen.
D. Perhaps related, I've noticed once in a while that if my phone goes to sleep not at the top of the screen, it will unlock with focus on the app focused on when the phone went to sleep rather than at the top of the screen where I expect it.
8. The speech dropping issue seems to be not just when ending phone calls, but any time an audio source changes. For instance, I've plugged in headphones and had speech go out on me, only to have it come back seemingly in mid-sentence when taking headphones out again.
8. Last but not least, I did notice that alert and ring tones now cannot be interchanged, but I just set my usual text tone for a friend whom I just added to my contacts less than a month ago and it took just fine. I'm going to now have to get used to hearing that tone for her.
VO crashing and cursor jumping
I don't have the cursor jumping quite so much as it seems to get stuck and refuses to move. As for the vo crashing thing, I have tried to switch to a different voice until they can fix Alex. Unfortunately, there really aren't any other voices that I like as well as Alex, so this has been a challenge for sure. Currently using UK Serena, and so far, no issues.
Anyone else have these problems?
Iâve been having trouble reading Apple Books with VO since updating to 17.2. It reads only a page or two and then stops. It also changes the speaking voice in the middle of a page.
Changing double tap timeout really helped. Let me explain why
Hi there,
I was one of the unlucky ones to experience the double tap issue mentioned in this blog since iOS 17.
After starting a thread on the Applevis forum, I discovered that not everyone was experiencing it, but that it was mostly due to their double-tap habits, and that those with a slower double-tap gesture suffered more than others.
Then I came across an iPhone that hadn't been updated, and remembered that little passage in the blog that said changing the double-tap timeout didn't really help. So I borrowed my friend's iPhone and looked at how its timeout was set. I discovered 2 things.
Firstly, it was set to 0.25 seconds, which was a very comfortable setting, and secondly, and more interestingly, the maximum value for this setting was 0.5 seconds. It just couldn't go higher than this.
Then I looked at mine, a 12 Pro, and saw that the timeout was also set to 0.25 seconds, but I could take it up to 2 seconds. I wondered why there was such a huge difference with previous operating systems, but I experimented with 2 seconds and found that a single tap was delayed, of course, but by much less than 2 seconds, I would say about 300 ms, which was already a lot. I then reduced it to what I felt was a comfortable value, which turned out to be 0.5 seconds, exactly the maximum on my friend's iPhone, only this time there was no noticeable delay, and the double-tap problem was solved, at least for me.
So I would encourage those suffering from this double tap problem to set their double tap timeout to 0.5 seconds and see how they feel.
Hope this helps a bit.
Cheers,
JPR