--force-renderer-accessibility not working in chrome

[Sushmitha.C]

Hi,

I have used --force-renderer-accessibility at the end of url to enable UIA mode in bp to interact with Chrome. This works fine in all Machines except one particular machine. Where --force-renderer-accessibility not enabling accessibility options in chrome and UIA mode is failing to identify element. wondering what could be causing this issue.

[harish.mogulluri · Accepted solution]

Hi Sushmitha,

Which version of chrome you are current encountered this issue?
Check below article from Knowledge Center.  after you click the below link, You need to login as a customer>Use blue Prism portal credential - to open this link

https://support.blueprism.com/en/support/solutions/articles/7000084193--important-notification-updated-21-nov-23-latest-versions-of-google-chrome-and-microsoft-edge-brow

[stepher · Accepted solution]

Hello, Sushmitha,

We do our web automations in the Chromium version of MS Edge, not Chrome directly.  However, there was a change a while back where the parameter '--force-renderer-accessibility' needed to be updated to '--force-renderer-accessibility=complete'.  Not sure if this is applicable to Chrome, but I imagine that it is.  Also, not sure why you would be seeing differing behavior between machines.  I would hazard a guess and say that it had to do with the version of the Chrome browser.  Left to their own devices, both Chrome and Edge deliver updates whether you ask for them or not.

Good luck,

Red

[Sushmitha.C]

Sol: it was issue with chrome version 117. the error is not happening in other version.