Pseudo element contrast failure too invasive?

👋

I’ve run into a situation where :nth-child style pseudo selectors are wrongly being identified as pseudo elements and therefore, can’t assume contrast acceptance. I’ve tracked down to this section here, but it does seem to only be checking for :before and :afters. Maybe something in the function being called?

https://github.com/dequelabs/axe-core/blob/f2f15377c917d0b6fc27d2181f64ebef26e5a9b0/lib/checks/color/color-contrast-evaluate.js#L103-L116

Anyhow, here’s also a screenshot showing the run through using the Chrome plugin and the result:

[straker]

Ok. We added the option and it should be available in the next feature release (coming in the next few weeks hopefully). Do note though that turning off the option may result in a Needs Review item being marked as a failure, so you’ll need to watch out to see what it will change for your tests.

[straker]

@craigkovatch the UI changes wouldn’t affect the js library. We’ll add an option to disable the pseudo check of color-contrast so you can turn off these warnings if you want.

@clottman for this one, let’s check in the pseudo algorithm the display and visibility of the element, if it’s none or hidden (respectively) we shouldn’t flag it as having a pseudo element. Additionally, let’s add an option to disable the pseudo check entirely. Let’s call it ignorePseudo to match the other options we have, and set it to default to false.