Thank you for your reply,
I assumed that this will be the case were one side will roll the issue to the other side as you can see from GOOGLE reply (attached at the end)
I’m a father to two blind, and in the last 30 years I’m very aware to accessibility issues, I agree that the logic solution is to make the SCREEN READERS able to deal with lack of awareness of million of developers to accessibility issues
To my estimation 90% of the app loaded to GOOGLE STORE are not accessible because of the use of canvas and component on it.
MIT is not just another developer, this is why my expectation from MIT is to raise the flag of accessibility and to set the standards and awareness to this issue.
I’m not a SW person (I’m electrical engineer) but I enjoy very much working on your platform and develop accessible app.
Searching the net I found the following site dealing with the same issue, maybe this can be implemented on your platform
Thanks
GOOGLE reply:
Hi Shmuel,
Thank you for contacting the Google Disability Support team! I'm Simone and I'll be happy to assist you today!
I understand that Talkback doesn't recognize elements in a third party app.
Since Talkback detects the code of the apps, you should contact the developers of that specific app in order to make it accessible. They should implement accessibility codes in their app in order to let Talkback announce their elements.
I hope it's clear.
Have a great day!
Simone
Google Disability Support Team