Creative Strategy
The Ad Copy Fits the Card. The Landing Page Breaks When a Reader Adds More Space.

Updated: November 22, 2026
WCAG does not require every landing page to ship with the test spacing values. It requires content and functionality to survive when a reader overrides line, paragraph, letter and word spacing to the specified levels. Apply a test stylesheet that sets line height to 1.5 times the font size, paragraph spacing to 2 times, letter spacing to 0.12 times and word spacing to 0.16 times.
Test adaptability, not a prescribed design style
WCAG does not require every landing page to ship with the test spacing values. It requires content and functionality to survive when a reader overrides line, paragraph, letter and word spacing to the specified levels.
Apply a test stylesheet that sets line height to 1.5 times the font size, paragraph spacing to 2 times, letter spacing to 0.12 times and word spacing to 0.16 times.
Start with the longest paid-media promise
Short placeholder copy can pass while the real campaign headline wraps into a badge, button or proof point. The highest-risk strings are usually the offer, disclaimer and localized variation.
Run the exact live headline, longest testimonial, price qualifier and CTA through the spacing test at desktop and mobile widths. Include translated variants when campaigns are multilingual.
Operating control table
| Control | Evidence | Failure prevented |
|---|---|---|
| Owner | Named reviewer and decision | Unclaimed change |
| Configuration | Saved source state | Cannot reproduce |
| Validation | End-to-end fixture | Partial success accepted |
| Threshold | Success and rollback rule | Result reinterpreted |
| Evidence | Public or reporting read-back | Configured mistaken for delivered |
Remove fixed heights from copy containers
A card with a fixed pixel height may clip the last line or overlap the CTA when text expands. The page can look polished at default settings while losing the claim or action under an override.
Let text containers grow with content, use padding instead of vertical centering assumptions and inspect every breakpoint for clipping, overlap and hidden overflow.
Do not hide truncation behind an ellipsis
An ellipsis can preserve the grid but still remove information. W3C guidance allows truncation only when a mechanism exposes the complete content, such as a focus, activation or linked-detail view.
Prefer natural wrapping for primary conversion copy. If truncation is unavoidable, provide a reliable, keyboard-operable way to reveal the full text and verify it remains available with spacing enabled.
Keep buttons and controls understandable
Increased letter and word spacing can push a compact button label onto two lines or outside its hit area. Icon-only fallbacks may remove the action name that persuaded the visitor to continue.
Allow button height to expand, keep the full accessible name and test the visible focus indicator. Avoid CSS that forces nowrap on long labels unless the container can safely grow.
Treat the result as creative-system feedback
If the page fails only with the current headline, the problem is not the user's spacing preference. It reveals a brittle component that will also struggle with localization, browser fonts and future offer changes.
Record the component, copy string and viewport that failed, repair the shared design system and retest the campaign. Preserve the test as part of creative release QA.
Connect the control to the wider system
Use this process alongside the image-text to real-text creative handoff. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.
Pre-launch checklist
- Write the decision and owner in plain language.
- Capture the source configuration and evidence.
- Test one realistic customer or reporting path end to end.
- Verify mobile presentation, links and accessibility.
- Record the success threshold and rollback trigger.
- Schedule the next review before material spend accumulates.
Run a cross-functional release review
Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.
Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.
Set the review cadence before launch
Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.
At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.
Frequently asked questions
Should this be automated?
Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.
What evidence should be preserved?
Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.
When should the team roll back?
Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.
