axe-core version is out-of-date (with fatal bug)

[mohmadt93]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

https://hungry-goldwasser-e4dfda.netlify.app/

What happened?

At the time I ran lighthouse audit before the v8 update and it didn't show this error.
But since then I get "Error!" or "?" for SEO audit.

Plus:

• when SEO and Accessibility are checked, both audits show an Error,
• Accessibility has 44 Error logs, SEO has 3 Error logs
• Link: https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fhungry-goldwasser-e4dfda.netlify.app%2F

• when SEO is unchecked, Accessibility shows 100%

• when Accessibility is unchecked, SEO still shows Error

This are the logs for SEO audit

• title does actually exist and is visible in source code

So I assume it has something to do with SEO audit, which is somehow linked to Accessibility.
If I run the LH audit in DevTools there is no Error at all.

What did you expect?

I expected 100% because actually there doesn't seem to be a real issue with the code.

What have you tried?

-CLI, WebDev Measure, DevTools

• doesn't work for both mobile and desktop audit
• Operating System: macOS Big Sur

How were you running Lighthouse?

CLI, PageSpeed Insights, Chrome DevTools

Lighthouse Version

8.0.0

Chrome Version

91.0.4472.114

Node Version

No response

Relevant log output

No response

[patrickhulce]

Thanks for filing @mohmadt93! This is a bug in the accessibility library Lighthouse uses (dequelabs/axe-core#2965) and was fixed recently, we just need to update on our side.

[mohmadt93]

Thanks for filing @mohmadt93! This is a bug in the accessibility library Lighthouse uses (dequelabs/axe-core#2965) and was fixed recently, we just need to update on our side.

Hey @patrickhulce, I was wondering if the update is already done, because the issue isn't resolved for me. Or can you tell me how I can recognize when it is finished? Kind regards

[patrickhulce]

@mohmadt93 The update has been done, but a new version of Lighthouse stable hasn't been released yet that includes the change.

You can use v8.0.0-dev.20210627 on npm if you want to test it immediately.