In plain language
Each link's purpose must be clear from its text (or its immediate context).
Who it affects
People who browse by links list or voice commands and need unambiguous link purposes.
How to check
Pull up the links list in a screen reader: no bare 'click here/read more', no duplicates going different places, no unnamed icon links. Worked example — A community forum's discussion thread: inspect a clickable card component in DevTools: if the wrapping link/element has no accessible name and the visible title is a sibling not referenced by it, it fails.
Common misconception
“Click here” is the classic failure, but the more common modern version is an icon-only button with no accessible name at all. Both leave a screen-reader user with no idea where the link goes. Real example: on a government tax-filing portal, the text explaining where a link goes is somewhere unrelated on the page — a screen reader user reading just the link (and its immediate context) can't tell its purpose.