Steven Lambert

@Sunny-0929 were you able to update to the latest ruby gems? Is this still an issue?

I'll let @WilcoFiers know you ran into trouble and he'll reach out to you with more directions at a later time (he's currently unavailable)

Looking at the issue, it appears we don't treat elements inside the `` as hidden when the element is collapsed. As is, we think the `` element is currently visible...

Need to discuss with Wilco the ramifications of saying elements inside closed detail elements are hidden as we may not run axe-core rules against them.

We discussed this and the resolution is we'll update the is-hidden function to account for this. This means rules will not run against elements inside of a closed `` elements...

Use https://wai-wcag-act-rules.netlify.app/standards-guidelines/act/implementations/axe-core/ to determine which rules to bring over (based on which ones we are conformant with).

We can do this by filtering the `ownedRoles` array and seeing which ones are not required ```js const invalidRoles = ownedRoles.filter(role => !required.includes(role)); if (invalidRoles) { this.data({ }) return false;...

This is a breaking change. Even removing testing in IE11 has the potential to introduce breaking bugs into IE11, so we shouldn't do that either. However, what we should do...

Fix: add an option to the `has-descendant-evaluate` check function that will check for an open modal. If the check fails because there is 0 descendants and a modal is open...

This is planned to go into the 4.5 release near the end of Q3, at which point we will update all the axe integrations and release a companion 4.5 release...