San Diego Next Experience UI does not allow UI Path software to recognise any elements on the screen. What do i need to do to get this working.

[Andy S]

We are enabling Next Experience in a phased Pilot after upgrading to San Diego back in May.

We have noticed that UI path software was successfully able to recognise all elements of San Diego platform screens before we switched on Next Experience. This is worrying for us as we do have users in the business who rely on screen readers to help them with their role. We are going to be asking them to regression test Next Experience with some screen reader tools. The initial question is around UI path because we rely on that to identfiy elements and click on elements for execution of scripts.

Is there a plugin required to allow UI Path to work with San Diego Next Experience.

[Maik Skoddow]

Hi

Shouldn't you better ask the manufacturer for "UI Path"?

A workaround is offering your users to decide by their own, whether they want to enable the Next Experience or not. Please see my article: Allow users to switch between Next Experience UI and UI16

Kind regards
Maik

[Andy S]

Thanks Maik, I was hoping that i could understand what had changed in Next Experience to stop the screen reader technology from working.

[Brad Tilton]

Hi Andy,

The new Next Experience UI adds a header and wrapper to the UI built on our Next Experience Framework, which uses a shadow dom that can make it difficult for tools that do a lot of dom inspection, if that makes sense. All that being said, I think we should still be supporting screen readers, but if you have your users do their testing with their screen readers and run into issues I would absolutely open a support ticket so we can get this logged.

[Andy S]

Thankyou Brad. 

That explains the change we are seeing.

Our screen reader testing will continue next week and conclude. I am inclined to raise a HI ticket but will hold off until we have the final testing result by the end of next week.

Cheers