-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Fast Pass and using iFrame #6874
Comments
Hello, @kirstenschaff! Thank you for using Accessibility Insights for Web! Are there any warnings about unresponsive iframes when you run FastPass automated checks? If so, it might be related to #6347 Can you either link directly to a page that this happens on or provide a minimal reproduction in something like codepen? This will allow us to best debug and assess the situation so we can take action. Thanks! |
The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights! |
Okay, this is helpful! Thank you! @kirstenschaff in order for Accessibility Insights to reach the iframe, the team will need to click the link in the banner on the automated checks tab saying, "give Accessibility Insights additional permissions" and then confirm in the dialog that pops up. This allows the extension to access iframes in the page. Once additional permissions are granted, the extension will have those additional permissions while installed. |
The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights! |
Thank you. The team has tried this and are now able to use information within the iframe. |
When I am trying to test tabbing in embedded Power BI reports the tool doesn’t show tab stops (even though my focus in on an element inside of the report)
The tool also will not show issues inside of the iframe (like regions or missing area labels). It stops at the iframe that is displaying the report.
The text was updated successfully, but these errors were encountered: