Steven Lambert

Thanks for the suggestion. We'll look into what it would take to implement this. Since the original issue and this suggestion are a bit different, I'm going to update the...

Thanks for the issue. We can probably add a note to the [result array section of the api docs](https://github.com/dequelabs/axe-core/blob/develop/doc/API.md#result-arrays) that documents that `failureSummary` is only for nodes in the `violations`...

Thanks for the update.

Thanks for the issue. I can see a few issues with our code that allows those not to get flagged. The `rp` one in particular is always hidden by default...

Gotcha. Testing it out it looks like we return Needs Review for the `rp` element when it's visible.

Thanks for the update. Do you happen to have a timeline for when these changes will go into the spec? The hard part of implementing this is that we don't...

Part of this ticket will need to include commonizing the handling of descendants of targets that can change the true clickable size of the target (such as an image inside...

@professorplumb Unfortunately there is no way to tell axe-core to ignore a specific violation, nor is there a good way for axe-core to detect the purpose of these tracking pixels...

Thanks for letting us know

This should pass for the 2 cases: * link being wrapped by a `u` element * link with graphical content (`img`, `svg`, `canvas`, `object`, etc.)