Why is click here a problem?

Screen-reader users often pull up a list of all links on a page to navigate. Out of context, a list full of click here and read more entries tells them nothing about where each link goes, which fails WCAG 2.4.6 (Link Purpose).

What link text gets flagged?

A configurable list of generic phrases — click here, here, read more, learn more, more, this, link, this link, continue, details — plus empty links, links whose text is just a raw URL, and an aria-label that does not add context.

Are aria-label and title considered?

Yes. If an anchor has an aria-label or a title that provides a meaningful accessible name, the visible generic text is acceptable, so the checker treats that link as resolved rather than flagging it.

What about duplicate link text?

Links that share identical text but point to different href values are flagged, because screen-reader users cannot distinguish them. Identical text to the same destination is fine and is not flagged.

Does my HTML leave the browser?

No. The HTML is parsed locally with the built-in DOM parser, and no data is sent anywhere.

Link Text Quality Checker

The Link Text Quality Checker finds links whose visible text fails to describe where they lead. Generic labels like click here and read more are everywhere, but they break a key accessibility expectation: a link should make sense when read on its own.

How it works

The tool parses your HTML and inspects every <a> element with an href. For each one it computes the accessible name, preferring an aria-label, then title, then the visible text. It then flags a link when:

The accessible name is empty (an image-only link with no alt text, for example).
The name matches a known generic phrase — click here, here, read more, learn more, more, this, link, this link, continue, details — and no aria-label/title adds context.
The visible text is just a raw URL like https://example.com/page, which screen readers read out character by character.

Finally it checks for duplicate link text pointing to different destinations, since those are indistinguishable in a links list.

This maps to WCAG 2.4.6 (Headings and Labels) and 2.4.4 (Link Purpose in Context).

Example

<a href="/pricing">click here</a>
<a href="/report.pdf">Download the 2026 annual report (PDF)</a>

The first link is flagged — click here says nothing about pricing. The second passes because its text fully describes the destination and format.

Tips

Front-load the meaningful words: Annual report (PDF) is better than Download the report by clicking this link.
If you must keep a short visible label for design reasons, add a descriptive aria-label — the checker will recognise it.
Avoid using the raw URL as link text; describe the page instead.