I'm developing some UI Automation work for a WPF program in VB.Net and have had great success. . . until trying to automate Web Browsers.

With Chrome there's --force-renderer-accessibility which was a Godsend, but it appears despite having been built off of Chromium they've disabled this flag on Microsoft Edge. . .

is it possible they have renamed the flag? Anyone else know how to force Microsoft Edge to be in accessibility mode? I have looked at

It gives me a TON of errors as shown,, but the button is there, albeit the text from the page is not.

If I change the registry setting, I get the text, but still get all the errors for the element.

Lastly, if I open MSEdge.exe via this command: start "Title for fun here" msedge.exe --force-renderer-accessibility "URL here" not only will the text show up, but so will the information for the element I'm searching for!

As to what @Jimi mentioned in the comment, I believe this issue with persisting MSEdge processes when clicking on the X button only occurs if the MSEdge Performance Boost is enabled. I had found an article at some point, but with all the searching and frantic "Oh goodness no, I have to jump to Selenium?!?" moments I've had recently with trying to automate Edge, I've lost it in the swamp of my browser history. If I find it again, I'll post the link in this answer.

If anyone has a better way of doing this very same thing outside of the flag, please, feel free to give some insights!