Skip to main content
It looks like you're using Internet Explorer 11 or older. This website works best with modern browsers such as the latest versions of Chrome, Firefox, Safari, and Edge. If you continue with this browser, you may see unexpected results.
"Click Here" is NOT the name of a link!
We've gotten so used to seeing "Click Here" that it can be difficult to think of how to rephrase our own links, but you can do it! AND, you should get in the habit of giving every link a title within the code. Why is it important?
- Screenreaders will read the given link title instead of reading the entire url; considering how long some urls can get, this is much more user friendly.
- Links that are named appropriately give both sighted and visually impaired users a "heads up" about where they will end up once clicking on the link.
- If (heaven forbid) your link is broken, users will have enough information to find the intended resource.
- Appropriately naming the link should also include what type of format the user can expect to find once it's clicked. It's frustrating to click a link thinking you can quickly scout out a website, only to have to wait for a huge .pdf to download...
See below for an example of what inserting the title will look like in a visual editor.
Examples of Naming Links Within the Text
For more information about Indianapolis, click here!
For more information about Indianapolis, visit the City of Indianapolis government website.
Click here to find more databases.
For more article resources, visit our Databases A-Z guide.
AGH! A Broken Link!!
As frustrating as it is for anyone to click on a broken link, it can be even worse for students with disabilities. Below are some suggestions to help you avoid having too many of these roadblocks in your online guides.
- Limit the number of links that you include: students are not likely to click on more than the top three, so try to refrain from including every resource a student "could" find helpful & only include the ones they "will" use.
- Re-Use existing links locating within your LibGuides. For example, have a LibGuide of frequently used databases and another one for website links. This way, a broken link fixed in the primary guide will automatically fix every other spot the link has been re-used.
- Check for broken links regularly. LibGuides "Link Checker" will spot publicly accessible links that are completely broken, but you'll still want to manually check that links behind proxies work and that public links are still going to the right spot.
- Link colors should be varied enough from the text that they stand out so that color-blind visitors recognize the link. To check, try printing out your page in black & white...do the links stand out?
- Underline links at least when they are hovered over.
- Avoid underlining any text that is NOT a link & do not use change regular text into the same font color as your hyperlinks. Visitors will likely try clicking on regular text & will think that something is broken.
- Stay consistent with the link styles & colors being used across the site; even if you hate them, users will know what to expect.