Issue on using the Active Accessibility UI Framework after Browser Upgrade

[Jerry1 (Jerry)]

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

[sven.wullum1]

Hi!

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

UiPath Chrome Manifest V3 Extension Released with 2022.4 Update

UiPath Chrome Manifest V3 Extension Released with 22.4 Update Context The adoption of Manifest V3 represents one of the biggest shifts in the Google Chrome extensions platform since it launched a decade ago. Extensions using Manifest V3 will enjoy enhancements in security, privacy, and performance. The new UiPath Chrome MV3 extension We’ve implemented a completely new extension following the Manifest V3 standard released by Google. This new extension can be installed from both Studio ->Tools…

[Anil_G (Anil Gorthi)]

@Jerry1

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

Broken selectors after Chrome/Edge update to version 114.0.1823.37

The latest Chrome and Edge updates (114.0.1823.37) introduced a breaking change to the way support for Active Accessibility is enabled. This causes automation processes to fail when trying to interact with the following browser screens: Print popup PDF viewer Observed behavior Following the browser update, it is no longer possible to identify web elements using Active Accessibility (AA) mode with UIAutomation activities. Example of selector that no longer works because of this issue: <wnd…

Hope this helps

cheers