Improve ad-hoc visualizations on cross-origin iframes

[karanbirsingh]

Is your feature request related to a problem? Please describe.

Some websites reference cross-origin iframes. Our extension requires additional permissions to run scripts on such pages.

If a user runs an ad-hoc visualization without granting these permissions, the extension silently ignores results in these iframes. My example is headings, but other visualizations like tab stops are similar.

missing headings in an iframe (demo page)

However, the user is not presented with a permissions banner in the ad-hoc panel. They need to open the details view and run a scan.

after granting permissions:

Describe the desired outcome

A user reached out to us internally asking why the tool wasn't finding their iframe's heading. It would be good if we can reuse the banner UX, or consider an FAQ / setup question to address it.

Describe alternatives you've considered

We have UX for this for automated checks - when a user attempts either flow, we show a banner:

We could consider something similar.

We have a section in our FAQ that talks about cross-origin iframes, but it assumes the user has seen the banner.

[ghost]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[ferBonnin]

as discussed with the team, we will wait until we hear more from users on this edge case scenario. @waabid mentioned he has some ideas on how to tackle this

[ghost]

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

[waabid]

My idea was to add something like this:

This extra text on the bottom would only show if permissions were not granted. I believe we could decide then what this should do: ask for permissions or point to the "learn more" page. The latter might be more appropriate if we feel like the text isn't sufficient and we want to add something longer (that might not fit as nicely and hence, maybe something short for the learn more page).

[ferBonnin]

Per conversation with Peter, moving to await community interest to check if this is an issue

[DaveTryon]

Unfortunately, this is out of scope given our current priorities.

Thanks for using Accessibility Insights!

[rickynyairo]

Hi @DaveTryon I experienced this same issue recently. If you have resolution on how to fix it, e.g as suggested by @waabid , I'd be happy to take it up and raise a PR.