Lamdatest giving more detailed audits on contrast as compared to lighthouse

### FAQ

- [x] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [x] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
- [x] Yes, my issue is not answered by [other FAQs](https://github.com/GoogleChrome/lighthouse#faq).

### URL

play.geforcenow.com

### What happened?

Lamdatest extension is giving more detailed audits as compared to Lighthouse audits on accessibility issues.

Lamdatest :

Lighthouse:

Mainly, the contrast audits are passing in lighthouse but failing on lambdatest.
Both of them seem to use the same guidelines, WCAG.

**I filed this issue with axe-devtools, they asked me to report it on lighthouse instead.
https://github.com/dequelabs/axe-core/issues/4778#issuecomment-2919001360**

### What did you expect?

I wanted to see the full detailed list of accessibility audits that were missing on lighthouse.

### What have you tried?

_No response_

### How were you running Lighthouse?

Chrome DevTools

### Lighthouse Version

12.5.1

### Chrome Version

136.0.7103.114

### Node Version

_No response_

### OS

_No response_

### Relevant log output

```sh

```

Start with the reported URL, Lighthouse 12.5.1 in Chrome DevTools, and the LambdaTest screenshots; compare the contrast findings against the referenced axe-core discussion. Identify which accessibility audits differ and whether the contrast result is reproducible, then document the cause or the missing Lighthouse audit coverage.

Written by the indexing model from the issue text.