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
Reading the documentation on buttons and it says it generates the following html (also verified this is true)
<arole="button" href="/docs/">Learn more</a>
This is not how the button role should be used. The general rule of thumb is that links navigate, buttons perform an action. This example navigates so it should be a link. This cause 2 problems:
It misleads the user on what will happen if when they click it.
It doesn't behavior properly without additional work. For example users expect buttons to active when you press space which this does not.
I think simply removing the role would be sufficient? Though you may want to rethink having buttons take an href option at all depending on what you want them to mean.
Describe the Bug
Reading the documentation on buttons and it says it generates the following html (also verified this is true)
This is not how the button role should be used. The general rule of thumb is that links navigate, buttons perform an action. This example navigates so it should be a link. This cause 2 problems:
I think simply removing the role would be sufficient? Though you may want to rethink having buttons take an href option at all depending on what you want them to mean.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role
https://www.washington.edu/accesstech/checklist/links-buttons/
The text was updated successfully, but these errors were encountered: