RE: Buttons vs links
"Jan Hellbusch" <[email protected]> Thu, 7 May 2020 18:27:31 +0200
| Newsgroups | gmane.org.w3c.accessibility.general |
|---|---|
| Message-ID | <[email protected]> |
Hi, according to HTML spec, links are for resources and buttons are for = actions. There are exceptions: * in general, use links for going to a new page or downloading a = document. * links can also be used within a web page (skip navigation links etc.). * buttons are used for sending forms (most often to a script). * Otherwise they should be used for performing actions on the web page = (e.g. widgets). * Actions can, of course, mean calling a new resource in a process. It = will not always be clear, whether a button or a link is more appropriate.=20 Jan > -----Original Message----- > From: Savage, Angela (ITS) <[email protected]> > Sent: Thursday, May 7, 2020 6:02 PM > To: [email protected] > Subject: Buttons vs links >=20 > I was wondering what is the proper usage for a button and a link when building > an accessible application or website? >=20 >=20 >=20 > I=92m reading multiple articles on this topic and I read an article = from the Nielsen > Norman Group on command links and they state that buttons should not = be > used for navigation and that users should click a plain link to move = to another > page of information. Multiple articles I have read on using buttons = and links > when creating an accessible application or page mention this too. >=20 >=20 >=20 > Article: Command Links = <https://www.nngroup.com/articles/command-links/> >=20 >=20 >=20 > Thank you in advance, >=20 >=20 >=20 > Angela Savage >=20 > Accessibility Auditor