Replies: 1 comment
-
|
Also seeing this, opened #7190 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there any way to set
aria-disabled="true"for the b-button component while keeping it as an html<button>?I see that some other aria-* attributes are passed through as attributes to the generated
<button>tag, but notaria-disabled.The ability to set the property
disabledis not interchangeable witharia-disabled="true"asdisabledremoves the element from being perceivable. In some use cases, we should be able to inform assistive technology that a button is disabled while keeping it perceivable.I recognize that this requires the developer to ensure that the button is visually and functionally disabled so it requires more intention with its use.
From the documentation if you set the
disabledproperty andhref="#"property (changing it the button to<a role="button">) it will add thearia-disabled="true", but it also adds the attributetabindex="-1".I am curious if I am missing some way to set it directly.
If not and there isn't a good reason why it isn't being passed through, I would be interested in investigating it for a pull request.
Beta Was this translation helpful? Give feedback.
All reactions