Usecase: Call to action, e.g. SITCON Exhibition
-> the functionality is that of a link, visually a button.
Question to UX @jannick-ux: should we just use the OnyxButton and internally allow that it could be an <a>nchor or should we create another mode for OnyxLink which looks button-esque but a bit different?
This matters because semantically (especially for screen readers), buttons and links fulfill different purposes
Links fulfill navigational purposes
Buttons are used to trigger actions within an application
Input from Mirco: Link button example from ODS
Usecase: Call to action, e.g. SITCON Exhibition
-> the functionality is that of a link, visually a button.
Question to UX @jannick-ux: should we just use the OnyxButton and internally allow that it could be an
<a>nchor or should we create another mode for OnyxLink which looks button-esque but a bit different?This matters because semantically (especially for screen readers), buttons and links fulfill different purposes