Primary static call-to-action link has no supported destination
ShipReady found an eligible primary call-to-action anchor with an empty, hash-only, or javascript:void href and no recognised handler attribute.
Why it matters
A primary call to action is worth reviewing when its static markup does not expose a destination or a recognised handler signal.
How ShipReady detects it
What it inspects
ShipReady inspects already-fetched static anchors in navigation, headers, and the first section of a page. It does not request the destination or execute the page.
What triggers a finding
The rule triggers only on a recognised call-to-action label with an empty, hash-only, or javascript:void href, no handler-shaped attribute, and no detected client-framework marker. Repeated labels are deduplicated.
What the evidence shows
The inspected static markup contains an eligible primary call-to-action link with a supported no-destination href and no recognised handler attribute.
Limits of this check
ShipReady does not execute JavaScript, click the element, test navigation, inspect all interactive elements, or prove that a user cannot complete the action. Client-rendered pages are deliberately suppressed.
How to fix it
Review the call-to-action implementation
Give the action an intended destination or ensure its supported client-side handler is present in the served markup. Preserve deliberate non-navigation controls outside the rule's scope.
How to verify the change
Test the actual user flow
After deployment, activate the affected call to action in supported browsers and confirm the intended flow occurs.
Expected: The primary action leads to its intended destination or interaction.