{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-design-reference-acceptance-test","id":"email-design-reference-acceptance-test","slug":"email-design-reference-acceptance-test","title":"Test a Design Reference Before an Email Agent Reuses It","description":"Score provenance, recency, accessibility, channel fit, and prohibited elements before saving an email or image as reusable design direction.","dek":"A reference is an input to future work, not proof that its layout, claims, assets, or accessibility should be copied.","category":"Email Marketing","topics":["Migma","email design","design references","AI governance"],"author":"Marketing Wiki Research Automation","reviewer":null,"publishedAt":"2026-09-06","updatedAt":"2026-09-14","lastVerifiedAt":"2026-09-14","readingMinutes":4,"featured":false,"sources":[{"title":"Migma: Connected Agents Keep Your Brand on Track","url":"https://docs.migma.ai/changelog/2026-09-05?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test"},{"title":"Migma: Brand Setup","url":"https://docs.migma.ai/get-started/configure-brand?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test"},{"title":"Migma: Visual Canvas","url":"https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test"},{"title":"W3C: Web Content Accessibility Guidelines 2.2","url":"https://www.w3.org/TR/WCAG22/?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test"}],"wordCount":649,"body":"Save a design reference only after it passes a reusable-input test. Judge provenance, date, purpose, accessibility, channel fit, and prohibited elements separately; “the team likes it” is not an acceptance criterion.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Sources were refreshed on September 6, 2026.\n\nMigma's [September 5 changelog](https://docs.migma.ai/changelog/2026-09-05?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test) says a connected agent can star an existing email or store a pasted design for future use. The [brand setup guide](https://docs.migma.ai/get-started/configure-brand?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test) says references guide design without copying words, and the [Visual Canvas guide](https://docs.migma.ai/creating-emails/visual-canvas?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test) lists HTML, screenshots, images, saved emails, and competitor emails as reference forms.\n\nThat flexibility makes admission control important. A reusable library amplifies both good systems and hidden defects.\n\n## Score the candidate\n\n| Dimension | Pass evidence | Reject or restrict when |\n| --- | --- | --- |\n| Provenance | Owner, source URL or campaign ID, capture date | Origin or right to reuse is unknown |\n| Purpose | Named pattern such as hierarchy, spacing, or product grid | “Make everything like this” |\n| Recency | Current brand and campaign context | Old offer, logo, footer, or product state |\n| Accessibility | Reading order, meaningful text, alt-text plan, contrast review | Image-only meaning or decorative text dominates |\n| Email fit | Received HTML or tested source, narrow-screen behavior known | Website screenshot assumes unsupported interaction |\n| Copy boundary | Explicit instruction not to reuse claims, price, or legal text | Reference is likely to leak obsolete wording |\n| Brand scope | One named brand, region, and message class | Cross-client or cross-market scope is implicit |\n\nUse [WCAG 2.2](https://www.w3.org/TR/WCAG22/?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-design-reference-acceptance-test) as a general accessibility baseline, then add email-client and received-message tests. A visually attractive source can still fail reading order, text resizing, link identification, or non-text alternatives.\n\n## Describe what to learn\n\nConvert taste into bounded attributes:\n\n- hierarchy: one headline, short support line, one primary CTA;\n- rhythm: alternating image and text sections with predictable spacing;\n- component: two-product comparison card, not the source products;\n- image treatment: subject isolated on a quiet background;\n- mobile rule: stack image before copy and preserve reading order.\n\nAlso state what must not transfer: logos, product photography, trademarks, claims, prices, testimonials, tracking links, personal data, and legal footers. The [competitor-remix review](/articles/competitor-email-remix-review) provides a narrower campaign-level check; maintain the reusable reference-rights record beside this library entry.\n\n## Run an influence test\n\nCreate one neutral fixture brief that contains no visual hints beyond the reference. Generate a controlled draft and inspect:\n\n1. whether the intended pattern appears;\n2. whether prohibited words or assets appear;\n3. whether the output remains editable;\n4. whether narrow-screen reading order still makes sense;\n5. whether the result passes preflight and a received-message test;\n6. whether removing the reference materially changes the intended attribute.\n\nThe final comparison isolates the reference's influence. Without it, reviewers may credit the reference for behavior caused by the prompt or brand kit.\n\n## Store a reference card\n\n```yaml\nreference_id: \"ref-newsletter-grid-03\"\nsource_type: \"received-html\"\nsource_owner: \"named internal campaign\"\ncaptured_at: \"2026-09-06\"\nlearn: [\"section rhythm\", \"single primary CTA\"]\nnever_reuse: [\"copy\", \"images\", \"prices\", \"legal footer\"]\nbrand_scope: \"example-retail\"\nmessage_scope: [\"newsletter\"]\naccessibility_review: \"passed with noted fixes\"\nrights_status: \"internal-owned\"\nreview_on: \"2026-12-01\"\n```\n\nExpire or revalidate the card when the brand system, footer, design tokens, product line, or accessibility baseline changes. Delete or quarantine it if ownership becomes uncertain.\n\n## Stop conditions\n\nDo not save a reference when its source is private customer material without authorization, its licensing is unclear, it contains personal data, its core pattern depends on inaccessible image text, or reviewers cannot name the exact characteristic worth preserving.\n\n## Evidence limits\n\nMarketing Wiki did not save or delete a reference in Migma and did not measure similarity between a reference and generated output. Product documentation supports the available reference types, not a legal conclusion about reuse or an accessibility guarantee."}