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

Clean up aXe audits #6169

Closed
paulirish opened this issue Oct 3, 2018 · 3 comments
Closed

Clean up aXe audits #6169

paulirish opened this issue Oct 3, 2018 · 3 comments
Assignees

Comments

@paulirish
Copy link
Member

paulirish commented Oct 3, 2018

The axe gatherer is now frequently one of the slowest parts of our run. A few of their checks are particularly slow, including color-contrast and td-has-header Due to the response on the td-has-header item, I started looking into disabling the td-has-headers check for now. But this turned out to be more amusing... Follow along. 👇


I figured I'd disable it in the axeConfig and then remove the audit file.

However, there's no audit js file. :)
Yes, that means we've been incurring the cost of this check and not even showing the results. 😭

Apparently that audit file was removed partway through the PR that added most axe audits.


I compared what audit files we have vs the results that aXe currently returns and found a few cases where we're doing unnecessary work:

No LH audit file for existing aXe result

  • td-has-header
  • table-fake-caption (also removed in that PR)
  • marquee (??)

My preferred action is to disable the above to start. We can add them back in as necessary. OK with you, @robdodson?

@robdodson
Copy link
Contributor

sgtm, though I'm a bit surprised by a few of these. All of the ones mentioned in the right column never return an axe result?

@paulirish
Copy link
Member Author

paulirish commented Oct 3, 2018

All of the ones mentioned in the right column never return an axe result?

Ah, I bet that those 4 were actually 'passing', but we set resultTypes: ['violations', 'inapplicable'],, so we just didn't receive data about them. I'll confirm that, but we can assume that's the case. :) (edited the issue above)

@paulirish
Copy link
Member Author

fixed by #6180

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

No branches or pull requests

3 participants