Skip to content
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

Background and foreground colors have a sufficient contrast ratio error axe-core Error:Cannot read property 'cells' of undefined #12039

Closed
bhaskar1603 opened this issue Feb 3, 2021 · 15 comments · Fixed by #13441

Comments

@bhaskar1603
Copy link

Provide the steps to reproduce

  1. Run LH on https://gurugramproperty.in/

What is the current behavior?

shows red Question mark on accessibility test for both mobile and desktop report
Background and foreground colors have a sufficient contrast ratio error axe-core Error (Cannot read property 'cells' of undefined)

What is the expected behavior?

Shall show the accessibility score .

Environment Information

  • Lighthouse version: 6.4.0
  • Device: Emulated Desktop
    Network throttling: 40 ms TCP RTT, 10,240 Kbps throughput (Simulated)
    CPU throttling: 1x slowdown (Simulated)
    Channel: devtools

User agent (host)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.104 Safari/537.36

User agent (network)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4143.7 Safari/537.36 Chrome-Lighthouse

CPU/Memory Power
1483

Axe version
3.5.5

Related issues

@patrickhulce
Copy link
Collaborator

Thanks for filing @bhaskar1603! This appears to have already been fixed in Lighthouse 7.0 with the latest version of axe. You can use Chrome Canary for now as a workaround or if you're still able to repro with axe-core, welcome to file an issue over there :)

@patrickhulce
Copy link
Collaborator

I can't reproduce this with the settings you specified in #12043 either. Is there any additional information you can provide? Any additional steps or settings used? Is it possible there's a local extension being used that causes this to happen?

Using just axe-core I also cannot reproduce this error.

@bhaskar1603
Copy link
Author

I didn't used any additional step. can you please specify what else info can i provide
Screenshot (52)

@bhaskar1603
Copy link
Author

i don't have any extentions installed

@patrickhulce
Copy link
Collaborator

I still can't reproduce :/ but there appears to be a nearly identical error open bug at dequelabs/axe-core#2674. If it's the same root issue, when axe-core fixes it Lighthouse will be fixed on the next update.

@Scrabble96
Copy link

I've just had this on Google Chrome Version 88.0.4324.150 (Official Build) (64-bit) and on Microsoft Edge Version 88.0.705.68 (Official build) (64-bit) on Windows 10 Pro. Both are using Lighthouse 6.4.0.

This did not happen last week.

Lighthouse-axe-core-error

@phamhuanmko
Copy link

My website also has this error! Who can help me!
image
My web is: https://hungthinhclinic.com/
Thank all

@gwenevieve
Copy link

Also having this error on one of my sites. 'axe-core cannot read property '4' of undefined'.

@Dawntraoz
Copy link

In my articles page is also happening https://www.dawntraoz.com/blog/my-web-performance-journey-with-nuxt-storyblok-netlify/.
When I pass the AxeDevtools it shows me 0 issues but in lighthouse I get the question mark.
The problem is the scrollable divs I have for code blocks, when I removed them everything it works just fine.

If I can help with some debugging let me know :)

@Dawntraoz
Copy link

For me, it already works in the last 8 version!! 🏄🏽‍♀️ Thank you folks!

@davidstellini
Copy link

davidstellini commented Aug 12, 2021

Reproduced on latest Chrome Canary Version 94.0.4605.0 (Official Build) canary (x86_64).
To reproduce run on https://allfront.io
image

@Lucania001
Copy link

Still the same issue on https://zenbears.co.uk. We are 90-100 on everything so this is frustrating

@bluepeter
Copy link
Contributor

This is definitely still an issue for us on various sites/pages.

@Lucania001
Copy link

To confirm I fixed the issue with zenbears. Mine was my offscreen nav was causing havoc. Make sure any off screen elements that you only want rendered with JS or on click have display none set

@digiage
Copy link

digiage commented Sep 29, 2021

The same error for https://digiage.cz. Chrome 94, Lighthouse 8.3, Axe 4.2.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.