What a link should communicate

A link’s purpose is the result a person can expect when activating it: reaching a page, opening a document, or starting a download. Understandable wording helps people decide whether to follow it, especially when navigating a page with a keyboard or using a screen reader’s list of links. Link text should provide direction, not merely announce that something can be clicked.

That does not mean every link needs a long description. A short phrase may be enough if it identifies the destination or action and nearby context supplies anything missing. For example, in a section about the school calendar, “2026–2027 school calendar” already tells people what resource will open; “More information” does not do so by itself.

A practical approach is to write for two situations: reading the paragraph normally and moving quickly among links. The name should remain recognizable when heard on its own, but it need not repeat the whole paragraph. Link the most informative phrase rather than adding “click here” as a preface.

WCAG 2.4.4 and 2.4.9 do not ask for exactly the same thing

WCAG 2.4.4, Level A, allows the purpose of a link to be determined from its text alone or from that text together with context that is programmatically associated with it. The W3C’s explanation gives examples such as the same paragraph, list item, or table cell; it also covers programmatic relationships, including those identified with ARIA. Context matters, provided people can access it without losing the link’s location.

WCAG 2.4.9, Level AAA, sets a stricter requirement: the purpose must be identifiable from the link text, except when that purpose would be ambiguous to everyone. “View schedules” might therefore be sufficient on one page, while “School bus schedules” makes the destination easier to recognize with less reliance on the surrounding material. These criteria are not interchangeable: meeting 2.4.4 does not mean meeting 2.4.9.

Do not turn an editorial preference into a universal requirement. Under 2.4.4, “More information” does not automatically fail in every situation: programmatically determinable context may clarify it. Still, improving the wording often makes navigation easier and reduces reliance on that context. Meeting a particular criterion and writing links that work comfortably for more people are related goals, but they are not identical.

Review the link with and without its immediate context

To check criterion 2.4.4, first identify the linked phrase and ask what it communicates on its own. If it is brief or generic, check whether a person can obtain the missing information from text directly associated with it, without scrolling away or searching for explanations scattered elsewhere on the page. Visual proximity alone is not enough if the relationship is not available programmatically.

Consider this illustrative example: “Read the course assessment policy” is clear when the link is considered on its own. In “Read the policy,” the paragraph “To learn about grading methods, read the policy” may provide enough context if that relationship is structured correctly. By contrast, text in another column, a disconnected caption, or a sentence that appears later without an association may not provide the same context to people navigating by links.

Read through the links a second time as if you could hear only their names. Would “Open,” “Here,” or several instances of “More information” help you choose the right destination? If not, rewrite the label or provide associated context. To aim for 2.4.9, also perform the stricter text-only check; do not rely on the surrounding paragraph to complete an insufficient link name.

Match the wording to the destination and action

A useful label can describe the content, the task, or both. “Enrollment guide” identifies a resource; “Download the enrollment guide” also says that activating the link starts a download. Choose a verb that matches what actually happens: do not promise a download if the link opens an information page, or call something a form if the document only explains a process. The promise and the result should match.

When linking to a file, identify its format if that helps people anticipate the experience, particularly if the document opens in another application or requires specific software. For example: “Download the enrollment form (PDF).” Including the format in the linked text is useful because that information remains available when someone moves through a list of links. This does not mean every file link needs a long label: the information should be relevant to the destination and its use.

In documents meant to be printed or presented without access to interactive links, it may be useful to include a readable address alongside the resource name. On a web page, however, using a long URL as the label often makes listening and reading harder. Adapt the label to the medium: retain information that is genuinely needed on paper, and avoid carrying technical strings into links intended for on-screen navigation.

Ajusta el texto al destino y a la acción Una etiqueta útil puede describir el contenido, la tarea o ambos. «Guía de inscripción» identifica un recurso; «Descargar la guía de inscri...
Editorial illustration by BytePreview

Avoid repeated names that conceal different destinations

Two links with the same name may be appropriate when they lead to the same destination and serve the same purpose. If one opens a calendar and another an enrollment guide, calling both “More information” makes people depend on context to tell them apart and makes a list of links less useful. Distinguish different destinations with names that identify the relevant resource or action.

A link does not always need the full title of a page when context resolves the difference and the applicable criterion allows it. In a list of books, for example, links labelled “PDF” may be understandable if each is clearly associated with the corresponding book title. If that association is lost while navigating the list, a label such as “Journey to the Center of the Earth, PDF” is more unambiguous, although also more repetitive.

Links placed one after another deserve a separate check. Several short names packed together may be difficult to distinguish when heard aloud. Separating them into list items or using a clear structure can help people recognize where one ends and the next begins. On a page with extensive navigation, descriptive headings and, where appropriate, an option to skip that block can make it easier to reach the main content.

A short routine for reviewing pages and documents

The same editorial review can be applied to web pages, spreadsheets, presentations, and documents: find each link, check its actual destination, and assess what its name promises. In Office files, pasting a URL can automatically create a link that uses the address as its text; replacing it with a clear phrase is usually more useful to people navigating or listening. Appearance alone is not enough: the accessible name and the destination must also correspond.

Use this sequence for a quick check:

  1. Gather the links on the page or in the document and check that none are empty or lead to an unexpected destination.
  2. Read each label on its own and confirm that it identifies the destination or action sufficiently.
  3. When a link depends on context, check that the relationship is programmatically associated and understandable without losing focus.
  4. Review repeated links, downloadable files, formats, and actions that open or submit content.
  5. Navigate through the links with a keyboard and, if possible, with a screen reader’s link list; confirm that the order and names help people choose.

Automated tools can flag some problems, but they cannot decide on their own whether a label promises the right thing or whether nearby wording genuinely clarifies the destination. Human review should consider both content and structure, while checks with assistive technology provide information about how navigation is presented. A favorable automated result does not by itself show that an entire page or document conforms to WCAG.

Review links for clarity and purpose

A concise sequence for checking link names, context, destinations, and navigation in web pages and documents.

  1. Destination

    Confirm it is expected

  2. Link name

    Make its purpose clear

  3. Context

    Keep it associated

  4. Files and repetition

    Distinguish destinations

  5. Navigation

    Check names and order

Web pages and digital documents

This checklist covers link purpose and does not establish accessibility conformance for an entire page or document.

Sources and references3

What this check covers and what it does not

The review described here concerns the purpose and clarity of links. It is not a complete accessibility evaluation and does not by itself establish conformance with a particular WCAG version, level, or legal standard. Other aspects also need checking, including keyboard navigation, visual presentation, and how the destination actually works. A clear link does not make its destination accessible on its own.

The W3C Understanding document explains the criterion and gives examples of associated context; it does not replace reading the normative text or evaluating the full content. WebAIM offers practical recommendations on links, lists, and non-HTML files, but its editorial advice should not be presented as a universal WCAG requirement. Section508.gov provides training materials for spreadsheets and presentations; its steps relate to those formats and their tools.

To finish a review, record the link, destination, visible text, context being used, and criterion checked. If your team works with WCAG, note the version and level relevant to the project and review the applicable normative document. A template improves traceability, but it is neither certification nor legal advice.