leo stone

Hm, then one workaround would be, to have NVDA running, Ha,Ha,Ha. Regarding the --force-renderer-accessibility flag, would it not be good, to have short description on how to add this, when chrome is the default browser, so the flag is added, regardless from which application a link is opened. It probably involves registry entries, I haven't googled for it yet. Well, now I did, it involves changing at least one entry: HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command\Default from "C:\Program Files...

Hm, then one workaround would be, to have NVDA running, Ha,Ha,Ha. Regarding the --force-renderer-accessibility flag, would it not be good, to have short description on how to add this, when chrome is the default browser, so the flag is added, regardless from which application a link is opened. It probably involves registry entries, I haven't googled for it yet.

Hi there, yes I've only realized afterwards, that you are actually very aware of this issue, and also that you seem to have implemented both ways. I've stumbled over some information that you might want to have a look at. https://github.com/progietheus/Google-Chrome-URL-Check-C-Sharp related stackoverflow thread: https://stackoverflow.com/questions/18897070/getting-the-current-tabs-url-from-google-chrome-using-c-sharp To me it looks like, if you would be using the UIAutomationClient.dll that this...

Web accessibility not activated in Chrome