# Coverage CTA and form mismatch — dev spec
Site: nomadinternet.com · Priority 7 · High · Effort: Low (0.5-2 days)

## Problem
Coverage CTAs lead to a form labeled UNLOCK MY SAVINGS, creating a mismatch between intent and interaction.

## Evidence (from the live site)
> 4 distinct calls to action compete on the same page: “CHECK COVERAGE”, “CHECK IF IT WORKS AT MY ADDRESS”, “START CHAT”, “CHECK MY COVERAGE”.
> A form on this page: its submit button is labelled “UNLOCK” and it carries 3 fields.

## Current state
h1: Finally. Real Internet in Rural America; cta: CHECK COVERAGE | CHECK IF IT WORKS AT MY ADDRESS | START CHAT | CHECK MY COVERAGE; notes: Form label does not match CTA intent.

## Required change
cta: CHECK COVERAGE; notes: Change form submit to CHECK COVERAGE and make ZIP the only required field.

## Acceptance criteria
- GIVEN a first-time visitor on the affected page
- WHEN the change is live
- THEN Change form submit to CHECK COVERAGE and make ZIP the only required field.
- AND no layout regression at 375px / 768px / 1280px
- AND the changed control is keyboard-reachable with an accessible name

## Tracking
- Fire `cro_coverage_cta_and_form_mismatch` on interaction with the changed element
- Verify the event fires in BOTH variants before opening traffic

## Test plan
- Two-proportion z-test, 95% significance, 80% power
- 315,206 visitors per variant to detect a 5.0% relative lift
- Run at least one full business cycle; not testable at current traffic

## Rollback
Feature-flag the change; revert if the primary metric drops for 3 consecutive days.