RE: Buttons vs links

Thank you for the responses. These have been helpful!

-----Original Message-----
From: Jan Hellbusch <[email protected]>=20
Sent: Thursday, May 7, 2020 12:28 PM
To: [email protected]
Subject: RE: Buttons vs links

ATTENTION: This email came from an external source. Do not open attachments=
 or click on links from unknown senders or unexpected emails.

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.

Jan

> -----Original Message-----
> From: Savage, Angela (ITS) <[email protected]>
> Sent: Thursday, May 7, 2020 6:02 PM
> To: [email protected]
> Subject: Buttons vs links
>
> I was wondering what is the proper usage for a button and a link when
building
> an accessible application or website?
>
>
>
> I'm reading multiple articles on this topic and I read an article from=20
> the
Nielsen
> Norman Group on command links and they state that buttons should not=20
> be used for navigation and that users should click a plain link to=20
> move to
another
> page of information. Multiple articles I have read  on using buttons=20
> and
links
> when creating an accessible application or page mention this too.
>
>
>
> Article: Command Links=20
> <https://www.nngroup.com/articles/command-links/>
>
>
>
> Thank you in advance,
>
>
>
> Angela Savage
>
> Accessibility Auditor