accessibility-insights-web
accessibility-insights-web copied to clipboard
Color-contrast produces false-positive on elements during transition/animation
Describe the bug
Color-contrast produces a failure in automated checks on an element while the DOM may be animating/transitioning around it.
To Reproduce Steps to reproduce the behavior:
Note: these failures are not real failures and only occur randomly and rarely.
- Go to https://visualstudio.microsoft.com/
- Scroll to the carousel.
- Keep scanning until issues are seen (like screenshot below).
Expected behavior
These should not be errors.
Screenshots
Context (please complete the following information)
- OS Name & Version: MacOS Big Sur
- AI-Web Version & Environment: Version 2.25.0
- Browser Version: Edge 90.0.818.46
- Target Page: https://visualstudio.microsoft.com/
Are you willing to submit a PR?
Yes
Did you search for similar existing issues?
Yes
Additional context
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!
per triage conversation, assigning to @waabid
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!
A similar issue was found when there is white text overlaying images with lazyload behavior. Before scrolling down to the images, AI Web would find the color contrast issues. The color contrast issues are not present when scrolling down the page far enough to load the images (no color contrast issues by the time the user can view the images/text). Additionally, the color contrast issues are not present when CSS is disabled for the page.
The service has a bit at packages\scanner-global-library\src\page-navigation-hooks.ts
that injects some CSS that disables animations on target pages. I think we have similar in our own e2e tests of ourselves. We might consider applying something similar to target pages.
After reviewing the full list of issues in our backlog, we have concluded that we will not be addressing this issue.