Steven Lambert

Awesome. When https://github.com/w3c/html-aria/pull/489 is merged we can go ahead and add `separator` to the allowed list for button.

Thanks for the issue. I can see where the confusion is. The rule has a qualifier (that we seem to have not documented) that it only applies to roles that...

Thanks for the issue. We'll need to do some extensive research to see how much assistive technologies support different element internal properties. If they support it, adding support to axe-core...

@Westbrook The biggest support we could get from the community is to determine how well `ElementInternals` is supported in various assistive technologies and browsers. We've seen before that [some ATs...

Thanks for that information. Unfortunately what the browser reports / logs at the accessibility tree layer is only a partial understanding. In the end what matters is what screen readers...

Thanks for the issue. Could you provide some more details please, like what URL the error occurred on, the steps to reproduce the error, and which versions of axe-core or...

Thanks for the issue. I can't say for certain why it's being marked as incomplete. Would you be able to share the website this happened on? If not, maybe a...

Thanks for the website, I can see what's going on. The issue is in our code and is caused by the `body` having a `z-index: -1`. Mostly for my notes:...

Thanks for the issue. I've let the appropriate team know.

Thanks for the issue. The reason the example provided fails is that the accessible name of the button does not match the beginning of the `aria-label`. This follows [Technique G208](https://www.w3.org/WAI/WCAG22/Techniques/general/G208.html)...