Your caution isn't wrong, but ultimately it may be futile.
Inevitable, you have to reach out to the specifics of the UI end, but for most of the tests all you may need is - Run App, Accept Some License / Button, Press something else, then something else - and it elevates some confidence that at least it can run and go that far (sometimes changes can break even this).
So such tests can be coded by completely autonomous team, not having to deal with how you've build the software to begin with, or coordinate changes you've made later (apart from how the UI works).
You're offering a retort to someone who is communicating their position that you ought not do something, where the retort consists of nothing more than explaining that people are doing it. Yes, clearly. But what the person you're responding to is arguing is that you ought not do it.
Consider the following hypothetical:
Person A: Here's little advice: don't take up smoking. Smoking is bad for you.
Person B: Yet people smoke—my cousin, for example.
The point of the other comment wasn't that it isn't happening or that it's physically impossible to even try. Indeed, the fact that it's being done—or that people are attracted, at least, to trying to do it—was rather the entire premise of their "word of caution".
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?
> Dear ImGui is designed to enable fast iterations and to empower programmers to create content creation tools and visualization / debug tools (as opposed to UI for the average end-user). It favors simplicity and productivity toward this goal and lacks certain features commonly found in more high-level libraries.
Here's a quote from my comment [1] on an earlier discussion about Dear ImGui vs. "bloated" browser APIs:
> This is what I hear when I enable VoiceOver on macOS and open Discord (either the web app or the desktop app):
> 1. “Discord, friends - Discord window, direct messages, selected cell”
> 2. “You are currently on a cell inside of a table. To navigate the cells within a table, press…”
> 3. (when navigating with the keyboard) “1 mention, $SERVER_NAME, cell” “$SERVER_NAME, cell” etc
> And here’s when I do the same with a random Dear ImGui app I have installed:
> 1. “$APP_NAME, $APP_NAME window, $APP_NAME window”
> 2. “You are currently in a window”
> 3. (when navigating with the keyboard) [silence; no additional instructions]
[1] https://news.ycombinator.com/item?id=37302809