I was looking at feathers UI demo when it hit me: the DOM has support for accessibility features such as talk back and tabbing through menus, general content and descriptions for images.
When developing in each platform’s native engines, support for a11y is also there.
What is the state of a11y in openfl for the multiple targets it supports? how does the community handle this matter? I know that for games, this is not generally a concern, but for other types of apps it definitely should be.
I started thinking about possible implementations to tackle this problem and am willing to start learning how to integrate openfl display list with the a11y features of each platform, in the case openfl/lime is lacking it (I really don’t know, couldn’t find relevant sources, but I admit I didn’t spend too much time searching).
Hope this is an interesting discussion for the community!