-
Notifications
You must be signed in to change notification settings - Fork 747
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
Two additional elements that prohibit naming from authors #3410
Comments
Thanks for the issue. I can see a few issues with our code that allows those not to get flagged. The Do you know of a browser that would show the fallback parenthesis? MDN shows full support in all major browsers for the |
There's been a lot of discussion about the ruby elements in HTML lately, and there are some proposals for updated mappings for these elements (they're not close to landing right now), but that was the impetus for me to review these to make sure that authors didn't do things that could potentially muck things up in the future. But, per your point, seems that ARIA in HTML is actually incorrect in allowing anything on Edit: so webkit actually does render |
Gotcha. Testing it out it looks like we return Needs Review for the |
FYI: @straker I've removed |
From my checks, axe-core largely identifies ARIA 1.2's naming prohibited rule., and extends that rule to HTML elements with similar implicit roles. However, there are a few elements which were not flagged for having an
aria-label
oraria-labelledby
attribute per the test case I checked against.body
label
(removed)rp
The remaining 38 elements checked in the test case were all flagged by axe for not supporting
aria-label
oraria-labelledby
unless a role which allows naming is also specified.The text was updated successfully, but these errors were encountered: