-
Notifications
You must be signed in to change notification settings - Fork 151
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
[Tracking] AIWeb skips unresponsive iframes #6347
Comments
we will monitor every week for a month and revisit if needed |
This has started to show up as an issue when testing components within our Storybook site for Microsoft Graph Toolkit. Load this url: https://mgt.dev/?path=/story/components-mgt-agenda--simple OS: Windows 11 Enterprise AI-Web Version: 2.38.1 Browser: Microsoft Edge for Business Is there any known work arounds I could look into? |
Hi, @gavinbarron! We've looked into this, and StoryBook's IFrames can't be scanned by Accessibility Insights for Web. StoryBook is sort of an artificial hosting environment, so we don't recommend it as a test bed for assessing the accessibility of your controls. You'll get a much more meaningful result by hosting your control in a simple test page and scanning that page using Accessibility Insights for Web. As an alternative, StoryBook has an accessibility add-on that is intended to provide accessibility testing within StoryBook. This add-on is based on axe-core (the same engine used by Accessibility Insights for Web), but because it uses a 2020 version of axe-core, its results may be somewhat behind current WCAG standards. Thanks for using Accessibility Insights! |
Hi,
|
@TaliHausner did you ever get more followup on this? we are now seeing this in some of our reactview blades in the azure portal as well |
Describe the bug
Our extension makes a best-effort attempt to scan child iframes - we send messages to the child frame and wait for a small timeout. If the child frame does not respond by our timeout, we skip the child iframe. This is a tracking issue for cases when the extension skips child iframes unexpectedly.
If you are running into this issue, please comment below with the following information:
Context
The purpose of this issue is to track all known instances of AI web skipping iframes unexpectedly. It is pointed to in the iframe skipped warning banner, added in #6330
The text was updated successfully, but these errors were encountered: