Dear specialists,
My name is Janusz Chmiel. I have installed Corona build system to my Windows 10 operating system recently. Because I Am visually impaired user with no sight at all I would like to know, if it would be possible to build apps for Android platform, which will be accessible with Talkback or other screen reader. Unfortunately, examples, including audio player are not accessible. Do you think, that there is some possibility to create accessible GUI? It is sad, if it will not be possible, because stability of compiled apps is perfect. Even GUI of Corona simulator is completely accessible. Build time is very fast. May be, that it would be possible to construct new API, which would enable visually impaired developer to create apps also for this target group. The main issue is, that apps, which are based on Android native activity are not accessible with screen readers. It is sad, because such apps are very fast, stable. But unfortunately, not accessible for Talkback or other screen readers.
Any help will be welcomed.
Hi Janusz. Welcome to the Corona Labs forums.
I think you’re going to find getting Corona-made apps to work with screen readers near impossible. With the exception of the “native.*” API calls, everything else that gets drawn to the screen is a graphics texture. Unlike HTML, which has hidden meta-data for images like “alt tags”, Corona doesn’t have any such metadata and there is no facility to add such data.
With a web page, text content (HTML, CSS, JavaScript) is downloaded to the browser where the browser renders any graphics, but because the HTML text exists, screen readers are able to function. For applications like Corona, yes, our menus and dialog boxes will work but that’s because it’s actual text being rendered by the operating system. But when it comes to the built app itself, think of the screen as one big image with no text to describe it.
Rob
Dear Rob, thank you very much for yours qualified answer. But even if yours product can not create accessible GUI for users who are using screen readers, receive my deepest possible appreciation to yours excellent work. Apps which are created by yours environment can look very attractive, its load time is very fast and reliability of compiled code is outstanding. The main problem is, that The core developers of Talkback do not wan to support C apps, which are using Native Android activity. So even if yours product would not write graphics, it would not be able to run. This is The reason, why apps must contain special Java bridge, which creates bridge between Java code and native C code. So .java code and .xml files contain buttons and app GUI, and C compiled code from .so libraries is executing The appropriate action based on user input from GUI. If user click on some button, menu item, ETC. The main disadvantage of this enforced approach is, that reaction speed of Talkback is slower than if app would be written entirely in Java. VLC media player, or apps, which have been written in C++ by using Android QT creator IDE also contain similar accessibility bridge. But it may even cause random crashes of apps. So sure, yours approach, which you have incorporated to The compile and build algorithm is much more better. And yours approach is really ideal for creating professional looking games and other apps. In fact, only users of assistive technology, which are using Explore by touch Android service are excluded from using yours professional and stable solution. It is reality of visually impaired and every one must accept The fact, that not all apps will be usable. I can use Android Studio, Eclipse with Java, QT Creator for Android, or Lazarus with Lamw special installable package for Lazarus. Which produces Java bridges to create accessible GUi. I wish you many programmers achievements and much busyness achievements. And really. Thank you again for yours fast and qualified answer. I wish all sighted developers much development skils by using yours outstandingproduct.
Hi Janusz. Welcome to the Corona Labs forums.
I think you’re going to find getting Corona-made apps to work with screen readers near impossible. With the exception of the “native.*” API calls, everything else that gets drawn to the screen is a graphics texture. Unlike HTML, which has hidden meta-data for images like “alt tags”, Corona doesn’t have any such metadata and there is no facility to add such data.
With a web page, text content (HTML, CSS, JavaScript) is downloaded to the browser where the browser renders any graphics, but because the HTML text exists, screen readers are able to function. For applications like Corona, yes, our menus and dialog boxes will work but that’s because it’s actual text being rendered by the operating system. But when it comes to the built app itself, think of the screen as one big image with no text to describe it.
Rob
Dear Rob, thank you very much for yours qualified answer. But even if yours product can not create accessible GUI for users who are using screen readers, receive my deepest possible appreciation to yours excellent work. Apps which are created by yours environment can look very attractive, its load time is very fast and reliability of compiled code is outstanding. The main problem is, that The core developers of Talkback do not wan to support C apps, which are using Native Android activity. So even if yours product would not write graphics, it would not be able to run. This is The reason, why apps must contain special Java bridge, which creates bridge between Java code and native C code. So .java code and .xml files contain buttons and app GUI, and C compiled code from .so libraries is executing The appropriate action based on user input from GUI. If user click on some button, menu item, ETC. The main disadvantage of this enforced approach is, that reaction speed of Talkback is slower than if app would be written entirely in Java. VLC media player, or apps, which have been written in C++ by using Android QT creator IDE also contain similar accessibility bridge. But it may even cause random crashes of apps. So sure, yours approach, which you have incorporated to The compile and build algorithm is much more better. And yours approach is really ideal for creating professional looking games and other apps. In fact, only users of assistive technology, which are using Explore by touch Android service are excluded from using yours professional and stable solution. It is reality of visually impaired and every one must accept The fact, that not all apps will be usable. I can use Android Studio, Eclipse with Java, QT Creator for Android, or Lazarus with Lamw special installable package for Lazarus. Which produces Java bridges to create accessible GUi. I wish you many programmers achievements and much busyness achievements. And really. Thank you again for yours fast and qualified answer. I wish all sighted developers much development skils by using yours outstandingproduct.