The only way to solve that problem is to render objects as actual native objects. That will probably not be happening, but I wanted to check and be sure I was correct in my asumptions.
Here’s some backup information as to how Corona uses OpenGL:
https://forums.coronalabs.com/topic/59278-i-want-video-fill-to-background-rectangle/
Again, I don’t know if I can call this a problem, in that there are many other options for software development. Now, if one were to say, “but Corona is so easy to use! If they could stop using OpenGL then everyone would benefit.” the answer would most likely be, “if Corona stopped using OpenGL, then it would be exponentially more difficult to use, thereby eliminating the benefit.”
disclosure: I’m not employed by Corona, nor do I derive financial or practical benefit from the company aside from using the SDK they produce for app development. My opinions and comments above are my own and do not reflect the feelings, views or opinions of anyone from Corona. My comments are not intended to offend, hurt, demean or insult any person, group or affiliation. If my comments have done so, I apologize.
I guess the difference is that where native iOS controls expose some accessibility properties to VoiceOver, the screenreader built into iOS which is not speech-to-text but rather OS-wide text-to-speech, it appears these Corono-specific controls do not. I have no idea if Apple allows for a whole lot of options in this matter, you would either have to compile down to native or at least nativer code to get those access properties back or Corona would have to implement their own accessibility API, which I’m not sure is possible either. We’d need an engineer knowledgeable about iOS internals and the Corona toolchain to comment on this…