Work 4 min read

Why "Learn more" links are hurting your website

Generic "learn more" links confuse screen reader users and tell Google nothing. How to write descriptive links, with examples and code.

  • #accessibility
  • #seo
  • #drupal
  • #wcag

“Learn more”, “Read more”, “Click here”. They’re on almost every website. The problem isn’t the phrase: it’s that the link, on its own, doesn’t say where it goes.

Why they hurt #

  • Screen readers. Many people move through a page by pulling up a list of its links. Out of their paragraph, that list reads “Learn more, Learn more, Learn more”. WCAG 2.4.4 (Level A) accepts context from the same sentence or paragraph, but that list loses it; that’s why WCAG 2.4.9 (Level AAA) asks for links that make sense on their own.
  • Google. Search engines use a link’s text to understand the page it points to. “Learn more” tells them nothing.
  • Everyone else. People scan for links. Ten identical labels make them read every paragraph to know where each one leads.

The mistake is in what’s inside the <a> #

“Learn more about the spring apple festival” is fine, as long as the whole phrase is the link. The mistake is when only “Learn more” is linked and the context is left outside:

<!-- ❌ Avoid: the link only says "Learn more" -->
<a href="/festival">Learn more</a> about the spring apple festival.

<!-- ✅ Right: the whole phrase is the link -->
<a href="/festival">Learn more about the spring apple festival</a>

<!-- ✅ Right: the link is on the name -->
See the <a href="/festival">spring apple festival</a> schedule.

A few rewrites:

Before (no context)After (with context)
Click hereDownload the registration guide (PDF)
More informationSee the requirements for vendors
Learn moreLearn more about the spring apple festival
Watch videoWatch the plant tour video
Visit our websiteVisit the state fair website

When the design needs a plain “Learn more” #

Sometimes the button has to say “Learn more”, for example on a row of cards. That’s not wrong; it just lacks context, and you can add it without changing what people see.

Option 1: visually hidden text. It’s read aloud but not shown:

<a href="/festival">
  Learn more
  <span class="visually-hidden">about the spring apple festival</span>
</a>

visually-hidden is Drupal’s class; in Tailwind it’s sr-only.

Option 2: aria-label. It replaces the link’s name, so it has to include the visible text, ideally at the start:

<!-- ✅ Right: starts with what's on screen -->
<a
  href="/festival"
  aria-label="Learn more about the spring apple festival"
>
  Learn more
</a>

<!-- ❌ Wrong: doesn't contain "Learn more" -->
<a
  href="/festival"
  aria-label="Spring apple festival 2026"
>
  Learn more
</a>

The second one fails WCAG 2.5.3, Label in Name: someone using voice control says “click Learn more” and it may not work, because the link’s real name is “Spring apple festival 2026”.

One catch: some audit rules (DubBot’s, for example) only read the visible text and keep flagging these links, even though screen readers are already fine. If you need the report at zero, the only way out is changing the visible text.

How I fixed it on a real site #

On a large Drupal site, with nearly 1,800 published pages, I found 7 “Learn more” links. That’s not many, and it speaks well of the site, but the goal is zero.

These were the text changes, for example:

BeforeAfter
Learn MoreLearn more about the spring apple festival
Learn MoreView the 2026 grant recipients
Learn MoreHow to safely thaw a turkey

To apply them, Drupal gives you two paths, depending on where the link comes from.

If it comes from a template, fix it in Twig, and one change fixes every page that uses it:

<a href="{{ url }}">
  {{ 'Learn more'|t }}
  <span class="visually-hidden">
    {{ 'about @label'|t({'@label': label}) }}
  </span>
</a>

If it’s in the content, the temptation is to log into production and edit it by hand. It’s better to write an update hook that changes the text in the database:

// mymodule.post_update.php
function mymodule_post_update_descriptive_link_text() {
  // nid => [old, new]. Include the href so only that link matches.
  $changes = [
    123 => [
      '"/festival">Learn More</a>',
      '"/festival">Learn more about the spring apple festival</a>',
    ],
  ];
  $nodes = \Drupal::entityTypeManager()
    ->getStorage('node')
    ->loadMultiple(array_keys($changes));
  foreach ($nodes as $nid => $node) {
    [$old, $new] = $changes[$nid];
    $node->body->value = str_replace($old, $new, $node->body->value);
    $node->setNewRevision();
    $node->setRevisionLogMessage('Descriptive link text.');
    $node->save();
  }
}

That way the change lives in code: it gets reviewed in the pull request, tested with drush updatedb on Tugboat or locally with a copy of the database, and reaches production exactly the same, with a new revision on every page. On another site I used this same approach to fix 185 links on 57 pages without editing production by hand.