-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Button Block - Ability to make a button a semantic <button> element #57404
Comments
Hi, Thanks for reporting; |
I'm not so sure these two issues are exactly related. Nowhere in the description does it discuss the semantics or exact element usage. I'm surprised this is being looked at as such a trivial issue. The semantics are extremely misleading currently. |
At this moment I am trying to make a website with Gutenberg which should be accessible with a level AA or AAA if possible but this behavior that @robruiz reports is clearly not healthy for accessibility |
I am currently thinking of using this focus while Wordpress responds something for a solution, this leaves my solution alternative for another person index.js
this can be used with webpack or wp scripts in plugins basic for compiler and adding in your theme |
What problem does this address?
Currently, when a user adds a "button" to the buttons block, it's not a semantic button element. The only option is a div with an anchor tag inside. This is bad for semantic mark up and also effects SEO and accessibility to some degree.
What is your proposed solution?
Either make the default element a instead of a
The text was updated successfully, but these errors were encountered: