An HTML <button> element can contain any phrasing content but Webflow seems to only allow text content. Sometimes an HTML <a> element is appropriate and a Webflow Link Block can be used but other times a <button> would be more semantically correct. I suggest adding support for a Button Block in Webflow.
Mark Fulton
.svg){kind=logo}
This is a CRITICAL update that should be implemented, especially with the growing need for websites to be built to be accessible.
As mentioned in previous comments, the current button block uses an <a> tag, which denotes it as a link, not a button. Button blocks should output the <button> tag instead.
Links are elements that take users to a new location on the website. Buttons, however, are elements that trigger an action on a page. Examples of actions that would be triggered by interaction with a button include opening and closing accordions, modals, or dropdown menus, changing the visible content in a slider or carousel, submitting a form, or playing an audio or video file.
Screen readers and assistive technologies rely on identifying these different tags to properly inform users of the intended functionality of the element in question.
Currently Webflow devs can get around this by adding a custom attribute to buttons (role="button") but this is semantically incorrect HTML.
It would be great to have a standard button component we can use. For functional pages which have buttons that "do a thing", it's important that it's a <button> not an <a>.