# Click-Consent Just Got Its Sixth Circuit Imprimatur – Here's the Lead-Gen Form Audit That Actually Matters Now > **Canonical:** https://www.leadgen-economy.com/blog/dahdah-rocket-mortgage-click-consent-form-audit/ > **Published:** 2026-05-21 > **Author:** Alex Paddington > **Source:** LeadGen Economy - https://www.leadgen-economy.com --- *The Sixth Circuit's January 26, 2026 opinion in* Dahdah v. Rocket Mortgage *moved the load-bearing element of every TCPA defense from the consent record to the web form itself. The court's four-factor conspicuousness test – notice placement, button proximity, visual conspicuousness, dynamic scrolling – is now the doctrine that determines whether a putative class action lands in arbitration or in certification. With the FCC's one-to-one consent rule vacated and a 'Delete, Delete, Delete' NPRM signaling formal elimination, every active lead-generation funnel is operating on click-wrap architecture that will be litigated, screenshot by screenshot, in the next eighteen months.* --- ## A Form Architecture Opinion in TCPA Clothing On January 26, 2026, a Sixth Circuit panel reversed the Eastern District of Michigan's denial of Rocket Mortgage's motion to compel arbitration in *Dahdah v. Rocket Mortgage, LLC*, No. 24-1910 (6th Cir.). The case began as a consumer's TCPA class-action complaint about marketing calls allegedly placed without prior express written consent. It ended as something more consequential: a published appellate opinion holding that the click-wrap signup on a LowerMyBills.com mortgage-shopping form formed a binding contract under California law (per the LowerMyBills.com choice-of-law clause), that the contract carried both an arbitration clause and a TCPA consent provision, and that the proper forum for the dispute was therefore individual arbitration rather than a federal court class proceeding. For the bar, the holding was a clean win on the arbitration question. For lead-generation operators, the opinion is something different. The Sixth Circuit did not simply rule that this particular click-wrap was enforceable. It articulated a four-factor framework – notice placement, button proximity, visual conspicuousness of the disclosure text, and dynamic scrolling behavior – that lower courts are already applying to other lead-generation funnels. The factors are not new to contract law; they trace back through *Specht v. Netscape*, *Berkson v. Gogo*, *Sgouros v. TransUnion*, *Meyer v. Uber*, and *Sellers v. JustAnswer*. What is new is that the Sixth Circuit applied them in a TCPA case to a lead-generation publisher's funnel and produced a published, citable opinion that buyers and publishers will spend the next eighteen months litigating, screenshot by screenshot. The April 22, 2026 trade-press analysis published by Global Arbitration News treated *Dahdah* as the most important click-wrap case of the cycle. The Bubeck Law privacy practice published a parallel walk-through framing the opinion as a design specification for "enforceable opt-ins." Kelley Drye's TCPA Tracker for March-April 2026 placed *Dahdah* at the top of its consent-defense section, alongside the companion *Tablada v. Rocket Mortgage* filing in the District of Rhode Island (No. 1:2026cv00118). The trade-press alignment is unusual; what it tells operators is that the bar reads *Dahdah* as the doctrine that will govern the next wave of TCPA defenses, and the form architecture that the Sixth Circuit blessed is the architecture every defendant will now try to mirror. This analysis covers what *Dahdah* held, where the four-factor test traces from in click-wrap doctrine, why the timing aligns with the FCC's vacated one-to-one consent rule and the "Delete, Delete, Delete" NPRM, what the form audit looks like in operational terms, and why the difference between an arbitration-bound dispute and a class-cert-bound dispute is now measured in pixels and CSS specificity. The headline: a TCPA defense in 2026 is not a consent record. It is a screenshot of a landing page and the underlying HTML, and the load-bearing question is whether the disclosure was reasonably conspicuous to a reasonable user at the moment the button was clicked.
Four-factor click-wrap conspicuousness test from Dahdah v. Rocket: notice placement, button proximity, visual conspicuousness, dynamic scrolling.
The yellow disclosure bar is the load-bearing element courts now test — fail any of the four factors and there is no binding contract, no arbitration shield.
--- ## What the Sixth Circuit Actually Held in Dahdah The factual background matters because the court's analysis is granular about the mechanics of the funnel. The plaintiff, Hassan Dahdah, used the LowerMyBills.com mortgage-shopping funnel in 2023. LowerMyBills, a long-standing lead-generation publisher, operates a multi-step form that captures borrower information – loan purpose, property type, credit-score band, contact details – and routes the resulting lead to mortgage lenders within its buyer network. At the end of the form sequence, the user clicked a button. Adjacent to the button was a disclosure stating that by clicking, the user agreed to the site's terms of use and privacy policy and consented to be contacted by the buyer network at the phone number provided, including by autodialer and prerecorded message. The terms of use, accessed through a hyperlink in the disclosure, contained both a binding arbitration clause and a class-action waiver. The lead routed to Rocket Mortgage. Rocket called the number Dahdah had supplied. Dahdah filed a putative class action under the TCPA, alleging that the calls were placed without prior express written consent. Rocket moved to compel arbitration, citing the LowerMyBills.com terms of use linked from the click-wrap disclosure. The Eastern District of Michigan denied the motion, reasoning that the disclosure was insufficiently conspicuous to bind Dahdah to terms he had not actually read. The Sixth Circuit reversed. Writing for the panel, the court applied California contract law (the governing law specified in the LowerMyBills.com terms-of-use choice-of-law clause) to the question of whether a binding agreement had formed. The framework the court used is the same multi-factor conspicuousness analysis that federal appellate courts have applied to online contracting since *Specht v. Netscape* in 2002. Under that framework, the question is whether a reasonable user, encountering the disclosure in its actual visual context at the moment of clicking, would have been on inquiry notice of the terms being agreed to. The four factors the *Dahdah* panel identified – and that subsequent district courts in the Sixth Circuit have already begun citing as a checklist – are: **Notice placement.** Where on the page did the disclosure text appear relative to the action button? A disclosure positioned immediately above or below the button receives more weight than one buried in a footer or set apart by white space and unrelated content. **Button proximity.** What was the pixel-level distance between the disclosure text and the button itself? The court emphasized that proximity is not a metaphor; it is a measurable spatial relationship that affects whether a reasonable user reading the button label would also have seen the disclosure. **Visual conspicuousness of the disclosure.** Was the disclosure rendered in a font size and color contrast that made it readable in the visual hierarchy of the page? Disclosures rendered in eight-point gray text on a white background fared worse than disclosures rendered in twelve-point black text with normal weight. **Dynamic scrolling behavior.** Did the disclosure remain visible as the user interacted with the form, or did the page's scroll behavior push the disclosure off-screen before the click occurred? This factor is particularly relevant on mobile devices, where viewport limitations and dynamic form expansion can move the disclosure outside the user's field of view. Applying these factors to the LowerMyBills.com funnel, the Sixth Circuit found that the disclosure was reasonably conspicuous. The notice appeared immediately above the action button. The button was within a small pixel distance of the disclosure text. The disclosure was rendered in a font size and color contrast that the panel found legible. The page's scroll behavior preserved the disclosure's visibility. On those findings, the court held, a reasonable user clicking the button would have been on inquiry notice of the linked terms – including the arbitration clause and the TCPA consent provision – and the click therefore formed a binding contract. The Sixth Circuit's order to the district court was to grant Rocket Mortgage's motion to compel arbitration, terminating the federal class action and routing the dispute to individual AAA arbitration under the LowerMyBills.com terms. ### Why the form mattered more than the disclosure language A point worth dwelling on: the Sixth Circuit's analysis turned on the form's visual architecture, not on the disclosure's textual content. The court did not parse whether the disclosure language adequately described the scope of consent under the TCPA. It did not analyze whether the linked terms of use complied with FCC regulations. It analyzed whether a reasonable user would have seen the disclosure at the moment of clicking. The textual sufficiency question was downstream of the architectural sufficiency question. This is the inversion that *Dahdah* delivered to the lead-generation industry. The prior decade's TCPA litigation focused heavily on the textual completeness of consent disclosures – whether the disclosure named the specific calling party, whether it mentioned autodialer and prerecorded message, whether it complied with the FCC's prior express written consent regulations. *Dahdah* does not displace those questions; they remain relevant once contract formation is established. But it places the architectural question first. If the form's visual design fails the four-factor test, the textual content of the disclosure never reaches analysis, because there is no contract for the textual content to live inside. For operators whose [TCPA defense relies on prior express written consent](/blog/consent-lead-generation-tcpa-pewc-guide/), this reordering matters. The consent record – the database row that captures IP address, timestamp, user agent, and the disclosure text presented – is the second layer of the defense, not the first. The first layer is the page itself. If the page does not satisfy the conspicuousness factors, the consent record points to a contract that never formed. --- ## The Click-Wrap Doctrinal Line: Specht to Sellers The four factors in *Dahdah* did not arise from nowhere. They are a synthesis of two decades of federal click-wrap doctrine, and the synthesis is worth tracing because it tells operators which historical cases their funnels will be measured against. The doctrinal starting point is *Specht v. Netscape Communications Corp.*, 306 F.3d 17 (2d Cir. 2002). The Second Circuit held that a disclosure positioned below the fold – invisible to a user who clicked a download button without scrolling – did not provide the inquiry notice necessary for contract formation. *Specht* established that visibility is the threshold question and that "reasonable inquiry notice" is the standard. The framework was elaborated in *Berkson v. Gogo LLC*, 97 F. Supp. 3d 359 (E.D.N.Y. 2015). Judge Weinstein's analysis cataloged four design considerations – appearance and design of the website, nature of the agreement, opportunity to read, and conspicuousness of the link – and produced a working taxonomy of online contracting modes (browsewrap, clickwrap, sign-in-wrap, scrollwrap) that subsequent courts adopted. *Berkson* is the case operators most often cite when designing form-audit checklists, because it produces the most granular factor list in the doctrinal line. *Sgouros v. TransUnion Corp.*, 817 F.3d 1029 (7th Cir. 2016), addressed a different failure mode: a disclosure that was visible but contradicted by adjacent on-page text. The Seventh Circuit held that a click could not form a contract where the page's surrounding language affirmatively suggested that the click meant something different from what the linked terms said. The lesson for operators is that conspicuousness alone is insufficient; the disclosure must be accurate and consistent with the visual context in which it appears. *Meyer v. Uber Technologies, Inc.*, 868 F.3d 66 (2d Cir. 2017), is the case most cited for the proposition that mobile click-wrap can be enforceable when the disclosure design accommodates the smaller viewport. Uber's signup screen presented a hyperlink to terms in a position that the Second Circuit found legible and proximate to the action button on the iPhone interface in question. *Meyer* is also important for its holding that a reasonably prudent smartphone user is on notice that linked terms exist when the design is competently executed. *Sellers v. JustAnswer LLC*, 73 Cal. App. 5th 444 (2021), is the most operator-relevant California decision. The California Court of Appeal held that JustAnswer's sign-in-wrap was not enforceable because the disclosure was rendered in a font and color combination that rendered it visually subordinate to the action button. *Sellers* introduced a sharper articulation of the visual-conspicuousness factor – distinguishing between text that is "technically visible" and text that is "reasonably noticeable" in context. The *Dahdah* panel did not cite all of these cases by name, but the four-factor framework it articulated maps cleanly onto the doctrinal line. Notice placement is the *Specht* question. Button proximity and visual conspicuousness are the *Berkson* and *Sellers* questions. Dynamic scrolling is the *Meyer* question, updated for the way modern form components reflow on mobile devices. What *Dahdah* added was the synthesis itself – a published appellate opinion in a TCPA context that lower courts can cite as a single, coherent test. ### Why state law variability still matters A practical caveat: contract formation is governed by state law. *Dahdah* applied California law via the LowerMyBills.com terms-of-use choice-of-law clause, putting the Sixth Circuit's analysis on the same doctrinal lane as *Sellers v. JustAnswer*. *Tablada v. Rocket Mortgage*, pending in the District of Rhode Island, will apply Rhode Island law. The four-factor framework converges across jurisdictions because each state's contract-formation doctrine asks substantially the same conspicuousness question, but the weight assigned to particular factors and the threshold for "reasonable conspicuousness" varies. California – through both *Sellers* and now the *Dahdah* analysis flowing from a California choice-of-law clause – runs at the strict end of the conspicuousness spectrum, and the *Dahdah* opinion's articulation of the four-factor test means California's posture is now the working standard for any operator whose form architecture flows through a forum-selection or choice-of-law clause that points to California. Rhode Island's posture in *Tablada* is what the bar is now waiting to see. For operators, the implication is that a form audit must satisfy the strictest jurisdiction in which the funnel operates. A national lead-generation funnel that satisfies a permissive jurisdiction but fails California is functional in some states and broken in others. The audit standard is the strictest jurisdiction; anything less leaves a defense gap that plaintiffs' counsel will exploit by filing in the strict-state forum. --- ## Why the FCC's One-to-One Consent Vacatur Made Dahdah Mission-Critical The *Dahdah* opinion would matter regardless. What makes it mission-critical for lead operators is the regulatory context in which it landed. In December 2023, the FCC adopted what became known as the "one-to-one consent rule," requiring that prior express written consent under the TCPA be obtained for one specifically named seller at a time, rather than for an open list of marketing partners. The rule was scheduled to take effect in early 2025 and was designed to eliminate the long-standing lead-generation practice of obtaining a single consent that authorized contact from any participant in a buyer network. In January 2025, the Eleventh Circuit vacated the one-to-one rule in *Insurance Marketing Coalition v. FCC*, holding that the FCC had exceeded its statutory authority. The vacatur returned the lead-generation industry to the pre-2024 click-wrap framework, in which a single consent disclosure could authorize contact from a defined buyer network. In early 2026, the FCC issued a notice of proposed rulemaking informally known as "Delete, Delete, Delete," proposing to formally eliminate the one-to-one rule from the Code of Federal Regulations and to clarify the Commission's view that the prior framework remains operative. As of April 2026, the NPRM is in comment, and industry expectations are that formal elimination will occur in 2026 or early 2027. The significance of this regulatory sequence for *Dahdah* is direct. With one-to-one vacated and likely formally eliminated, the click-wrap consent framework that *Dahdah* validated is the consent framework operators will use to defend the next several years of TCPA litigation. There is no regulatory backstop. There is no FCC rule that, if satisfied, automatically establishes consent. There is only the click-wrap and its conspicuousness factors. The defense rises or falls on whether the form architecture meets the *Dahdah* test. This is why the trade-press attention has been so concentrated. Kelley Drye's TCPA Tracker estimates that approximately 1,800 TCPA class actions are filed annually in federal court, with the bulk targeting lead-generation publishers and their buyer-network participants. The *Dahdah* framework will govern the consent defense in a substantial share of those cases. For operators, the framework is not an abstraction. It is the litigation reality of every funnel they currently run. ### Where Dahdah sits in the broader 2025-2026 TCPA case cluster *Dahdah* is the click-consent and contract-formation case in a wider 2025-2026 cluster of TCPA decisions that operators should track together rather than in isolation. The cluster's other anchors address adjacent but distinct compliance failure modes. The [Davis v. Healthplex emergency-purposes ruling](/blog/davis-healthplex-emergency-exception-tcpa-insurance/) addresses the purpose-versus-relationship boundary for post-bind insurance servicing calls – a doctrine that does not reach the pre-sale prospecting calls *Dahdah*'s framework most directly affects. The [multistate AG civil investigative demand pattern around 72-hour TCPA enforcement](/blog/multistate-ag-cid-tcpa-enforcement-72-hours/) addresses the state-AG enforcement substitution channel that operates in parallel with the federal class-action pipeline *Dahdah* governs. The [Irvin v. Sonic split between texts and calls under DNC analysis](/blog/tcpa-texts-not-calls-irvin-sonic-dnc-split/) and the [Illinois Rabbit-Rohrman ruling on SMS DNC compliance](/blog/illinois-sms-tcpa-dnc-rabbit-rohrman-ruling/) address text-message-specific consent and DNC issues that *Dahdah*'s click-wrap framework intersects with but does not resolve. The [Know Your Agent (KYA) replacement-compliance framework](/blog/know-your-agent-kya-tcpa-replacement-compliance/) addresses the operational substitute that emerged after the FCC's one-to-one consent vacatur. *Dahdah*'s contribution to this cluster is specifically the click-consent contract-formation lens – the pixel-level question of whether the form architecture supports a binding contract that carries arbitration and PEWC. Compliance officers running funnels exposed to the full cluster should treat *Dahdah* as the form-architecture anchor of an analytical stack that includes the other rulings as separate audit surfaces. ### The arbitration leverage that Dahdah preserves A second-order consequence of the *Dahdah* holding is the preservation of arbitration as the operator's primary defensive lever. A TCPA class action that survives a motion to compel arbitration becomes a class-certification fight, with statutory damages of $500 per violation (treble to $1,500 for willful violations) and class sizes routinely in the tens of thousands. The economic asymmetry is severe: a typical certified TCPA class settles in the range of $6.6 million on average, with high-profile settlements reaching well into eight figures. A successful motion to compel arbitration converts the same case into an individual proceeding with capped damages exposure. The *Dahdah* framework, properly applied, preserves the arbitration lever. Operators whose funnels satisfy the four factors retain the ability to compel arbitration on the contract-formation theory the Sixth Circuit blessed. Operators whose funnels fail the factors lose the arbitration lever and face the full class-action exposure. The economic distance between those two outcomes – the difference between an individual arbitration and a certified class – is the difference that the form audit determines. For practitioners thinking about [the relationship between arbitration clauses and TCPA defense](/blog/arbitration-clauses-tcpa-protection/), *Dahdah* is the doctrinal anchor. The arbitration clause itself is meaningful only to the extent that the click-wrap that incorporated it formed a contract. That contract-formation question is the *Dahdah* question. --- ## The Form Audit: What Actually Has to Be Measured The form audit that *Dahdah* requires is more granular than most lead-generation operators currently run. The factors translate into specific, measurable design parameters that compliance review must capture and that engineering must control. ### Factor one: notice placement The audit task is to document where on the rendered page the disclosure text appears relative to the action button. Documentation requires a screenshot of the form in its rendered state, with the disclosure text and the button both visible in the same frame. The screenshot must capture the page at multiple viewport widths – desktop, tablet, mobile – because reflow can change the spatial relationship between disclosure and button. The audit standard, drawn from the *Dahdah* analysis and the underlying *Specht* line, is that the disclosure must be in the same visual block as the button, with no intervening content (other content, white space exceeding a defined threshold, decorative elements) that visually separates the disclosure from the button. Disclosures positioned in a footer, in a separate panel, or below additional form fields fail the placement factor. The documentation requirement is screenshots, not descriptions. Plaintiffs' counsel in *Dahdah* and similar cases will subpoena and depose form designers about the rendered state of the page on the date the plaintiff used it. Operators who cannot produce dated, rendered screenshots of their form's actual appearance on the relevant date will face significant evidentiary difficulty. ### Factor two: button proximity The audit task is to measure the pixel-level distance between the closest edge of the disclosure text and the closest edge of the action button. The measurement must be performed at each viewport width, because responsive design can change the proximity at different breakpoints. The audit standard is informal but consistent across the recent district-court decisions applying *Dahdah*: a proximity of less than approximately 15-20 pixels at standard zoom is generally treated as sufficient; proximity of more than 40-50 pixels is treated as suspect; intermediate ranges are case-specific. The rendered measurement, not the CSS specification, is what the court analyzes – a CSS margin of "10px" can produce a different effective proximity depending on the surrounding box model and inherited styles. Documentation requires both the screenshot and the underlying HTML and CSS as rendered (not as authored). Browser developer tools can capture the rendered measurement; the audit artifact is a saved version of that measurement plus the screenshot. ### Factor three: visual conspicuousness The audit task is to evaluate the disclosure's font size, color, contrast, weight, and visual hierarchy relative to the button label and surrounding text. The audit standard incorporates several measurable parameters. Font size. Disclosures rendered in less than 10-point equivalent (approximately 13.3px at standard rendering) face increased scrutiny. The *Sellers* decision was particularly skeptical of disclosures rendered in 8-point equivalent. Color contrast. Web Content Accessibility Guidelines (WCAG) contrast ratios are not the legal standard, but they have become the de facto baseline that courts cite. A disclosure with contrast below WCAG AA (4.5:1 for normal text) faces increased scrutiny; contrast below WCAG A (3:1) is generally treated as a conspicuousness failure. Weight and emphasis. A disclosure rendered in a thinner weight than the button label or surrounding body copy is visually subordinated and faces increased scrutiny. Visual hierarchy. The disclosure should not be positioned within a visual block that the design treats as supplementary to the primary action – for example, in a "fine print" or "legal" section that the page's visual language signals as auxiliary. The *Sellers* analysis was particularly attentive to this hierarchy question. Documentation requires both the screenshot and a quantitative record of each parameter – font size in pixels, contrast ratio measured against the actual rendered background, weight specification – captured at the rendered state. ### Factor four: dynamic scrolling The audit task is to evaluate whether the disclosure remains visible to the user during the form interaction sequence that culminates in the click. The audit standard, which the *Dahdah* panel and subsequent district courts have developed, is whether a reasonable user could reasonably encounter the disclosure as part of the action of clicking the button. Several common failure patterns emerge in funnel design. Long forms that auto-scroll as fields are completed can move the disclosure off-screen before the user reaches the submit button. Mobile viewports can clip the disclosure when the on-screen keyboard is active. Sticky button components that float at the bottom of the viewport can be visible while the disclosure (positioned above the button in document order) is scrolled out of view. Dynamic content insertion – such as conditional fields that expand the form between the disclosure and the button – can introduce intervening content that violates the placement factor at certain interaction states. Documentation requires recordings or sequenced screenshots of the actual user interaction flow at each viewport width, capturing the disclosure-button visual relationship at the moment immediately before the click. Static screenshots of the rendered form are insufficient for this factor; the audit must capture the dynamic state. ### The audit artifact: what to retain The form audit produces a per-page artifact bundle that should be retained as part of the operator's compliance documentation. The bundle includes, at minimum: - Dated screenshots at desktop, tablet, and mobile viewport widths showing the disclosure-button relationship - Recorded interaction sequences (video or sequenced screenshot capture) showing the dynamic state at the moment of click - Rendered HTML and CSS captures showing the actual layout - Quantitative measurements of font size, color contrast, button proximity, and disclosure visibility duration - Version-control history linking the audit artifact to the specific page version that was live at the time of audit Retention should align with the [TCPA documentation retention framework](/blog/consent-documentation-retention-tcpa/) – the audit artifact has the same evidentiary status as the consent record itself and should be retained for the same period (most operators retain consent documentation for at least four years, and the same retention applies to form-audit artifacts). --- ## The CSS as Evidence: Why Engineering Owns the TCPA Defense Now The operational implication of *Dahdah* is that the engineering team responsible for the form's CSS now owns a non-trivial share of the operator's TCPA defense. This is a reorganization that most lead-generation operators have not formally made, and the reorganization carries practical consequences. ### The version-control problem Marketing teams iterate on lead forms continuously. A/B tests change button positioning. Conversion-rate optimization sprints adjust font sizes and color contrasts. Mobile-first redesigns move the disclosure into different visual hierarchies. Each iteration alters the form's compliance posture under *Dahdah* – sometimes improving it, sometimes degrading it, sometimes leaving it unchanged in ways that are difficult to confirm without an audit. Most operators do not maintain a version-control history that ties marketing iterations to compliance reviews. Forms are deployed through marketing-page builders, content-management systems, or component-library frameworks that abstract the rendered state away from the team responsible for compliance. When a TCPA class is filed alleging conduct on a specific date, the operator must reconstruct the form's appearance on that date – and the reconstruction is often impossible because the version history was not preserved. The *Dahdah* implication is that version control of marketing pages is now a litigation-evidence problem. Operators need to retain dated, rendered captures of every form variant that has ever served live traffic, indexed to the date range during which each variant was active. This is not a marketing-analytics retention requirement; it is a compliance-evidence retention requirement, with substantially longer retention horizons and more rigorous chain-of-custody expectations. ### The A/B testing problem A/B testing is, by design, a process of running multiple form variants against live traffic and measuring conversion outcomes. Each variant has its own compliance posture. A test that includes a variant with degraded conspicuousness – for example, a smaller font size on the disclosure to make room for a larger, higher-converting button – is a test that exposes some share of users to a non-compliant form. If a TCPA class is filed by a user who interacted with a degraded variant, the operator's defense depends on whether that specific variant satisfies the *Dahdah* test. The operator's overall conversion-optimization story is irrelevant; the question is whether the form the plaintiff actually saw was compliant. This is why [A/B testing of lead forms](/blog/ab-testing-lead-forms-guide/) now requires a compliance-screening step that most operators do not currently run. Each variant should be evaluated under the four-factor framework before it is included in a test. Variants that materially degrade conspicuousness should be excluded from production testing, regardless of their conversion-rate potential. The conversion benefit of a degraded variant cannot offset the litigation exposure if a plaintiff interacts with it. ### The mobile-vs-desktop divergence A form's compliance posture under *Dahdah* can differ between desktop and mobile rendering even when the underlying CSS is unchanged, because viewport differences, font scaling, and dynamic content reflow produce different rendered states. A form that satisfies the four factors on desktop can fail them on mobile if the disclosure is clipped by the on-screen keyboard, or if the mobile viewport's narrower width pushes the disclosure into a stacked block that auto-scrolls off-screen. The audit must cover both rendering modes. Most operators run mobile-specific compliance audits less rigorously than desktop audits, partly because the desktop rendering is easier to capture and partly because compliance teams are typically more familiar with desktop layouts. *Dahdah* and its progeny – including the *Tablada* filing in D.R.I. – are likely to be litigated significantly on mobile rendering, because mobile traffic is the majority share of lead-generation funnel traffic and because mobile-specific failure modes are more common. For operators whose funnels are mobile-dominant – most consumer-finance, solar, and insurance lead-generation pages – the audit emphasis should be on mobile rendering first. --- ## The Three Vertical Hot Spots: Mortgage, Solar, Insurance *Dahdah* itself is a mortgage case. *Tablada* is a mortgage case. The trade-press attention has concentrated on mortgage-vertical implications because the underlying litigation arose in that vertical. But the doctrinal framework is industry-neutral, and the verticals where the implications are most acute extend beyond mortgage. ### Mortgage: high CPL, dense buyer networks The mortgage vertical is the canonical *Dahdah* vertical. Cost-per-lead in mortgage runs $25-100 depending on credit-score band and loan purpose, and the buyer networks are dense – a typical mortgage lead routes through the LowerMyBills, LendingTree, Rocket Mortgage, or Quicken-aligned aggregator stack to a network of fifteen-to-fifty receiving lenders. Each call from each receiving lender that is not covered by a properly formed consent contract is a per-violation TCPA exposure. The class sizes are large because the funnels operate at high volume. The damages stack quickly. For mortgage operators specifically, the form audit is a near-term operational priority. The trade-press treatment has signaled to the plaintiffs' bar that mortgage is the vertical to file in. The *Tablada* case in D.R.I. is the next testing ground, and the operators routing leads through the same publisher networks Dahdah used – LowerMyBills and adjacent aggregators – should expect to be named in subsequent filings if their funnels deviate from the *Dahdah*-validated architecture. ### Solar: long-cycle conversion, intense post-lead contact The solar vertical operates on a different conversion cycle but the same TCPA exposure. Solar leads typically convert over weeks-to-months, with intense outbound contact from installer-network sales teams during the qualification period. The contact intensity multiplies the per-lead violation count if consent fails. Solar funnels often include long, multi-step forms that aggravate the dynamic-scrolling factor – disclosures positioned at the top of a six-step form sequence may not be visible at the moment of the final-step click, depending on how the form's progress UI is designed. Solar operators' form audits should focus particularly on the dynamic-scrolling factor and on how multi-step forms preserve disclosure visibility through the interaction sequence. The most common failure mode is a disclosure that appears on step one and is no longer on-screen when the user clicks the submit button on step six. ### Insurance: heavy automation, marketplace dynamics The insurance vertical – auto, home, life, health – runs the most heavily automated outbound contact pattern of the three. Autodialer campaigns, prerecorded message tests, and SMS sequences create high per-lead message volumes that produce substantial damages stacks if consent fails. Insurance lead operators often work with affiliate publisher networks where the form architecture varies across publishers; the receiving carrier is often two or three steps removed from the form the consumer actually clicked. For insurance operators, the audit complexity is the affiliate-publisher dimension. The receiving carrier's defense depends on the form architecture of the publisher that captured the lead – but the carrier may have limited visibility into that architecture, depending on the affiliate-network agreement. Insurance carriers should be auditing their affiliate publishers' form architectures and contractually requiring documentation that meets the *Dahdah* standard. Across all three verticals, the common pattern is that the form audit is no longer a once-a-year compliance exercise. It is a continuous operational requirement that scales with the rate of funnel iteration. Operators who treat the audit as quarterly or annual will accumulate compliance gaps faster than the audit cycle can close them. --- ## The Approaches That Will Underperform This Cycle Three responses to *Dahdah* are visible in the early industry chatter. Each will produce worse outcomes than its proponents expect. The first is the wait-and-see posture. The argument runs that *Dahdah* is a single Sixth Circuit opinion, that *Tablada* is still pending, that the doctrine is unsettled, and that operators should wait to see how the framework develops before investing in form-audit infrastructure. The problem with this argument is that the framework is not unsettled; it is a synthesis of two decades of click-wrap doctrine that has been consistent across federal circuits since *Specht*. *Dahdah*'s contribution is the published TCPA-context articulation, not the framework itself. Operators who wait will accumulate exposure on every form that fails the test during the wait period. Plaintiffs' counsel are not waiting. The second is the form-doesn't-matter posture. The argument runs that the operator's TCPA defense rests on the textual content of the consent disclosure and the consent record, not on the form's visual architecture. If the disclosure language is correct and the consent record is properly captured, the form architecture is a secondary concern. The argument was defensible before *Dahdah*. It is no longer. The Sixth Circuit's analysis placed the architectural question first; the textual sufficiency question is downstream of contract formation. A form that fails the four factors does not produce a contract, and a defective contract does not provide a TCPA defense regardless of how completely the disclosure language is drafted. The third is the legalese-overload posture. The argument runs that adding more disclosure language – longer, more detailed, more comprehensive – strengthens the consent defense by giving the courts more textual content to find sufficient. The empirical effect of this approach in practice is the opposite. Longer disclosures push more text into the visual block, which competes with the button for attention and degrades the visual conspicuousness factor. The *Sellers* analysis was particularly clear that visual subordination of the disclosure – including by burying it in surrounding legal text – is a conspicuousness failure regardless of how complete the disclosure language is. The common pattern across these three approaches is that each underestimates the speed at which the *Dahdah* framework will become operative case law in lead-generation contexts. The framework is already being applied in district courts within the Sixth Circuit. The *Tablada* case will produce a Rhode Island application. By the end of 2026, similar opinions will likely have emerged in the Ninth, Eleventh, and Second Circuits as the trade-press concentration on the doctrine attracts plaintiffs' counsel filings in those forums. The operators who satisfy the framework now have a defense that will hold in the next eighteen months. The operators who delay will face the doctrine's tightening curve while still running funnels designed for the pre-*Dahdah* environment. --- ## The Strategic Reframe: Form as Litigation Evidence The right response to *Dahdah* starts from a different premise. The lead-generation form is no longer a marketing surface that compliance occasionally reviews. It is a litigation artifact that engineering and compliance jointly own and that marketing operates within. ### Principle one: every form variant is an evidence record In the legacy operating model, marketing iterates forms continuously and compliance reviews them episodically. In the *Dahdah*-aware model, every form variant is a discrete evidence record that is subject to retention, version control, and compliance attestation before it serves traffic. The marketing iteration cycle is not slower under this model, but it is better instrumented – every change is captured, every version is testable, and every variant's compliance posture is documented at the moment of deployment. Operators who adopt this model report initial slowdowns in iteration velocity (typically 10-20 percent during the first quarter of adoption) followed by velocity recovery as the instrumentation becomes routine. The compliance overhead is real but bounded. ### Principle two: the form's compliance posture is a CRO constraint [Conversion-rate optimization on lead forms](/blog/anatomy-high-converting-lead-form/) traditionally trades against several constraints – page load speed, form length, friction in field design – but it has rarely been disciplined by a hard compliance constraint at the disclosure level. *Dahdah* introduces that constraint. A button-position change that improves conversion by 12 percent but pushes the disclosure outside the audit standard's proximity tolerance is a net-negative change. The conversion gain is realized in the marketing analytics; the litigation exposure is realized in the legal department's settlement reserves. The marketing analytics typically have higher organizational visibility than the settlement reserves, which is part of why the legacy model produced compliance gaps. Bringing the compliance constraint into the CRO process explicitly – with a hard rule that no variant deviating from the audit standard reaches production traffic – is the only stable equilibrium. This is the operational discipline that [AIDA-driven lead form copywriting](/blog/aida-copywriting-lead-forms-landing-pages/) and conversion design must integrate. The disclosure is not the part of the form that the copywriter optimizes for action; it is the part that the architect places to satisfy the compliance constraint. ### Principle three: the buyer side requires consent documentation chain-of-custody For receiving lenders and carriers in mortgage, solar, and insurance buyer networks, the *Dahdah* framework introduces a documentation requirement that flows backward through the publisher chain. The buyer's TCPA defense depends on the form architecture of the publisher that captured the lead. The buyer needs documentation that the form satisfied the four factors at the moment the lead was captured. Buyer-side documentation requirements should include, at minimum: - A contractual representation from the publisher that the form satisfied the audit standard at the date of lead capture - Access to the publisher's form-audit artifact bundle for the specific page version that was live on the capture date - A representation regarding mobile-versus-desktop compliance posture - A representation regarding which buyer-network participants were named in the consent disclosure (relevant if any portion of the one-to-one framework is reinstated) Publishers who cannot or will not provide this documentation should be repriced or removed from the buyer's preferred-source list. The buyer's counterparty risk on a non-documenting publisher is the full TCPA exposure on every lead that publisher delivers – an exposure that exceeds the cost-per-lead saving by orders of magnitude in any plausible scenario. ### Principle four: bot detection and form integrity become consent-defense components A form-audit defense depends on the consent record reflecting an actual human interaction with the form as audited. If the consent record can be impeached as having originated from a bot, a form-fill service, or a fraudulent re-render of the form (one that bypasses the audited disclosure), the defense fails. [Bot detection and CAPTCHA integration on lead forms](/blog/bot-detection-captcha-lead-forms-implementation/) is therefore not only a fraud-prevention concern; it is a consent-defense concern. Operators whose forms are vulnerable to automated submission cannot fully rely on the *Dahdah* framework, because the contract-formation analysis presumes a human user who saw the audited form. The integration is operationally straightforward – most operators already run CAPTCHA or device-fingerprint-based bot detection on lead forms – but the audit artifact should explicitly link the bot-detection logs to the consent record, so the chain-of-custody connecting the audited form to the human user is verifiable. --- ## Implementation Reality: A Realistic Audit Timeline The form audit, properly executed, is not a one-week project. The implementation timeline for a mid-sized lead-generation operator with a portfolio of fifteen to fifty active landing pages is several months end-to-end. | Phase | Duration | Key Activities | |-------|---------:|----------------| | Inventory | 14-21 days | Catalog all active lead-generation pages, including A/B test variants and affiliate-network-specific pages | | Audit standard authoring | 14-21 days | Define quantitative thresholds for each factor (proximity, font size, contrast, etc.) calibrated to the strictest jurisdiction in the operator's footprint | | Audit execution | 30-60 days | Run the audit standard against every page in inventory; capture screenshots, rendered HTML/CSS, and dynamic interaction recordings | | Remediation prioritization | 14-21 days | Triage failed pages by traffic volume and exposure risk; sequence remediation based on impact-weighted ranking | | Page remediation | 60-120 days | Re-engineer failed pages to satisfy audit standard; integrate compliance review into deployment pipeline | | Documentation infrastructure | 30-45 days | Build version-control system for form variants with linkage to audit artifacts | | Buyer-network attestation | 30-45 days | For publishers, prepare documentation that buyers can rely on; for buyers, request documentation from publishers | | Total elapsed time | 4-6 months | Conservative estimate for an operator without prior structured form audit | *Source: Composite of trade-press implementation guidance and analysis of publisher-buyer documentation practices* The critical-path items in this timeline are the audit execution phase and the page remediation phase. The audit execution requires manual review of every page across multiple viewport widths, with the dynamic-state captures that static screenshots cannot replace. Most operators will discover that the audit takes longer than they estimated because the interaction-state captures require operator-time per page that does not scale linearly with the number of pages. The remediation phase is gated by engineering capacity and by the marketing organization's willingness to accept the audit standard as a binding constraint on iteration. Operators where marketing controls the form-builder configuration without engineering or compliance review will face longer remediation phases; operators with formal change-management processes and shared form-component libraries will move faster. ### Common obstacles Three obstacles consistently slow these implementations beyond the nominal timeline. The first is the affiliate-publisher visibility gap. Operators who source leads from affiliate publishers often do not control the publisher's form architecture and have limited visibility into it. Securing the documentation that the audit standard requires depends on the affiliate agreement and the publisher's willingness to cooperate. Some publishers will cooperate readily; others will require contract renegotiation or removal from the operator's source list. The second is the legacy form-builder lock-in. Operators on commercial form-builder platforms (HubSpot, Marketo, Unbounce, ClickFunnels, and similar) have varying degrees of control over the rendered output. Some platforms generate clean, controllable HTML/CSS that the audit can certify. Others produce complex, dynamically-injected layouts where the rendered state is difficult to audit and even more difficult to control across viewport widths. Operators on lock-in platforms may need to migrate to a more controllable form-rendering stack – a migration that is expensive but increasingly unavoidable. The third is the A/B testing infrastructure gap. Operators running statistically rigorous A/B testing programs need to integrate compliance screening into the test design without crippling the testing velocity. The operational answer is a compliance-pre-screen step that runs on every variant before it enters production traffic, plus a kill-switch that automatically removes any variant that drifts outside the audit standard during the test. Building this infrastructure is a non-trivial engineering project, typically forty to sixty engineering days. --- ## What the Tablada Case Will Likely Tell Us The *Tablada v. Rocket Mortgage* filing in the District of Rhode Island (No. 1:2026cv00118) is the next significant testing ground for the *Dahdah* framework. The case is at an early stage as of April 2026, and the docket activity to date has focused on initial pleadings and preliminary motions. Several questions the case is positioned to answer are worth flagging because they will affect operator audit standards. The first question is whether the Rhode Island federal courts will adopt the *Dahdah* framework directly or will articulate Rhode Island-specific contract-formation factors that diverge from California's. Rhode Island contract law is generally aligned with the multi-factor conspicuousness analysis that the federal circuits have applied, but the weight assigned to particular factors can vary at the state-law margin. A Rhode Island opinion that placed greater weight on, for example, the visual-conspicuousness factor relative to button-proximity would tighten the audit standard for operators with funnels in the District of Rhode Island. The second question is how the case treats mobile-specific factors. The trade-press commentary has noted that *Tablada* is positioned to produce more granular guidance on mobile rendering than *Dahdah* did, because the underlying funnel-interaction record may include mobile-specific allegations. If the District of Rhode Island produces a published decision that articulates mobile-specific conspicuousness factors, those factors will become part of the audit standard for national operators. The third question is whether the Rhode Island court accepts the same arbitration-leverage outcome that the Sixth Circuit adopted in *Dahdah*. The same fact pattern – click-wrap, terms of use with arbitration clause, TCPA claim, motion to compel – will be litigated again. A Rhode Island ruling consistent with *Dahdah* would extend the framework's persuasive reach into the First Circuit; a ruling diverging from *Dahdah* would create the kind of circuit-split tension that elevates issues toward Supreme Court attention. For operators, the *Tablada* docket should be monitored. The case is likely to produce intermediate rulings (motion to compel, possible denial, possible appeal to the First Circuit) over the course of 2026. Each ruling will tighten or loosen the audit standard, and operators should be prepared to update their audit specifications in response. ### The other circuits to watch Beyond *Tablada*, several pending and likely-to-be-filed cases will shape the *Dahdah* framework's reach across other circuits. The Ninth Circuit, which has been particularly active in TCPA litigation and in click-wrap doctrine more generally, is likely to produce a *Dahdah*-aligned opinion within twelve to eighteen months as plaintiffs' counsel file in that forum. The Eleventh Circuit's posture is shaped by the *Insurance Marketing Coalition* vacatur of the one-to-one rule and by the bar's expectation that the FCC's "Delete, Delete, Delete" NPRM will land formal elimination in 2026 or early 2027. The Second Circuit's posture is shaped by *Specht* and *Meyer*, both of which align with *Dahdah*'s synthesis. The aggregate picture is that the *Dahdah* framework is unlikely to be displaced or significantly narrowed across circuits over the next eighteen months. The variations will be at the margin – weighted differently in different jurisdictions, with state-specific contract-law overlays – but the core four-factor analysis will hold. --- ## Future Implications: The Five-Year Trajectory of TCPA Form Compliance The *Dahdah* opinion is the first substantial doctrinal event in a multi-year sequence that will reshape how lead-generation operators design, document, and defend their forms. In the next twelve months, the form-audit standard will harden into industry practice. Trade groups will publish reference audit specifications. Outside counsel will offer audit-as-a-service engagements. Form-builder platforms will introduce compliance-screening features that automate parts of the audit. The audit will move from a novel concept to a standard operational requirement, and operators who have not adopted the practice by Q2 2027 will be running funnels at material disadvantage to the cohort that has. In the next twenty-four months, the buyer-side documentation requirement will harden into contract terms. Mortgage, solar, and insurance buyers will require publisher attestations and audit-artifact access as a condition of buyer-network participation. Publishers who cannot or will not provide the documentation will be repriced or removed from preferred-source lists. The compliance posture of a publisher's form will become a quantitative input to the buyer's pricing model, with non-compliant inventory bid lower regardless of conversion quality. In the next thirty-six months, automated form-compliance monitoring will become commercially available at scale. The technology – periodic crawling, rendered-state capture, automated conspicuousness measurement – is straightforward and is already in development at several compliance-tech startups. By 2029, the standard practice will be continuous monitoring with automated remediation alerts, replacing the periodic-audit cadence that the next two years will normalize. In the next sixty months, the litigation pipeline will produce circuit-level convergence on the four-factor framework, possibly culminating in Supreme Court attention on a focused subset of factors (most likely the dynamic-scrolling factor, where mobile-specific interpretations vary most). The convergence will narrow the operator's compliance window – the strictest jurisdiction's standard will become the de facto national standard – but will also stabilize the audit specification, allowing operators to invest in compliance infrastructure with confidence in its multi-year durability. For lead operators, the strategic implication is to build the audit infrastructure for the world after the framework's convergence, not just the world after *Dahdah*. A form-audit system that captures the full evidence record at deployment time, retains it under version control, and integrates compliance pre-screening into the CRO and A/B testing process is durable across whatever circuit-level developments emerge. A system optimized only to pass the *Dahdah* test as currently articulated will need to be re-engineered as the framework tightens. --- ## Key Takeaways The Sixth Circuit's January 26, 2026 decision in *Dahdah v. Rocket Mortgage* repositioned the lead-generation web form from a marketing surface into a litigation artifact, with a four-factor conspicuousness test (notice placement, button proximity, visual conspicuousness, dynamic scrolling) governing whether the click-wrap forms a binding contract carrying both arbitration and TCPA prior express written consent. The four-factor framework is a synthesis of two decades of click-wrap doctrine traceable through *Specht*, *Berkson*, *Sgouros*, *Meyer*, and *Sellers*. *Dahdah*'s contribution is the published TCPA-context articulation, not the underlying analytical structure, which is why the framework is unlikely to be displaced or significantly narrowed by subsequent circuits. With the FCC's one-to-one consent rule vacated by the Eleventh Circuit's *Insurance Marketing Coalition* decision and the Commission's "Delete, Delete, Delete" NPRM proposing formal elimination, the click-wrap consent framework that *Dahdah* validated is the consent framework operators will use to defend an estimated 1,800 TCPA class actions filed annually. The economic asymmetry between an arbitration-bound dispute and a class-cert-bound dispute – individual damages caps versus an average $6.6 million certified class settlement – is the asymmetry the form audit determines. A funnel that satisfies the four factors retains the arbitration lever; a funnel that fails the factors loses it. The form audit is more granular than most operators currently run. It requires per-page documentation of dated screenshots at multiple viewport widths, recorded interaction sequences capturing dynamic state, rendered HTML and CSS captures, and quantitative measurements of font size, color contrast, button proximity, and disclosure visibility duration. The audit is now a continuous operational requirement, not an annual compliance exercise. A/B testing integration, version control of form variants, mobile-specific compliance review, and bot-detection chain-of-custody linkage to the consent record are the four operational disciplines that turn the audit from a one-time exercise into a stable practice. The vertical hot spots are mortgage (where *Dahdah* and *Tablada* arose), solar (where multi-step funnel architecture aggravates the dynamic-scrolling factor), and insurance (where affiliate-publisher visibility gaps complicate the buyer-side documentation chain). Each vertical has a vertical-specific audit emphasis, but the four-factor framework applies uniformly. Three approaches will underperform: the wait-and-see posture (accumulates exposure during the wait period), the form-doesn't-matter posture (relies on a textual-sufficiency argument that the framework no longer treats as primary), and the legalese-overload posture (degrades visual conspicuousness by adding text that competes with the button for attention). The realistic implementation timeline for a mid-sized operator is four to six months end-to-end, with audit execution and page remediation as the critical-path items. The infrastructure investment is non-trivial but bounded; the litigation exposure of running un-audited funnels through 2026 substantially exceeds the audit investment. The *Tablada v. Rocket Mortgage* case in the District of Rhode Island is the next testing ground for the framework. Operators should monitor the docket and be prepared to update audit specifications in response to intermediate rulings throughout 2026. The five-year trajectory points toward industry-standard audit specifications by Q2 2027, buyer-side documentation requirements as standard contract terms by 2028, automated form-compliance monitoring at scale by 2029, and circuit-level framework convergence by 2031. Operators who build the audit infrastructure now have a six-to-twelve-month structural advantage in defending the litigation pipeline that the next eighteen months will produce. --- ## Frequently Asked Questions ### What did the Sixth Circuit hold in Dahdah v. Rocket Mortgage? On January 26, 2026, the Sixth Circuit reversed the Eastern District of Michigan's denial of Rocket Mortgage's motion to compel arbitration in *Dahdah v. Rocket Mortgage, LLC*, No. 24-1910 (6th Cir.). The court held that the click-wrap signup on the LowerMyBills.com mortgage-shopping form formed a binding contract under California law (per the LowerMyBills.com choice-of-law clause), that the contract carried both an arbitration clause and a TCPA prior express written consent provision, and that the dispute belonged in individual arbitration rather than in federal court class proceedings. The court applied a four-factor conspicuousness test – notice placement, button proximity, visual conspicuousness of the disclosure text, and dynamic scrolling behavior – and found that the LowerMyBills.com funnel satisfied each factor. The opinion is most consequential not for the specific outcome but for the published articulation of the four-factor framework in a TCPA context, which lower courts have already begun applying to other lead-generation funnels. ### How does the four-factor test relate to prior click-wrap cases? The four factors are a synthesis of click-wrap doctrine traceable through several federal appellate decisions. *Specht v. Netscape Communications Corp.*, 306 F.3d 17 (2d Cir. 2002), established that visibility is the threshold question and that disclosures positioned below the fold do not provide reasonable inquiry notice. *Berkson v. Gogo LLC*, 97 F. Supp. 3d 359 (E.D.N.Y. 2015), produced the most granular taxonomy of online contracting modes and the most detailed factor catalog. *Sgouros v. TransUnion Corp.*, 817 F.3d 1029 (7th Cir. 2016), addressed cases where adjacent on-page text contradicted the disclosure. *Meyer v. Uber Technologies, Inc.*, 868 F.3d 66 (2d Cir. 2017), addressed mobile click-wrap enforceability. *Sellers v. JustAnswer LLC*, 73 Cal. App. 5th 444 (2021), tightened the visual-conspicuousness factor. *Dahdah*'s contribution is not new doctrine but a clean published TCPA-context synthesis that is straightforward for lower courts to apply. ### Why does the FCC's one-to-one consent rule vacatur matter for Dahdah? The FCC's December 2023 one-to-one consent rule would have required that prior express written consent be obtained for one specifically named seller at a time, replacing the long-standing click-wrap framework that allowed a single consent to authorize contact from a defined buyer network. The Eleventh Circuit vacated the rule in January 2025 in *Insurance Marketing Coalition v. FCC*. The FCC's 2026 "Delete, Delete, Delete" NPRM proposes formal elimination of the rule. With the regulatory backstop removed, operators are returning to the click-wrap framework that *Dahdah* validates, which makes the form-audit standard the operator's primary consent defense. There is no FCC rule that, if satisfied, automatically establishes consent. The defense rises or falls on whether the form architecture meets the *Dahdah* test. ### What is the economic difference between arbitration and class certification in TCPA cases? A TCPA class action that survives a motion to compel arbitration becomes a class-certification fight, with statutory damages of $500 per violation (treble to $1,500 for willful violations) and class sizes routinely in the tens of thousands. The average certified TCPA class settlement is approximately $6.6 million, with high-profile settlements reaching well into eight figures. A successful motion to compel arbitration converts the same case into an individual proceeding with capped damages exposure – typically four to six figures on individual claims. The form audit is the lever that determines whether an operator retains the ability to compel arbitration. The economic distance between the two outcomes – the difference between an individual arbitration and a certified class – is the asymmetry that justifies the audit investment. ### What is the LowerMyBills.com funnel architecture that Dahdah examined? LowerMyBills.com operates a multi-step mortgage-shopping form that captures borrower information – loan purpose, property type, credit-score band, contact details – and routes the resulting lead to mortgage lenders within its buyer network. At the end of the form sequence, the user clicks an action button. Adjacent to the button is a disclosure stating that by clicking, the user agrees to the site's terms of use and privacy policy and consents to be contacted by the buyer network at the phone number provided, including by autodialer and prerecorded message. The terms of use, accessed through a hyperlink in the disclosure, contain both a binding arbitration clause and a class-action waiver. The Sixth Circuit's analysis examined this architecture factor by factor and found that the disclosure's notice placement, button proximity, visual conspicuousness, and scroll behavior all satisfied the conspicuousness standard. ### What does the Tablada v. Rocket Mortgage case add to the picture? *Tablada v. Rocket Mortgage, LLC*, No. 1:2026cv00118 (D.R.I.), is a companion case raising similar TCPA and arbitration questions in the District of Rhode Island. As of April 2026, the case is at an early stage and the docket activity has focused on initial pleadings and preliminary motions. The case is positioned to produce intermediate rulings throughout 2026 that will tell operators how the *Dahdah* framework applies under Rhode Island contract law, whether the framework receives more granular mobile-specific guidance, and whether the arbitration-leverage outcome the Sixth Circuit adopted is replicated in the First Circuit. The case is the next significant testing ground for the framework, and operators should monitor the docket. ### What does a form-audit artifact bundle actually contain? A complete form-audit artifact bundle for a single lead-generation page contains, at minimum: dated screenshots at desktop, tablet, and mobile viewport widths showing the disclosure-button visual relationship; recorded interaction sequences (video or sequenced screenshot capture) showing the dynamic state at the moment immediately before the click; rendered HTML and CSS captures showing the actual layout (not the authored CSS specification); quantitative measurements of font size, color contrast, button proximity, and disclosure visibility duration; and version-control history linking the audit artifact to the specific page version that was live at the time of audit. Retention should align with the operator's TCPA documentation retention policy, typically at least four years and longer for high-volume publishers. The audit bundle is the evidentiary record that supports the contract-formation defense in subsequent litigation; without it, the operator is forced to reconstruct the page's appearance retrospectively, which is often impossible. ### How do mobile-specific factors complicate the audit? A form's compliance posture under *Dahdah* can differ between desktop and mobile rendering even when the underlying CSS is unchanged, because viewport differences, font scaling, on-screen keyboard interactions, and dynamic content reflow produce different rendered states at the moment of click. Common mobile-specific failure modes include disclosures clipped by the on-screen keyboard, sticky button components that float at the bottom of the viewport while the disclosure scrolls out of view, multi-step forms whose progress UI pushes the disclosure off-screen at intermediate states, and dynamic content insertion that introduces intervening visual elements between the disclosure and the button. Operators whose funnel traffic is mobile-dominant – which describes most consumer-finance, solar, and insurance funnels – should treat mobile rendering as the audit priority, not as a secondary check. ### How should A/B testing integrate with the audit standard? Each form variant in an A/B test has its own compliance posture, and a test that includes a variant with degraded conspicuousness exposes some share of users to a non-compliant form. The operational answer is a compliance-pre-screen step that runs on every variant before it enters production traffic, with hard rules that exclude variants deviating from the audit standard regardless of conversion-rate potential. Operators should also build an automated kill-switch that removes any variant that drifts outside the audit standard during the test (for example, due to a CSS regression in the variant's deployed code). Building this infrastructure is a non-trivial engineering project – typically forty to sixty engineering days – but it is the difference between a testing program that respects the compliance constraint and a testing program that systematically generates litigation evidence against its own operator. ### What documentation should buyers require from publishers? For receiving lenders and carriers, buyer-side documentation requirements should include a contractual representation from the publisher that the form satisfied the audit standard at the date of lead capture; access to the publisher's form-audit artifact bundle for the specific page version that was live on the capture date; a representation regarding mobile-versus-desktop compliance posture; and a representation regarding which buyer-network participants were named in the consent disclosure. Publishers who cannot or will not provide this documentation should be repriced or removed from the buyer's preferred-source list. The buyer's counterparty risk on a non-documenting publisher is the full TCPA exposure on every lead that publisher delivers, which exceeds any plausible cost-per-lead saving by orders of magnitude. ### How do affiliate-publisher relationships complicate the audit? Operators who source leads from affiliate publishers often do not control the publisher's form architecture and have limited visibility into it. The receiving carrier's TCPA defense depends on the publisher's form architecture at the date of capture, but the carrier may have neither the contractual right to audit nor the operational visibility to confirm compliance. The remedy is contract renegotiation that incorporates audit-artifact access and compliance representations as material terms. Some publishers will cooperate readily; others will require pricing concessions in exchange for the documentation; some will refuse and will need to be removed from the carrier's source list. Affiliate-network agreements written before *Dahdah* generally do not include the necessary terms, so a renegotiation cycle through the operator's affiliate base is the typical first-year remediation activity. ### What is the realistic timeline for a mid-sized lead operator to implement the audit? A typical implementation timeline for a mid-sized operator with fifteen to fifty active lead-generation pages runs four to six months end-to-end. The phases are: inventory of all active pages including A/B test variants and affiliate-network-specific pages (14-21 days); audit standard authoring with quantitative thresholds calibrated to the strictest jurisdiction in the operator's footprint (14-21 days); audit execution against every page in inventory with screenshots, rendered HTML/CSS, and dynamic interaction recordings (30-60 days); remediation prioritization triaged by traffic volume and exposure risk (14-21 days); page remediation re-engineering failed pages and integrating compliance review into the deployment pipeline (60-120 days); documentation infrastructure for version control of variants linked to audit artifacts (30-45 days); and buyer-network attestation preparing publisher-side documentation or requesting buyer-side documentation (30-45 days). Audit execution and page remediation are the critical-path items. Operators on legacy form-builder platforms with limited HTML/CSS control may need additional time to migrate to a more controllable rendering stack. --- ## Sources ### Tier 1: Primary Court and Regulatory Sources 1. *Dahdah v. Rocket Mortgage, LLC*, No. 24-1910 (6th Cir. Jan. 26, 2026), Justia case archive – https://law.justia.com/cases/federal/appellate-courts/ca6/24-1910/24-1910-2026-01-26.html 1a. CourtListener, *Dahdah v. Rocket Mortgage, LLC*, underlying district-court docket No. 4:22-cv-11863 (E.D. Mich.), accessed April 2026 – https://www.courtlistener.com/docket/64886850/dahdah-v-rocket-mortgage-llc/ 2. *Tablada v. Rocket Mortgage, LLC et al.*, No. 1:26-cv-00118 (D.R.I. filed Feb. 27, 2026), companion case; PACER Monitor docket page, accessed April 2026 – https://www.pacermonitor.com/public/case/63332471/Tablada_v_Rocket_Mortgage,_LLC_et_al 3. *Specht v. Netscape Communications Corp.*, 306 F.3d 17 (2d Cir. 2002) 4. *Berkson v. Gogo LLC*, 97 F. Supp. 3d 359 (E.D.N.Y. 2015) 5. *Sgouros v. TransUnion Corp.*, 817 F.3d 1029 (7th Cir. 2016) 6. *Meyer v. Uber Technologies, Inc.*, 868 F.3d 66 (2d Cir. 2017) 7. *Sellers v. JustAnswer LLC*, 73 Cal. App. 5th 444 (2021) 8. *Insurance Marketing Coalition v. FCC*, Eleventh Circuit decision vacating FCC's one-to-one consent rule (January 2025) 9. Federal Communications Commission, "Delete, Delete, Delete" Notice of Proposed Rulemaking (2026), comments pending as of April 2026 10. Telephone Consumer Protection Act, 47 U.S.C. Section 227 11. Federal Arbitration Act, 9 U.S.C. Sections 1 et seq. ### Tier 2: Trade Press Analyses of Dahdah 12. Global Arbitration News, "Sixth Circuit Clarifies Multi-Factor Analysis for When Online Proposals Create Binding Contracts with Arbitration Clauses," April 22, 2026 – https://www.globalarbitrationnews.com/2026/04/22/sixth-circuit-clarifies-multi-factor-analysis-for-when-online-proposals-create-binding-contracts-with-arbitration-clauses/ 13. Bubeck Law, "Designing Enforceable Opt-Ins: Lessons from Dahdah v. Rocket Mortgage," 2026 – https://www.bubecklaw.com/privacyspeak/designing-enforceable-opt-ins-lessons-from-dahdah-v-rocket-mortgage 14. Kelley Drye, "TCPA Tracker: March-April 2026," April 24, 2026 – https://www.kelleydrye.com/viewpoints/newsletters/tcpa-tracker/tcpa-tracker-march-april-2026 15. Today's General Counsel, "Sixth Circuit Sides with Rocket Mortgage on Online Arbitration Clauses," 2026 – https://todaysgeneralcounsel.com/sixth-circuit-sides-with-rocket-mortgage-on-online-arbitration-clauses/ ### Tier 3: Industry Practice and Compliance Guidance 16. Industry trade-press analyses of TCPA class-action filing volumes (approximately 1,800 federal class actions annually) and average settlement values (approximately $6.6 million for certified classes), composite of 2025-2026 publications 17. Web Content Accessibility Guidelines (WCAG) 2.1, contrast ratio standards (referenced as de facto baseline for visual-conspicuousness factor), W3C accessibility documentation 18. American Arbitration Association, Consumer Arbitration Rules and procedural framework as referenced in LowerMyBills.com terms of use (publicly available AAA rule text) ### Tier 4: Supporting Industry Commentary 19. Trade-press commentary on the FCC's "Delete, Delete, Delete" NPRM and the regulatory trajectory following the Eleventh Circuit's *Insurance Marketing Coalition* vacatur, composite of industry publications through April 2026 20. Compliance-tech vendor commentary on automated form-audit tooling and the projected emergence of continuous-monitoring services through 2027-2029 21. Affiliate-network and publisher contractual practice as documented in industry guidance on TCPA audit-artifact access provisions --- ## Closing *Dahdah* will be remembered for the wrong reason. The headlines treated it as a Sixth Circuit win for Rocket Mortgage on a narrow arbitration question. That framing misses what actually happened. The structural event was the elevation of web-form architecture to the load-bearing element of every TCPA defense, with a four-factor conspicuousness test that lower courts have already begun applying as a checklist. The operational event was the realignment of compliance, engineering, and marketing accountability around a form-audit discipline that most operators have not yet built. The economic event was the conversion of CSS specifications and pixel-level button placements into discoverable, citable, deposable litigation evidence. Lead-generation operators who treat *Dahdah* as a published case to read once will spend the next eighteen months running funnels designed for the pre-*Dahdah* environment into a litigation pipeline that is already calibrated to the new framework. Operators who treat it as a redesign trigger – auditing every active form, building the version-controlled documentation bundle, integrating compliance pre-screening into A/B testing, securing the buyer-side documentation chain – convert a doctrinal moment into a six-to-twelve-month structural defense advantage. The decision about which group to be in is being made in the next ninety days of audit work and the next one hundred and eighty days of remediation. The plaintiffs' bar is not waiting. The form is the evidence. The CSS is the defense. There is no comfortable third option, and [the difference between an individual arbitration and a certified class action](/blog/class-action-individual-tcpa-claims/) is now measured in pixels. --- *Court decisions, regulatory developments, and litigation pipeline observations reflect publicly reported conditions through April 28, 2026. Click-wrap doctrine, FCC rulemaking, and circuit-level applications of the Dahdah framework continue to develop; verify current case law and regulatory status through primary sources before making operational decisions. This article provides general industry analysis and does not constitute legal advice. Consult qualified counsel for specific compliance questions related to TCPA defenses, click-wrap form architecture, arbitration clause enforceability, and lead-generation buyer-network documentation requirements.*