[Updated: Fix On the Way] A Warning to Blind, DeafBlind, and Low Vision Users About Potential Loss of VoiceOver Speech in iOS 26 and iPadOS 26

By AppleVis, 18 September, 2025

Member of the AppleVis Editorial Team

Update, 09/18/2025: Apple has confirmed that they are aware of the issue and that it will be fixed in an upcoming software update. We will update this post as more information becomes available.


On occasions, blind, DeafBlind, and low vision users may lose VoiceOver speech after updating to iOS 26; either immediately after the update installs or upon a subsequent reboot of the device. If you use VoiceOver and have not already done so, we recommend that you do not install iOS 26 or iPadOS 26 until Apple resolves this issue.

At the outset, we must stress that the issue discussed in this post is not something that members of the AppleVis Editorial Team have personally experienced, and our understanding of the full nature and scope is limited. This issue also does not occur for everyone.

It is AppleVis' general practice to not post about issues that our team cannot personally validate; however, due to the seriousness and documented impacts for blind, DeafBlind, and low vision users, we feel that to not raise awareness of this issue would be doing a tremendous disservice to our community.

Shortly after the releases of iOS 26 and iPadOS 26, we began receiving reports from the community from users who experienced a loss of VoiceOver speech--either immediately upon installing the update, or after rebooting the device at a point in the future. From what we have gathered, this issue appears to present itself only while on the Lock Screen after a device restart, and it has so far only been reported on devices that are passcode-protected.

When the issue occurs, impacted users report that there is no VoiceOver speech and that Siri is also unusable. We hypothesize that inability to use Siri is tied to the device being locked and requiring a passcode upon first restart, as this was the case on a properly-functioning device we tested.

There are multiple reported manifestations of this issue. While some reports have been from users who experienced a loss of speech immediately upon installing the iOS 26 update, multiple users have also reported that the issue presents itself only after the device is rebooted after a period of time; suggesting that perhaps the underlying issue may be with something unrelated to the update process. One user reported that VoiceOver was turned off upon installing the iPadOS 26 update on their M1 iPad Pro.

Once the device is unlocked, impacted users report that VoiceOver speech works normally. We are not aware of any reports of this issue occurring more than once for a particular user.

While we believe the reach of this issue is somewhat limited, it is nonetheless incredibly serious. As just one example of the impact of this issue, a member of our community shared how their iPhone 15 became unusable upon rebooting some time after installing iOS 26, with all attempts at troubleshooting being unsuccessful.

As the issue appears to resolve upon unlocking one's device, it is possible that disabling one's passcode and biometrics in advance may allow a user to bypass the lock screen and get to a point where VoiceOver works normally. The only other confirmed solutions have been (1) obtaining sighted assistance to unlock the device, or (2) absent sighted assistance, erasing the device with Find My and/or via a computer.

Apple is aware of these reports and is investigating. We recommend that users do not update to iOS 26 or iPadOS 26 until this issue is resolved. We call on Apple to uphold their long-standing commitment to accessibility for their blind, DeafBlind, and low vision customers by prioritizing and releasing a fix for this issue as a matter of great urgency.

Options

Comments

By Holger Fiallo on Saturday, September 20, 2025 - 19:42

I do not worship on the apple alter. Do like my iPhone 16 pro max, airpod pro 2, watch 9 and iPad 9. Is not a crime to tell the true. Lucky for me I do not have all those issues, just the VO stopping on the middle of reading notifications. Long live cats.

By Dennis Long on Saturday, September 20, 2025 - 20:21

I'm really tired of the constant negative comments. It doesn't help the situation.

By Holger Fiallo on Saturday, September 20, 2025 - 20:28

With respect, do not read it. Enjoy your day. Long live cats.

By AppleVis on Saturday, September 20, 2025 - 20:32

Member of the AppleVis Editorial Team

A quick point of clarification :

  • Apple has confirmed that they are aware of the issue and that a fix is coming in a software update.
  • Apple has not shared when that update will be released.
  • All we know is that a fix is incoming.

By Theepan on Saturday, September 20, 2025 - 21:56

I had first reported this bug to Apple on July 25, 2025. (FB18391105)
This is, in my experience, related to the voiceover voice issues that me and others were having all along.
Similar, if not the same issue has persisted in previous years as well.
I find that this has something to do with voiceover voices not being available when the system update for restarts.

By Exodia on Sunday, September 21, 2025 - 00:25

guys, there’s no need for this kind of behavior. Negativity isn’t gonna get us anywhere. They are working on it, they will fix it. I get that its frustrating, but we shouldn't be so negative toward the company that has given the blind community so many good things. No I’m not a fan girl, but I’ve used a lot of Apple devices in my time starting with the old Apple 2E when I was a kid. Anyway, I am running an IPhone twelve and I never had that issue. Last night, I forgot to charge it and the battery ran down. When it started back up, VO started with no problem.

By Blindxp on Sunday, September 21, 2025 - 02:31

Okay so whilst I usually wouldn’t really agree with negativity, I do understand why some people are negative about this issue.

This issue first occurred for me on the first release of iOS 13, both on an iPhone SE first generation and an iPhone 7. To see this being essentially repeated it’s not a great look, at all.

As I said above, Apple is a multi trillion dollar company. Surely it has people on deck to actually test these releases before they get released to the public and tell Apple, stop, we need to fix this, all that, or whatever, because this will impact a certain community, and we don’t want any discontent. So, I understand where the negativity is coming from. But I do understand also that the negativity is somewhat overboard, and constant criticism isn’t going to get anybody anywhere.

By kool_turk on Sunday, September 21, 2025 - 04:34

I appreciate the desire to help, but I'm looking for advice from people who have directly experienced this. General advice or guesswork isn't effective when facing a showstopper bug like this. It's also not helpful to hear from those who haven't had the issue. When my phone screen went black after the update, the only thing that fixed it was a backup restore. I've learned my lesson and would strongly advise others to hold off on updating. It's frustrating, but I take full responsibility for updating anyway, knowing the risks.

By Blindxp on Sunday, September 21, 2025 - 04:50

The weird thing is, not everyone who’s updated iOS 26 has experienced this issue. But yet other people have. I don’t really know what’s going on.