search

GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.
https://developer.chrome.com/docs/lighthouse/overview/
Apache License 2.0
28.4k stars 9.38k forks source link

Accessibility review failing - it looks like contrast ratio is the cause (as it is in Error! mode) - both latest Chrome and Canary, Win10 #11384

Open BogdanCerovac opened 4 years ago

BogdanCerovac commented 4 years ago

Tested locally, on two different Windows 10, both evergreen Chrome (Version 85.0.4183.83 (Official Build) (64-bit)) and Canary (Version 87.0.4254.0 (Official Build) canary (32-bit)).

Axe did not have any problems v4.5.3 (axe-core 3.5.5)

Provide the steps to reproduce

  1. Run LH on:

What is the current behavior?

Accessibility KPI gets a question mark, Contrast check seems to be the cause as it falls into Error state

What is the expected behavior?

Accessibility KPI should get a point, Contrast check should report some errors (according to Axe)

Environment Information

Related issues Potential cause either contrast eval or maybe missing manifest.json, no other messages in the console

patrickhulce commented 4 years ago

Thanks for filing @bogdancerovac! It's a bug in axe-core see https://github.com/dequelabs/axe-core/issues/2483 for progress.

BogdanCerovac commented 4 years ago

@patrickhulce - thank you!

sergeykish commented 4 years ago

I've got same problem, very confusing — low contrast ratio with default colors http://sergeykish.com/web-api-element-prototype-queryxpathall.

Reproduced original issue on https://web.dev/measure/.

Not reproduced on Chrome Version 85.0.4183.121 (Official Build) Arch Linux (64-bit).

Issue was not found by "Background and foreground colors have a sufficient contrast ratio Error!", maybe now it will.

anisse commented 3 years ago

Hi, my website is affected by this issue:

https://anisse.astier.eu

https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?url=https%3A%2F%2Fanisse.astier.eu

It also seems #12613 might be a duplicate.