Auto language detection on South Indian languages like Kannada Telugu Tamil Malayalam

Yes, as an iPhone user I am very very disappointment for auto language. Switching is not working in India.. why Apple accessibility team doesn’t understand the situation and why they don’t understand Indian, Apple users problems, specially with accessibility. Again and again, we are waiting for fix the problem. Please try to understand the situation and solve the auto language problem.

I need to switch manually. Or y have a specific bug cause I haven't reset for a long time?

Hi, I’m Poojitha from India. I’m also facing the same problem with auto language detection. VoiceOver is not reading Telugu, Tamil, Kannada, or Malayalam correctly, and switching the rotor every time is very hard. I really hope Apple fixes this soon because it affects our daily use. Thank you.

This has been the serious concern for many of the iOS South Indian visually impaired iOS users

We have made numerous attempts, but we are not heard

Every time, We encounter a South Indian language text message, we have to switch our router to that particular South Indian voice to be able to read the message while the other Indian languages like Hindi gets auto switched when any text in Hindi is detected. This benefits Hindi readers to access the content with ease.

We South Indians are being deprived of this ease of access to the content when we encounter any of our local languages

Many of our South Indian visually impaired individuals do not prefer iOS only because of this reason

Apple is renowned for it’s Accessibility. Any visually impaired individual would resort to iOS to make their lives, comfortable and engaging

But it is extremely disheartening that we are not heard about auto language, switching availability to the VoiceOver

I failed to understandWhen it’s competitor, Google is considering Accessibility features and keeping it in a top priority list,
When Google talkback is providing such option, we being iOS lovers are gifted with this disheartening experience

Your best bet would be to email Apple at [email protected]

even I have written so many mails, tweeted apple on x, wrote a post on linkedin but, no any response.
we do understand that, its not the job of applevis to get this up to the apple nor this is affilated with the apple, but we need this issue somehow get noticed and sent to apple via bug tracker.

First, I am pretty sure that something like autotts on ios is impossible to code as the system is too closed, and most importantly, voiceover has 0 access unlike the little apple script hooks we can try to get on macos. And there is also the fact that most modern apps are with react native or another crap :) positively speaking, like fluttr, where a simple wrong tag lang="xxx" can absolutely screw screen readers.
And there is the fact that there is a fundamental misunderstanding or great confusion in term of language detection with pure latin character languages (e.g. english characters mostly) and others like greek, cyrillic, urdu / hindi / gujarati/punjabi/... which are completely different scriptures than latin or equivalent, and where some tts technologies like nuance, acapela, siri voices they are by nuance anyway as far as I know, Alex voice from apple, even eloquence for that matter, that simply don't support reading / processing those character. Nuance have a couple of different voices per language per dialect / accent, whereas espeak has one main same tembre / tone for as many languages as there are free people to play with phonemes and complicated math stuff beyond my poor understanding of big math :)
I am not saying this to justify apple, not at all. But for casual readers of this thread, I think some technical knowledge is a must.
I know nothing about tts, just enough in general to speculate and I am generally right on those things in this case as I too speak punjabi, english, french, and understand hindi, and find that support for our languages in digital accessibility landscape is still very lacking.

I am indian myself. But my point is that in the age of generative ai and llm, it's easier than ever to translate both the intent while clarifying the content and add a bit of paraphrasing / rephrasing, which wasn't the case with google translate or equivalent technologies in the past. It's almost impossible to actually understand even the base problem reading this thread for the first time, no wonder why apple haven't done anything yet, there is almost 0 chance they can ever understand the problem. Look at the participation rate in this very thread. Please :)