-
Notifications
You must be signed in to change notification settings - Fork 789
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
Unable to test contrast of nodes scrolled out of view #3772
Comments
In case it helps with prioritization/sense of scale of the issue: We were just doing some validation of axe-core 4.5.0 in preparation for upgrading Accessibility Insights for Web and found that 4.5.0 detected about 90% fewer color-contrast issues in our big corpus of test sites compared to 4.4.1 (78 vs 836 issues detected). Based on spot checking the cases with different results I suspect this is probably the root cause, but I didn't verify every case. |
@dbjorge axe-core 4.5.2 was released and should fix this issue. Would you be able to pull it down and test it to see if it returns results as expected? |
Yes, I'll rerun with 4.5.2 against our big batch of test sites overnight tonight! |
Yes, that resolved most of the differences. I did find one class of failure that was reported in 4.4.1 but still not in 4.5.2. It involves a specific type of carousel control currently used in a few Skype marketing pages. An example is the bottom of the main content in https://www.skype.com/en/content-creators/ (I tried to make a more minimal repro but gave up after 5 minutes). This specific control has a few reported I think it'd be pretty questionable to call this case an axe-core bug - the content in question is completely off-screen inside a container which uses |
Still seeing the issue, even when validated with the latest axe-core develop branch code base, Screen.Recording.2022-11-23.at.4.54.29.PM.mov@straker , can you please provide your observations here on this |
Validated with the latest code base of axe-core develop branch,
even after scrolled, |
This problem was introduced in axe-core 4.5. When an element is scrolled out of view, it is not included in the grid, which results (among other things) that it is reported as incomplete once its scrolled out of view.
Here's how to reproduce the problem. These logs should report the same, but the second one reports incomplete instead of a violations.
The text was updated successfully, but these errors were encountered: