# 2.4 Hyperlinks

## Screen Reader Interaction

{% hint style="info" %}
Another method for skimming a webpage with a screen reader is to listen to all of the hyperlinks on the page.
{% endhint %}

## Solutions

### Better Links

* Link wording should clearly explain its destination and/or intent. Ambiguous phrasing can obscure a link's purpose.
* Read your links out of context to insure they will stand alone as a screen reader presents them in order.
* Avoid introductory phrases such as "click here" for a link.&#x20;
* Definitely do not use "click here" as a link on its own.
* Do not use raw web addresses in links as the screen reader will read it aloud the entire URL.

### Better Link Examples

* ***Poorly written link***: [Click here](https://miamioh.edu/about-miami/visiting-miami/directions/index.html) for directions.
* ***Better***: [Directions to Miami University](https://miamioh.edu/about-miami/visiting-miami/directions/index.html) are available online.
* ***Poorly written***: Learn more about accessibility [here](http://webaim.org/standards/wcag/).
* ***Better***: Learn more about [accessibility standards from WebAIM](https://www.w3.org/WAI/intro/wcag).

## Video tutorial

{% embed url="<https://www.youtube.com/watch?v=Smy4OAmMEwE>" %}
All about links: how they are used in navigation, labelling concerns, and distinguishing them from surrounding text. From the ADA National Network.
{% endembed %}

## Testing

When reviewing WAVE's "Details" tab, look for alerts of "Suspicious Link Text" then click on the link alert icons to find the questionable links on your page. On this page WAVE identified the poorly written link examples above. The tool also identified redundant links from the examples above as well!

## Read More...

* [Tips for Getting Started Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.liba11y.org/howto/better-links.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
