[BUG] Accessibilityinsight v1.1.2360.01 reports chromium components issues

[alanPage2]

when testing a windows application with accessibility insights v1.1.2360.01
it says chromium components should be scanned with a web-based scanner and many errors reported

please check if there is a way to handle this? I am testing this windows application that has many web components, its not possible to test this with a web version of accessibility insights

thanks guys!

[madalynrose]

Hi, @alanPage2! We made this change because Accessibility Insights for Windows can basically say "Something is wrong with this HTML app", but it can't tell you what to do about it. Accessibility Insights for Web understands HTML and can point out the specific problem. If you can render the HTML in a standalone browser where Accessibility Insights for Web is installed, you'll end up with far more actionable results.

Your best path forward is to isolate your HTML and render it in a browser where it can be inspected with Accessibility Insights for Web. Inside of Accessibility Insights for Windows, ignore all results under the BrowserRootView window.

If you are unable to render the HTML separately, your second best option is to review the automated checks results in the Test view, then filter out the error about Chromium. Issues will still be reported against items inside the WebView control, but it will be much harder to try to figure out what to change to address the reported issues--some of them may even be handled completely by the browser and therefore outside of your ability to directly influence.

Thanks for using Accessibility Insights!

[alanPage2]

thanks Madalyn! your answer is much appreciated!
how about the 3rd option here to use an older version of accessibilityinsights like v1.1.2213.01, does that help with my windows app or no that we may miss more important issues if we keep using older version?

[madalynrose]

Hi, @alanPage2!

We don't recommend using an older version and don't make older versions of Accessibility Insights for Windows available for download.

We do have an issue related to the scanning Chromium-based UIs in the axe-windows repository so keep an eye there for updates: microsoft/axe-windows#836.

Closing this issue in favor of the issue in axe-windows.