[Feature Request] Interest in supporting IA2?

[sivakusayan]

Is your feature request related to a problem? Please describe.
There isn't currently an updated IA2 inspector for Windows. aViewer doesn't seem to be in active development, and unless I'm doing something wrong it's crashing on startup on Windows 11 for me. The legacy inspect tool can only look at MSAA. The dump tree utility only works for browsers, and it doesn't allow me to manually invoke functions on a node's interface which could be useful at points.

Describe the solution you'd like
I think it would be really nice if IA2 support could be added to Accessibility Insights for Windows, seeing as its the most feature-rich accessibility inspector on the platform right now (that I know of).

Describe alternatives you've considered
I described the alternatives I've considered in the first question.

Additional context
If there is interest in this but not bandwidth, I'd be happy to try my hand at a small prototype of this. Although from what I've seen in other issues here, significant features like this will usually need some sort of design first, and I'm not sure if there is some sort of process there.

Edit: I just looked at previous issues and notice a similar MSAA request was closed. I think that makes sense, but I'll pre-emptively mention that I'm not sure if the same line of reasoning could be used for IAccessible2. I'll admit that I'm not sure how common each API usage is, but at the very least there are two major IAccessible2 providers (Chrome and Firefox), and two major clients that I believe use IAccessible2 by default (NVDA and JAWs). Finally, UIAutomation and IAccessible2 are not necessarily one-to-one exchangeable with each other, as there are semantics each API can express that are not expressible in the other.

[microsoft-github-policy-service]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[microsoft-github-policy-service]

This issue has been marked as being beyond the support scope of Accessibility Insights. It will now be closed automatically for house-keeping purposes.

[peterdur]

Thanks for making this suggestion, and for your kind words about Accessibility Insights for Windows! We discussed this suggestion. Recognizing that IAccessible2 support is complex to implement for architectural reasons, that IAccessible2 is primarily exposed by browsers, and that we recommend that browser experiences be tested with our Accessibility Insights for Web product, we have decided not to implement this suggestion.