Why does the accessibility gatherer run when running just SEO audits? #16795
Description
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).
- Yes, my issue is not answered by other FAQs.
URL
What happened?
I run this CLI command:
lighthouse https://www.walmart.com/ --onlyCategories=seo
And the console output includes this:
LH:status Getting artifact: DevtoolsLog +7s
LH:status Getting artifact: Accessibility +0ms
LH:status Getting artifact: AnchorElements +210ms
LH:status Getting artifact: LinkElements +30ms
What did you expect?
I don't think the SEO audits depend on the accessibility artifact, so I would not expect it to be collected. It's also not listed in filterResistantArtifactIds.
What have you tried?
No response
How were you running Lighthouse?
CLI
Lighthouse Version
13
Chrome Version
No response
Node Version
No response
OS
No response