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
As seen in dequelabs/axe-core#4259 there are a number of important accessibility APIs that axe-core does not currently, and may not for a while, cover, like roles applies via elementInternals. The means that it is easy on an element that is give a role in this manner to receive this output:
❌ `aria-prohibited-attr` failure for `minScore` assertion (Elements use prohibited ARIA attributes: https://dequeuniversity.com/rules/axe/4.9/aria-prohibited-attr )
Expected >= 0.9, but found 0
Other than moving aria-prohibited-attr at large to a "warn" is there more nuanced configuartion that can be applied to prevent this false negative? For instances, some integrations of axe-core allow for ignoredTags to be listed or ignoredRules. For my cases, I think I really need a ignoredRulesByTag sort of thing, which I'm not sure is actually possible at the axe-core level, but am seeing what's possible.
The text was updated successfully, but these errors were encountered:
The check uses the standards object, which can be overriden via axe.configure({standards}) to provide your own role.
On the Lighthouse side, we don't have any way to pass options to gatherers (mentioned in #10247), so the only way to utilize your own axe configuration today is to create a custom Lighthouse config with your own Accessibility gatherer. I don't know if we have an example of what that would look like - @adamraine do we?
Summary
As seen in dequelabs/axe-core#4259 there are a number of important accessibility APIs that
axe-core
does not currently, and may not for a while, cover, likerole
s applies viaelementInternals
. The means that it is easy on an element that is give arole
in this manner to receive this output:Other than moving
aria-prohibited-attr
at large to a"warn"
is there more nuanced configuartion that can be applied to prevent this false negative? For instances, some integrations ofaxe-core
allow forignoredTags
to be listed orignoredRules
. For my cases, I think I really need aignoredRulesByTag
sort of thing, which I'm not sure is actually possible at theaxe-core
level, but am seeing what's possible.The text was updated successfully, but these errors were encountered: