A disclosure that is present, accurate, and complete can still fail. That is the practical message running through 2026 enforcement posture, and it relocates a large part of compliance review from the words to the interface those words sit in.
The standard being applied is not new in its wording. For a disclosure to be clear and conspicuous it should be difficult to miss — unavoidable — and easy to understand. What has changed is how literally the first half of that is being read.
The shift: substantial effect over formal compliance
Regulators are increasingly assessing the substantial effect of a practice rather than whether it formally satisfied a requirement. Applied to disclosure, that means the question is no longer “was it disclosed” but “did the design permit a reasonable consumer to encounter and understand it.”
The clearest articulation of the trap is that technically accurate disclosures can still be deceptive if other statements or design choices mislead consumers. The disclosure does not have to be wrong. It has to be defeated by the things around it — a headline that overstates, a default that pre-selects, a layout that places the qualifier where attention has already moved on.
That is particularly acute in digital interfaces, marketing claims, and the abbreviated disclosures common in fintech products, where the space constraint that makes abbreviation necessary is the same constraint that makes it easy to bury.
The FTC has signalled that dark patterns remain a subject of scrutiny, investigation, and enforcement, with its Bureau of Consumer Protection’s Division of Financial Practices explicit on the point. Design choices are being treated as conduct.
Where marketing teams are actually exposed
The exposure is rarely in the legal copy, which has usually been reviewed. It is in the four decisions made after that review.
Placement relative to the claim. A rate, a fee, or a condition disclosed several screens below the headline that it qualifies is present but not proximate. Proximity to the claim being qualified is doing the work, not presence somewhere on the page.
Visual hierarchy. Type size, contrast, and weight determine whether a disclosure reads as information or as boilerplate. A qualifier set in light grey at eight points beneath a high-contrast call to action has been designed to be skipped, whether or not anyone intended that.
Interaction cost. Anything requiring an expand, a scroll past the action button, a hover, or a tap to reveal has been made avoidable by construction. If the consumer can complete the flow without ever encountering it, it is not unavoidable.
Defaults and friction asymmetry. Pre-selected options, an enrolment path that takes one tap against a cancellation path that takes five, and confirm-shaming copy on the decline option all fall squarely inside the dark-patterns frame. Product design is expected to be evaluated from the consumer’s perspective, identifying features that exploit behavioural biases, create unavoidable harm, or interfere with the ability to understand or control financial obligations.
What this changes in the review process
The operational consequence is that a copy-only compliance review is no longer sufficient, because the failure mode lives in artifacts the reviewer usually never sees.
Review the rendered screen, not the copy deck. Approval should attach to a screenshot of the actual composed interface at real device widths, not to a document containing the approved sentences.
Review mobile first and separately. A disclosure that sits beside a claim on desktop routinely lands three scrolls below it on a phone. Desktop approval does not transfer.
Include the flow, not only the page. Whether a disclosure is avoidable depends on the path. Reviewing pages in isolation cannot answer that.
Version-control the design, not just the text. A layout change made after legal sign-off can defeat an approved disclosure without altering a single word, and nothing in a text-based approval trail will catch it.
Ask the effect question directly. Would a reasonable consumer moving at normal speed encounter this before acting? That is closer to the standard being applied than any checklist of required elements.
The uncomfortable implication
This standard puts compliance and conversion optimisation in direct tension, because many of the techniques that raise conversion — reducing friction on the primary action, minimising competing visual elements, deferring detail — are the same techniques that make a disclosure practically invisible.
Teams that treat that tension as a design problem to be solved openly tend to end up with defensible interfaces. Teams that resolve it silently in favour of conversion, one A/B test at a time, accumulate exposure that no copy review will ever surface — because the copy was fine every time.
This is an editorial summary, not legal advice. Specific disclosure and design decisions should be reviewed with counsel.
