You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aria-required-children checks only if at least one child has the appropriate role rather than making sure all the children of a particular role have the appropriate roles
For example if an element with role list has one child with role listitem and other children with inappropriate roles, aria-required-children does not fail on these children
Expectation: Fail all child elements with inappropriate roles. Case1 and Case3 in the example should fail
Actual: The rule checks only if at least on child has the appropriate role
@iamrafan Hey Guru. ARIA doesn't require this. The description of required owned elements is somewhat problematic. I have been trying to get the ARIA working group to update their spec to clarify on this issue w3c/aria#1033. As of today, The requirement is that at least one descendant (jup, doesn't even have to be a child) has the required role. It's pretty busted, and I hope they can get around to fixing this, but I don't want to change how axe-core works without seeing how the ARIA working group thinks it should be.
aria-required-children
checks only if at least one child has the appropriate role rather than making sure all the children of a particular role have the appropriate rolesFor example if an element with role
list
has one child with rolelistitem
and other children with inappropriate roles,aria-required-children
does not fail on these childrenExpectation: Fail all child elements with inappropriate roles. Case1 and Case3 in the example should fail
Actual: The rule checks only if at least on child has the appropriate role
Demo link: https://codepen.io/iamrafan/pen/qBNawdg
The text was updated successfully, but these errors were encountered: