Anchor without an href
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
An <a> without an href is not focusable or activatable by keyboard and is not announced as a link. If it behaves like a button, use a real <button>; if it is a link, give it an href. Heuristic: a router Link component is fine and is not matched.
Why it matters
An anchor with no href is not a link: it is not focusable by keyboard, cannot be activated with Enter, and is not announced as a link by screen readers. If it carries an onClick it becomes another mouse-only control. This is a heuristic; a router Link component that produces its own href is fine and is not matched here.
How to fix it
If the element navigates, give it an href (or use your router Link with a to prop). If it performs an action rather than navigating, use a real <button> instead of an anchor. Do not use an empty or placeholder href to satisfy the rule.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo