You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: src/_includes/content/links-vs-buttons.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@
4
4
- It is important to use Action Links for calls to actions that link to another page rather than buttons, because screen readers always say “link” before links, and “button” before buttons.
5
5
- A good rule is if the action changes the URL, it should not be a button.
6
6
- Button and link confusion can be very frustrating for assistive technology users. A user with a screen reader may pull up a list of links and may not find a specific link because it turns out that it’s been designated as a button in the markup.
7
-
- When a file download is involved, it is best to use a link. This is because links are intended for navigation, and downloading a file is a navigational action to a resource.
7
+
- When a file download is involved, it is best to use the [download link](https://design.va.gov/components/link/#download) component. This is because links are intended for navigation, and downloading a file is a navigational action to a resource.
0 commit comments