Steven Lambert

Looks like axe is reporting correctly. The use of roles on the `li` or `ul` elements is causing the issues. We can update the report to include information about that...

Thanks for the issue. When we created the check two years ago, [assistive technologies didn't support it very well](https://github.com/dequelabs/axe-core/issues/1216#issuecomment-454104190) for non-interactive elements. That may have changed in the past years,...

Thanks for the issue. This one's going to be a bit difficult to report on correctly so we might just have to ignore elements with `content-visibility` all together as the...

How do we want to classify the hidden state of this property (`isVisibleOnScreen` vs `isHiddenForEveryone`)? From https://web.dev/content-visibility/#a-note-on-accessibility it seems that it would be visible to the accessibility tree but not...

Thanks for the issue. It looks like we'll need to figure out how to handle this type of code as we currently think the nested `li` is overlapping the parent...

Thanks for the issue. Confirmed that this is an issue with our stacking algorithm as `.wrapper` and `body` are missing from the final stack calculation. ```js axe.setup() axe.commons.dom.getElementStack(document.querySelector('span')) // [span,...

Some more info on this ticket. This isn't limited to `overflow`, this same issue can be caused by the following DOM: ```html Hello world ``` Because our code only really...

I believe this is similar to #2806

The problem is that there is no standard way to mark a visual element as purely decorative (that I know of). `aria-hidden` doesn't make it decorative, it just removes it...

Thanks for the issue. You are correct that we don't support `-webkit-text-stroke-` for checking color contrast. However we do take into account `text-shadow`, which you could use as a stroke...