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
Thanks for the issue. I believe this should have been fixed in version 4.10.1 which added support of <labels> giving buttons an accessible name. I tested the latest axe-core and it doesn't throw a button-name issue.
Product
axe-core
Product Version
No response
Latest Version
Issue Description
Expectation
axe-core button-name test should pass a <button> with linked <label for> based on HTML standard https://html.spec.whatwg.org/multipage/forms.html#category-label
Actual
button-name rule fails for <button> with accessible name defined by linked <label>
How to Reproduce
Button has a linked label, Chrome DevTools shows defined accessible name, axe-core button-name rule fails:
https://codepen.io/a11yally/pen/dPbWxrv
Additional context
N/A
The text was updated successfully, but these errors were encountered: