![]() ![]() It's basicly the same for OpenGL, SDL, or on the web, or any library rendering something without specific accessibility support. Not in detail - but conceptually.Īs you have already well identified, your app is an accessibility blackhole because you are using a rendering engine. TL DR: How to provide screen-reader compatibility from scratch. Can someone point me in the right direction? However, I have a tough time finding resources and jump-in points to explore this topic. I'm fully aware this is far beyond the capability of a sole developer and know, that writing programs by ignoring native interfaces is a common accessibility hole, which you are advised to avoid. I'm finding a lot of information on this, with a framework as a starting point, but have a hard time finding resources on how to do it from scratch. How would that be possible on Windows, Linux, BSD or even android? In the *NIX world, I presume this would be Desktop environment dependent. How can I provide an interface for screen readers to cling unto? I presume this is a per OS thing. As such, standard screen readers like NVDA have no chance of picking up information ( excluding OCR ) and my applications are an accessibility black hole. All rendering happens in OpenGL, with a context provided by GLFW, all in C, with no framework to rely on supplying compatibility. I create applications, that are divorced from any native framework. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |