A useful link label helps a reader predict a destination or result. WCAG allows purpose to be determined from link text together with programmatically determined context in many cases. Illume Online’s stricter preference for useful link-only labels is a house practice, not a restatement of that requirement.

Finish with

Outcome

A link inventory containing the current label, relevant context, verified destination, proposed label, and any behavior the reader needs to know.

What you need

  • The rendered page and permission to follow every link being reviewed.
  • Destination titles or action results, including file types and new-window behavior.
  • A worksheet and a way to test links at narrow width and with keyboard focus.
  • Access to update both the source link and any repeated copies when needed.

The observable problem

Labels such as “Learn more,” “Read more,” and “Click here” transfer prediction work to surrounding prose. Repeated labels become especially difficult in a list. Raw URLs may expose irrelevant path text. A label can also sound clear while being wrong because the destination changed after publication.

State the evidence precisely: “Three cards use ‘Read more’; their destinations are the food program, room booking, and annual report.” Do not jump straight to “links are inaccessible.” Context, markup, destination behavior, and the reader’s task all affect the assessment.

Invented for instruction

Fictional worked example

Fictional worked example: Harbor Notes is an invented local archive. Its homepage has three “Read more” links. A raw URL opens a PDF, an envelope icon starts an email, and “Accessibility resources” leads only to a vendor product page.

The revisions are “Read the oral-history project,” “See archive opening hours,” and “Read the 2025 annual report.” The raw URL becomes “Download the room guide (PDF).” The email icon gains the visible label “Email the archive team.” A new tab is removed because the site has no established need for it.

The apparently clearer “Accessibility resources” label fails review because it overpromises. The destination is not a collection of resources. The accurate repair is “View the captioning product page,” or, if that destination does not serve the page task, remove the link and find an appropriate resource through normal editorial approval.

Procedure

  1. Inventory the rendered links

    Work from the actual page, not only the content system. Record each current label, the surrounding heading or sentence, and visible clues such as an icon. Include linked images, downloads, email actions, and repeated navigation links. Do not treat identical site navigation as separate editorial problems unless behavior differs.

  2. Open and verify each destination

    Record the destination title, the task it supports, its file type, whether it opens a new window, and whether access requires an account. Note redirects and labels that no longer match. Avoid renaming a link from assumptions about the URL alone.

  3. Draft labels from purpose

    When navigating, use the resource or destination name. When starting an action, name the expected result, such as “Email the bookings team.” Keep links with the same purpose consistent and links with different purposes distinguishable. Put repeated card links in their specific content context.

  4. Check promise, context, and behavior

    Read the proposed label by itself, then in its sentence or card. Confirm the destination fulfills the label. Name a download format when it affects the decision to activate. Avoid forcing a new tab; when one is genuinely required, explain the behavior before activation in a consistent way.

  5. Retest the page

    Navigate links with Tab, inspect them at narrow width, and confirm revised labels do not create awkward repeated speech. Search for the old vague label across the site. Save the inventory so destination changes can trigger a focused review later.

Reusable worksheet

Link inventory. Add one row for every unique editorial link purpose.
Current labelContextDestination titleReader taskProposed labelFile or window behavior
Read moreAnnual report cardAnnual report 2025Open the reportRead the 2025 annual reportPDF download
BlankHeading or sentenceVerify after openingState the intended resultUse destination or task languageRecord only real behavior

Decision rules

  • If the reader is navigating to a named resource, use the destination or resource name in the label.
  • If activating the link starts an action, name the result rather than instructing the reader to click.
  • If links have the same purpose, use consistent text; if they have different purposes, distinguish them.
  • If a new tab is not necessary for the task, use normal same-window navigation.
  • If a clearer-sounding label promises content the destination does not contain, narrow the label or change the destination.

Limitations and escalation

  • A link inventory cannot by itself establish accessibility conformance. Programmatic context, focus behavior, application state, and assistive-technology output may need technical testing.
  • Link-only clarity is often helpful but can become repetitive. Concise card links may reasonably rely on associated headings when the relationship is programmatically conveyed.
  • This method cannot decide whether a destination is editorially appropriate, safe, licensed, current, or authorized. Those questions require their own review.

Review list

Check the work

  • Every unique link purpose has a worksheet row and verified destination.
  • Repeated vague labels are replaced or supported by clear programmatic context.
  • The revised label does not overpromise the destination.
  • Downloads, email actions, account requirements, and unusual window behavior are disclosed when useful.
  • Keyboard focus and narrow-width presentation were checked after revision.

Review again when

  • A destination title or purpose changes
  • A file replaces a web page
  • A redirect is added
  • Cards or links are copied into a new context
  • Window or account behavior changes