Auditing consent and cancellation flows for the EU Digital Fairness Act
Nobody owns the distance between signup and cancellation, and that is the number the Digital Fairness Act conversation keeps coming back to. This walkthrough builds the measurement layer: a flow inventory generated from your route table, feature flags and live experiments, a CI gate that fails when a tagged flow has no evidence file, Playwright assertions for pre-selected add-ons and exit-path friction, and snapshot diffs so a friction regression arrives as a reviewable pull request. What the public record confirms is narrow. A Tech Times listing dated 9 November 2026 puts the act on Wednesday's schedule and frames it against dark patterns current platform rules miss. The operative definition, penalty ceilings, applicability thresholds and transition periods are unconfirmed, so this is preparatory engineering work, not a compliance opinion. The post covers the four flow families to enumerate, why GDPR Article 7 and DSA Article 25 do not own a checkout flow, deriving the inventory instead of hand-writing it, committing it as JSON, symmetry ratios, friction budgets across screens, clicks, fields and support contacts, and default and pre-selection checks. Full write-up: https://hackyjs.com/posts/auditing-consent-screens-and-cancellation-flows-for-the-eu-digital-fairness-act