|
|
|
|
|
by thezilch
905 days ago
|
|
Why should internal tools not have these things? That kind of argument smells of, internal tools can be slow. No. Seems we should lift up Dear ImGui -- contribute, donate, feedback (document, gather requirements, etc), etc -- as opposed to suggest we not use it. |
|
But any effort to document, specs, clarify etc would be helpful and not just to Dear ImGui.
Accessibility is a whole world that is hard to grasp when you are not a end-user, API are large, confusing, poorly documented, and I presume that there are a large variety of tools and use cases and it's even hard to gauge what are the low-hanging fruits that would be the best to implement/bind.
Given how obfuscated Web stacks are nowadays (since they do try to prevent unauthorized scrapping and automation), I'm honestly also a little bit surprised that nowadays screen readers aren't relying on OCR more?