Why This Update

On June 6, 2026, the Louisville location-page hero form shipped with Start My Free Review as the submit button and a No fee unless we win <small> sublabel beneath it. Root cause: prior §10 Forms QA only validated structure (endpoint, field names, honeypot, plugin signatures) — it did not check the visible text on the submit button or scan for sublabels below it.

This update aligns BOTH user-scope skills with two new runnable, FAIL-level assertions, plus matching Final Sweep checklist items and a v4.4 version-history entry on pre-publish-qa.

sa-copywrite-design §10 Forms — Updated Bullets

Bullet 1 (replaces the old `Form copy follows brand rules` line)

Form copy follows brand rules — FAIL-level (frozen). The submit button's VISIBLE TEXT must be exactly GET STARTED — uppercase, no variants. Banned button-text variants (FAIL on any match): Start My Free Review, Start Your Free Review, Get My Free Review, Free Case Review, Submit, Send, Send Message, Contact Us, Talk to Sam Aguiar, Call Sam Aguiar, Free Consultation, Call Now, any phone number, mixed-case Get Started. The check is a runnable visible-text assertion on the rendered button (see pre-publish-qa §10), not a structural/endpoint check — endpoint and field-name validation alone do NOT catch this bug. Root cause of the June 6, 2026 Louisville incident: the deployed HTML hardcoded Start My Free Review even though field names and endpoint were correct.

Bullet 2 (new — inserted directly after the bullet above)

No microcopy, <small> tag, sublabel, sublink, tagline, or reassurance line BELOW the submit button — FAIL-level. The submit button is the LAST visible element inside the form container. Banned button sublabels (FAIL on any match): No fee unless we win, No fee unless we win., No fees unless we win, Free consultation, 100% confidential, We respond within 24 hours, Your information is secure, any <small> / <sub> / <span class="*sublabel*"> / <p> element immediately following <button type="submit"> inside the same <form> or form card wrapper. The reassurance phrase No fee unless we win is permitted ONLY as standalone body copy in CTA banners or page prose — never as a button sublabel.

Bullet 3 (unchanged, kept for context — sits directly after the two above)

No subtext/subline under the form title. The form card carries its title (e.g., TELL US ABOUT YOUR CASE) and goes straight into the fields. No descriptive sentence, tagline, supporting paragraph, or reassurance line between the title and the first field.

sa-copywrite-design Final Sweep checklist — Forms section (updated)

A form is present as a default and is an approved custom form mapped to Litify + alert + email (this is a critical QA check as unfiring forms are killer), field-mapped to the homepage form, no third-party form plugin signatures, no orphan form fields
Submit button visible text is EXACTLY GET STARTED (all caps) — FAIL on Start My Free Review, Free Case Review, Submit, Send, Get Started mixed-case, or any other variant
No <small>, sublabel, microcopy, sublink, tagline, or reassurance line BELOW the submit button (e.g., No fee unless we win as a button sublabel = FAIL; allowed only as standalone body copy elsewhere)
No subtext/subline under the form title

pre-publish-qa §10 Forms — Updated Bullets

New runnable assertion 1 (replaces the old single-line `Submit button text is exactly GET STARTED` bullet)

Submit button visible text — runnable assertion (FAIL-level, frozen). For every <button type="submit"> inside any approved form container on the page, run the regex <button[^>]*type=["\']submit["\'][^>]*>(.*?)</button> (DOTALL flag, non-greedy). Strip inner HTML tags and  , trim whitespace, and compare to GET STARTED as an exact case-sensitive string. FAIL on any mismatch. Explicit banned values (auto-FAIL with name): Start My Free Review, Start Your Free Review, Get My Free Review, Free Case Review, Submit, Send, Send Message, Contact Us, Talk to Sam Aguiar, Call Sam Aguiar, Free Consultation, Call Now, mixed-case Get Started, or any phone-number pattern. Endpoint/field-name checks alone do NOT catch this bug (Louisville incident, June 6, 2026) — the visible-text assertion is mandatory.

New runnable assertion 2 (inserted directly after assertion 1)

No microcopy / sublabel after the submit button — runnable assertion (FAIL-level). After locating each <button type="submit"> inside the form container, scan the remaining sibling nodes inside the same <form> (or .sa-hero-split-card / form card wrapper) for any of: <small>, <sub>, <p>, <span>, or <div> containing visible text. FAIL on any visible text node following the submit button inside the form container. Specific banned strings (auto-FAIL with name regardless of element): No fee unless we win, No fee unless we win., No fees unless we win, Free consultation, 100% confidential, We respond within 24 hours, Your information is secure. Allowed: hidden inputs (<input type="hidden">), closing wrapper </div> tags, schema/script tags. The phrase No fee unless we win is allowed as standalone body copy in CTA banners or page prose — the check is scoped to the form container only.