Open svanherk opened 2 years ago
Update - axe-core
v4.4.0
(releasing at the end of this month) will add back the violation for non-global ARIA attributes on elements with a role. Custom elements will report as Needs Review rather than a failure.
So this shouldn't fail our builds (unless we have violations on native elements), and we should get a log to help us track down places we need to fix.
Does this include role
?
I believe role
is fine and sometimes necessary, and we've definitely leveraged that in a few places. role
and any global aria properties won't fail the tests, but I still think we'd want to avoid the global aria-* properties if all we're doing is passing them down to the web component. Like if we want to put an optional aria-live
on an internal element, we should have the custom element's property just be live
(or whatever).
axe-core
version4.3.4
caused a number of our tests to start breaking because we placearia-expanded
on things liked2l-button
,d2l-subtle-button
, etc. We then pass down the value into thearia-expanded
attribute on the actual nativebutton
. Even though this works from a screenreader POV, we really should be using something like justexpanded
here. This may be an issue for otheraria-*
attributes as well.The change was reverted in
4.3.5
after discussion in this issue: https://github.com/dequelabs/axe-core/issues/3241 It's still unknown whether this will be added back in version4.4.0
, or if it will be added as a warning. But we should go through and fix these when we can to avoid lots of warnings (in bothcore
tests and everywhere that usesd2l-button
tests) or having to lock ouraxe-core
version everywhere.