Steven Lambert

Thanks for the issue. Axe-core uses [colorjs.io](https://github.com/color-js/color.js) to parse color spaces. It looks like there are a few open issues about supporting `none`, such as https://github.com/color-js/color.js/issues/368, but nothing specific about...

That is indeed interesting. Our code mostly uses colorjs to parse the CSS string for the color bits but does have an exception only for HSL as colorjs doesn't support...

@dbjorge pointed out an issue with the `utils.publishMetadata` function that I need to address, but this is mostly in a reviewable state

Thanks for the issue. The code in your screenshot is our generate selector code, which is _the_ slowest part of our entire codebase as it has to generate a unique...

Thanks for the issue. I looked into it and think I've identified what's going on. The problem is that our code looks at the element stack for each individual text...

I'm going to move this bug to axe-core since that is where the problem is occurring.

I apologize for the delayed response, we've been super busy prepping for the 4.7 release. I plan on taking a deeper look at this next week.

Alright, here's some notes on what I found: * VO / Safari - doesn't see the svg using next/prev line. Reads the aria-label when putting tabindex on the svg (role...

Thanks for the issue. We'll look into ways we could address this.

Thanks for the issue. [ARIA in HTML](https://www.w3.org/TR/html-aria/) is the spec we follow when determining what roles and attributes are allowed on elements. According to the spec, the [role="separator" is not...