Issue on using the Active Accessibility UI Framework after Browser Upgrade

We encountered difficulties in an automation where we needed to capture data from a website. Appropriate selectors were not available for that, but we were able to resolve the issue by using the UI Framework called Active Accessibility in the Ui Explorer.

This workaround had been working well for the past 2 years. However, it has stopped working since yesterday. After investigating, we discovered that this is due to a browser version upgrade. The workaround is still effective in the older browser version.

Currently, we are unable to indicate the window or obtain proper selectors using the Active Accessibility UI Framework. This issue is not limited to a specific website but is affecting all other websites as well. Please refer to the screenshot below.

Browser: Edge
Updated version: 114.0.1823.37 (official build) (64-bit)
UiPath version: We are using an old version, but the same issue persists in the latest version as well.

Any suggestions or fixes for this issue?

Thanks :slight_smile:


Sounds like you’ve run into Chrome Manifest V3.
Take a look in this thread:

1 Like


Please check this. If using modern activities a work around is provided for now. If not downgrade the browser. UiPath is working on it and can use the workaround in the mean time

Hope this helps


1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.