- From: Cristiano Rastelli <cristiano.rastelli@hashicorp.com>
- Date: Fri, 20 May 2022 11:29:33 +0100
- To: public-aria-practices@w3.org
- Message-ID: <CAFxSxGOOb-N1TvT-x-Ep=yLi-h67sp6HinQipp_qqrwikC-RxQ@mail.gmail.com>
Hi There's been an ongoing discussion across the community, about the issue of *buttons vs links* (see here <https://marcysutton.com/links-vs-buttons-in-modern-web-applications>, here <https://medium.com/@h_locke/links-vs-buttons-e8b523660fb3>, here <https://css-tricks.com/use-button-element/> just to mention a few examples). Now, the Button page <https://www.w3.org/WAI/ARIA/apg/patterns/button/> of the APG patterns has a brief mention of the tension between the two, from the point of view of their appearance: > *The types of actions performed by buttons are distinctly different from > the function of a link (see link pattern). It is important that both the > appearance and role of a widget match the function it provides. > Nevertheless, elements occasionally have the visual style of a link but > perform the action of a button* but does not give any indication about what is the "correct" way to handle this difference *from the visual perspective*. The homepage <https://www.w3.org/WAI/ARIA/apg/> (and the entire APG website) is full of *links* (<a> anchors) *that look like buttons*, mixed with *buttons* (<button>) *that look like buttons*. I know this is a loaded topic, but I think it would be better to have clarity on this, and give guidance or what is the recommended approach, especially since you are using a pattern that, from my understanding of your best practices, is considered not correct. Thank you for your time Cristiano Rastelli
Received on Monday, 23 May 2022 06:56:34 UTC