When I updated to iOS 26.1 pronounciations no longer work for me. It just pronounces words how it originally does without using all the custom pronounciations I've made. Is anyone else experiencing this?
In this case, it appears with voices other than the main voice.
Regarding the handling of custom pronunciations by VoiceOver, with French voices it has been working very poorly for years. Many custom pronunciations are ignored by VoiceOver in numerous applications.
Let’s hope that Tim Cook’s successor finally puts the teams to work to fix the countless VoiceOver bugs that have been piling up for years, both on iOS and macOS, and which are almost never corrected. In short, the conclusion is clear: accessibility is falling apart at Apple.
There’s no need to be negative and saying things like Accessibility is falling apart at Apple. The reason you could even say that you think Accessibility is falling apart is because you have Accessibility in the first place. Do you want to be the one sitting here programming all the information to make these bones work? It’s amazing. They run as well as I do. Apple does listen to you. Their voices that weren’t working at all with iOS 26.0 and those got fixed with 26.1. Sure there’s some weird things happening so of course there is there’s always gonna be bugs. You just need to keep reporting them to Apple. They do listen to us.
When a device we all rely on that was previously functional has bugs which have not been addressed for upwards of six years despite all of us reporting them dilligently, we are allowed to speak out about it. If sighted people had to deal with any of this for even a day we know it would be fixed immediately. If Apple won't hear us, maybe someone seeing what we have to deal with on a public forum might notice and help get the ball rolling. So yes, people are allowed to give honest critique about their Apple devices and be frustrated when something that worked yesterday and which has no reason to break is suddenly destroyed today with no known time frame of when it might be fixed, if it ever will be.
At AppleVis, it is our goal to create a place where blind, DeafBlind, and low vision users can speak freely and openly about their experiences using Apple products and services. Part of being able to speak freely and openly is being able to be critical of Apple and other developers/companies serving our community. While we do ask that people please not troll topics with negativity (for example, if the post isn't about bugs or issues, we ask that people please not hijack the topic by saying how much they hate Apple or whatever issue is on their mind), talking about bugs in threads like this is legitimate, welcome, and necessary. If you don't want to read it, please move along.
Like, imagine if for example a sighted person had the name of their friend constantly misspelled in every context without any way to fix it. It doesn't keep them from using their phone in any way, but it would be infuriating to look at and something that they would want fixed right away. And if Apple adds a feature, no matter how small, it should work. I think that's not too big of an ask. I understand that code can sometimes change things in ways not everyone expects, but I do expect for bugs to be resolved at some point.
Subject says it all. I had the same problem in 26.1 but when I updated to 26.2 beta the pronunciations came back. Hopefully it stays fixed for the final release.
Different voices behave differently with pronunciation, I've found. You could try a different voice, but you shouldn't have to. Hopefully they'll have this fixed soon.
I’m going to say the same thing about different voices handling pronunciations differently. I’ve noticed that. Voices I mostly use as Samantha enhanced and Karen premium. But I have tried a couple other voices too, and they definitely handle pronunciations differently than some other voices. But just how things are I guess I think it might be like switching between different synthesizer. There used to be this weird bug like if you switched between a vocalizer voice and an eloquent voice on the back of vocalizer that it would crash you out ASAP, but that doesn’t happen anymore so they did fix it. It’s good that this bug is fixed for people in iOS 16.2 though. I meant 26.2 but yeah. That’s good. I still say we should be glad these things are even working as well as they are. I’m just talking about programming the devices nothing to do with voiceover. I think part of it is because we’ve got so many Accessibility features that travel hard to know which part of them a certain bug. There’s a lot more other Accessibility features than VoiceOver. I think that’s kind of where sometimes there are more bugs because maybe there’s more features now. I’m not sure exactly but I’m just guessing. I’ve never gotten pronunciation and it’s a successfully work honestly, so I just gave up on trying them.
Comments
I confirm this bug.
Hello,
I confirm this bug.
In this case, it appears with voices other than the main voice.
Regarding the handling of custom pronunciations by VoiceOver, with French voices it has been working very poorly for years. Many custom pronunciations are ignored by VoiceOver in numerous applications.
Let’s hope that Tim Cook’s successor finally puts the teams to work to fix the countless VoiceOver bugs that have been piling up for years, both on iOS and macOS, and which are almost never corrected. In short, the conclusion is clear: accessibility is falling apart at Apple.
Best regards,
Philippe
No need to be negative here
There’s no need to be negative and saying things like Accessibility is falling apart at Apple. The reason you could even say that you think Accessibility is falling apart is because you have Accessibility in the first place. Do you want to be the one sitting here programming all the information to make these bones work? It’s amazing. They run as well as I do. Apple does listen to you. Their voices that weren’t working at all with iOS 26.0 and those got fixed with 26.1. Sure there’s some weird things happening so of course there is there’s always gonna be bugs. You just need to keep reporting them to Apple. They do listen to us.
confirmed here as well
As the subject states, I will also confirm that this bug is present in iOS 26.1. Very odd. Hopefully it'll be fixed in a later OS build.
Singer Girl
It is a fact that VO is so. Please respect others personal experiences. Long live cats.
Being negative
When a device we all rely on that was previously functional has bugs which have not been addressed for upwards of six years despite all of us reporting them dilligently, we are allowed to speak out about it. If sighted people had to deal with any of this for even a day we know it would be fixed immediately. If Apple won't hear us, maybe someone seeing what we have to deal with on a public forum might notice and help get the ball rolling. So yes, people are allowed to give honest critique about their Apple devices and be frustrated when something that worked yesterday and which has no reason to break is suddenly destroyed today with no known time frame of when it might be fixed, if it ever will be.
Critique of Apple is Core to Platforms Like AppleVis
At AppleVis, it is our goal to create a place where blind, DeafBlind, and low vision users can speak freely and openly about their experiences using Apple products and services. Part of being able to speak freely and openly is being able to be critical of Apple and other developers/companies serving our community. While we do ask that people please not troll topics with negativity (for example, if the post isn't about bugs or issues, we ask that people please not hijack the topic by saying how much they hate Apple or whatever issue is on their mind), talking about bugs in threads like this is legitimate, welcome, and necessary. If you don't want to read it, please move along.
Confirmed
I can confirm this also. I don't have many pronunciations set up but the ones I do have I would like to hear and keep.
Yes!
Like, imagine if for example a sighted person had the name of their friend constantly misspelled in every context without any way to fix it. It doesn't keep them from using their phone in any way, but it would be infuriating to look at and something that they would want fixed right away. And if Apple adds a feature, no matter how small, it should work. I think that's not too big of an ask. I understand that code can sometimes change things in ways not everyone expects, but I do expect for bugs to be resolved at some point.
Seems to be fixed in 26.2 beta
Subject says it all. I had the same problem in 26.1 but when I updated to 26.2 beta the pronunciations came back. Hopefully it stays fixed for the final release.
Mine's working properly.
Different voices behave differently with pronunciation, I've found. You could try a different voice, but you shouldn't have to. Hopefully they'll have this fixed soon.
I was going to say the same thing about different voices
I’m going to say the same thing about different voices handling pronunciations differently. I’ve noticed that. Voices I mostly use as Samantha enhanced and Karen premium. But I have tried a couple other voices too, and they definitely handle pronunciations differently than some other voices. But just how things are I guess I think it might be like switching between different synthesizer. There used to be this weird bug like if you switched between a vocalizer voice and an eloquent voice on the back of vocalizer that it would crash you out ASAP, but that doesn’t happen anymore so they did fix it. It’s good that this bug is fixed for people in iOS 16.2 though. I meant 26.2 but yeah. That’s good. I still say we should be glad these things are even working as well as they are. I’m just talking about programming the devices nothing to do with voiceover. I think part of it is because we’ve got so many Accessibility features that travel hard to know which part of them a certain bug. There’s a lot more other Accessibility features than VoiceOver. I think that’s kind of where sometimes there are more bugs because maybe there’s more features now. I’m not sure exactly but I’m just guessing. I’ve never gotten pronunciation and it’s a successfully work honestly, so I just gave up on trying them.