-
Notifications
You must be signed in to change notification settings - Fork 796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aria-allowed-role
rule false positive for <img>
with no alt but with accessible name
#3143
Comments
EDIT Sorry, looking at the wrong row (too early for me :) ). Will look further into this |
Related code block for |
Hi @WilcoFiers and @Zidious we are happy to see a fix is coming in. Once you all checkin and merge the code we can run a test on our side to make sure the issue is resolved. Thank you! |
Yeah, some work have been done, but still fix is absent in all axe tools other than dev, that's why this issue is still open. |
@kospl Sure , No problem , I have validated with dev branch code base. Will open it until fix is available in the production |
Nope, sorry. Our policy is to close the issue after QA has confirmed the issue is resolved in the develop branch. @kospl, this fix will be in the next released, which its currently looking will be the 4.4 release on January 31st. |
Product: axe-core
Expectation:
<img>
with rolebutton
and accessible name is a valid element.Actual: axe core 4.3.3 reports it as a violation of
aria-allowed-role
rule.Motivation: as described in https://www.w3.org/TR/html-aria/#el-img-no-alt
<img>
with no alt but WITH accessible name may have same roles as https://www.w3.org/TR/html-aria/#el-img includingbutton
.Repro minimal example:
Result (axe-core 4.3.3):
The text was updated successfully, but these errors were encountered: