A novel bug or is it?

By Lee, 20 October, 2026

Forum
iOS and iPadOS

Ok Guys came across something very interesting which is probably a bug but hey ho. in the UK we have an insurance company called lv and whilst checking my banking app I came across an entry for 55. Totally baffled me at the time. Then it suddenly flashed into my head lv in roman numerals is 55. So as a test I tried other combos of letters and yep all are roman numerals. They have to be in uppercase or VO reads them correct. Lv would say lv lv would say lv but LV says 55 etc. XIV reads as 14. So you get the idea. Tried this with 4 voices and my personal voice and exactly the same. The only voice that seems to read the letters correct is Eloquence for whatever reason. Not sure if this is iOS27 or if it does the same in earlier versions. Quite funny though it was confusing.

Options

Comments

By FmNgqRZd on Tuesday, October 20, 2026 - 15:34

Definitely not new, but definitely jarring and annoying every time I've encountered it. Personally, I'd prefer any screen reader to read the literal text rather than making decisions without any context about what it thinks I want to hear, but VoiceOver seems to disagree in more cases than only this one.

By SheilaG on Tuesday, October 20, 2026 - 15:50

Like with Jaws, I think you can change this in the dictionary.

By Singer Girl on Wednesday, October 21, 2026 - 02:59

Voiceover has been doing this for years. It seems to be that the voices are trying to be too smart and they’re always expanding abbreviations when they don’t need to be. For example, if you write out the letters V and I next to each other to talk about the visually impaired community it always reads as six Community. So yeah, this has been happening for a very long time. Unfortunately, it’s nothing new. I really don’t know what can be done about it. These things don’t really even seem to work by fixing them with the pronunciation dictionary. I have honestly never gotten the pronunciation dictionary correctly even when it first became available through iOS 10. Every time I’ve tried to change any kind of pronunciation they were never honored. When you have to do the custom and then phrase and then play it and all the steps that you have to do for it I’ve never gotten that to work successfully. I don’t think it’s a bug. I think it’s just a synthesize. You’re trying to be too smart. Definitely seems to be more of a case when using enhanced or premium voices. That’s what I tend to use anyway as I don’t really like the standard version of Voice as quick as much. All occasionally use them, but I tend to gravitate more towards the premium and enhanced versions of voices. Hope that helps at least knowing that you’re not the only one who’s seen this.