In one paragraph
Links must have discernible text means a tested navigation control did not expose a usable accessible name. Add meaningful visible text or another appropriate naming mechanism, including a functional alternative for an image-only link. Verify the computed name and destination. A generic non-empty label may pass this rule without communicating useful purpose, while contextual WCAG evaluation requires more than an isolated string match.
Why it matters
A named link helps people decide where to go before activation. Screen-reader users can explore links in lists, and voice users can refer to names. An unlabeled chevron, social icon, or linked image can be difficult to distinguish even though it looks complete in a visual design.
Purpose and name presence are different questions. Click here supplies text and can pass a missing-name detector. WCAG link-purpose assessment considers the applicable accessible wording and programmatically determined context; it does not automatically fail every repeated visible label.
Use links for navigation and buttons for actions. An anchor with an onclick handler but no href does not provide the normal native link contract merely because it looks blue. It might be made focusable manually, but remains a different implementation needing appropriate semantics and keyboard behaviour.
How WebAuditOS evaluates this finding
The supplied axe link-name rule covers applicable anchor links, including href-based naming tests and relevant focusability cases. Text, supported ARIA names, and title-related paths can contribute to its result. An image alternative can contribute through the link's content when computed naming permits it.
Serious impact maps to high severity in the supplied integration. It does not prove the label accurately describes the destination or that every interaction is usable. Missing href cases and other custom controls require separate review; a passing link list is not full navigation conformance.
How to fix it
- Inspect the flagged link in the accessibility tree and read its computed name. Check child images, SVGs, hidden text, ARIA references, and whether the intended destination is actually expressed.
- Prefer concise visible destination wording where practical:
<a href="/pricing">Compare plans and pricing</a>Choose language that matches the real page. Do not add unrelated keyword lists in pursuit of SEO.
- For an icon-only link, add an accurate accessible name and hide decorative artwork from redundant announcement. For example:
<a href="/account" aria-label="Your account"><svg aria-hidden="true" focusable="false" viewBox="0 0 20 20"><circle cx="10" cy="6" r="3"/><path d="M3 18a7 7 0 0 1 14 0"/></svg></a>This illustrates naming and native navigation. It does not cover every visual state or account-access requirement.
- For an image-only link, provide an appropriate image alternative or another valid link name. Describe the relevant destination or function rather than a decorative visual shape. If adjacent visible text already names the link, avoid unnecessarily repeating that text through the image.
- Keep visible wording represented in the accessible name where required for voice use. aria-label can override useful descendant content, so inspect precedence instead of stacking labels indiscriminately.
- Confirm real href navigation for destinations and native buttons for actions. Test keyboard activation, focus visibility, open-in-new-tab behaviour, and expected history updates.
- Review repeated short labels in cards separately for purpose clarity. Correct source templates and translations so names remain accurate after content updates and on narrow layouts.
- Rescan and perform a manual navigation review. Look for misleading, excessively verbose, duplicate, or context-dependent names that a binary missing-name detector cannot judge.
What the fix can break
Naming changes can affect text-based analytics and test selectors. Update those dependencies without preserving confusing wording indefinitely.
An ARIA-only repair can make assistive output clear while leaving sighted users with an obscure icon. Consider tooltips or visible labels as complementary design where appropriate, not a replacement for robust naming.
Do not turn every clickable element into a link to satisfy this rule. Action semantics, keyboard handling, and actual destinations must remain correct.
Questions
Does click here pass this missing-name rule?
It can. That does not automatically make its purpose clear or establish every relevant WCAG requirement.
Why is a linked decorative image a problem?
If the image is the only content and neither it nor the link supplies a name, the navigation destination remains unnamed.
Can I fix an action by giving its anchor a fake href?
Do not use a misleading destination. Use an appropriate button for an action and implement the intended behaviour.
Which related checks help?
Review button names, image alternatives, and the automation limits guide.
What severity does this get in the report?
High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. This rule is declared serious in axe-core, so a failure arrives as high. That is why the panel above states a conformance level rather than a severity - for other axe rules the value depends on what failed.