Learning path · Level 8 · Tutorial 2

Draft an Accessible Email Campaign

Draft an accessible email whose inbox preview, body, and call to action work together, and explain what must be checked before sending. Use a text-based draft or an optional Mailchimp editor where its current free tier permits; no domain setup or live send is required.

  • Level: Intermediate
  • Duration: 22 min
  • 9 steps
Start tutorial Back to the path
Draft an Accessible Email Campaign

What you will go through

  1. Define the Campaign Brief Define the audience, purpose, offer, and destination action before drafting the email. 2 min
  2. Align the Inbox Preview Create inbox elements that recognize the sender, accurately promise the offer, and remain meaningful when an inbox shortens the display. 2 min
  3. Build the Body Around One Action Build a concise, accessible email body that explains one offer and leads to one clear action. 3 min
  4. Keep Meaning Accessible Without Images Specify image treatments and readable link styling so the campaign remains understandable and actionable when images are unavailable. 3 min
  5. Review Mobile and Client Variations Review likely email rendering variations and separate observations from checks that remain unverified. 2 min
  6. Specify Sender and Footer Details Specify a coherent sender identity, a monitored reply path, and clear footer controls while preserving unresolved operational details for later verification. 2 min
  7. Understand Sender Authentication Distinguish SPF, DKIM, and DMARC roles and identify the domain-authentication checks that need administrator support. 3 min
  8. Separate Delivery from Inbox Placement Separate provider acceptance from inbox placement, then identify practices that can create avoidable sender-reputation risk. 2 min
  9. Complete the No-Send Preflight Finalize the accessible campaign draft with evidence-based preflight records, without sending it. 4 min

What you will learn

  • Write aligned sender-name, subject-line, preview-text, body, and call-to-action specifications for one eligible segment.
  • Structure the email so its message and action remain understandable on mobile devices and when images are blocked.
  • Explain the distinct roles of SPF, DKIM, and DMARC and identify when domain-administrator support is required.
  • Distinguish accepted delivery from inbox placement and identify practices that can damage sender reputation.
  • Complete a no-send preflight review, including destination links, preferences, unsubscribe access, and tool restrictions.

Before you start

  • Design a Permission-Based Email List
  • Write Benefit-Led Marketing Copy
  • Create Readable Marketing Visuals with Free Tools
  • Create Consistent UTM Campaign Links

Step 1 of 9

Define the Campaign Brief

Define the audience, purpose, offer, and destination action before drafting the email.

Connect the essential decisions

One campaign, one clear path

A one-time campaign brief is the decision sheet behind an email draft. It connects four choices:

  1. One eligible audience
  2. One message purpose
  3. One offer
  4. One destination action

Keeping these choices aligned prevents a campaign from promising one thing and asking recipients to do another. The brief guides later copy and layout decisions; it is not evidence that an email is ready to send.

A four-part flow from an eligible plant-care subscriber group to a focused message, a free guide, and one destination action.

A campaign brief creates one connected path: eligible audience → purpose → offer → destination action.

Use the scenario without inventing conditions

Scenario facts for Northstar Plants

Use the supplied scenario facts exactly. The audience is active, permission-based subscribers who selected indoor plant care and are not suppressed.

The offer is the free online Small-Space Plant Care Guide. It covers choosing a spot, watering basics, and checking drainage. It requires no purchase or registration and has no deadline.

The intended destination action is to read the guide. The supplied destination is:
https://northstarplants.example/plant-care-guide?utm_source=newsletter&utm_medium=email&utm_campaign=plant_care_guide

Do not add a discount, urgency, a signup requirement, or another campaign goal.

Example

Example: a compact campaign brief

Campaign brief

Audience: Active, permission-based subscribers who selected indoor plant care and are not suppressed.

Message purpose: Invite eligible subscribers to use a practical small-space plant-care resource.

Offer: The free online Small-Space Plant Care Guide, covering choosing a spot, watering basics, and checking drainage. No purchase, registration, or deadline applies.

Destination action: Read the plant care guide at the supplied tracked guide URL.

This is a draft specification for later copy, structure, destinations, and operational checks. It does not prove that the address, link, or any sending setup is ready for use.

Tip

Practice boundary

Create the brief in a local text document. You may also enter it into an optional Mailchimp draft only if your current account permissions and free-tier features allow it. Do not add contacts, configure a domain, schedule, or send an email for this activity.

Practice: specify one clear campaign

Write the campaign brief

Using the supplied Northstar Plants scenario, write a compact Campaign brief with these four labeled parts: Audience, Message purpose, Offer, and Destination action.

Use one eligible audience and one destination action. Keep the offer accurate, and do not invent conditions or additional goals.

Write at least 180 characters (0/180).

Step 2 of 9

Align the Inbox Preview

Create inbox elements that recognize the sender, accurately promise the offer, and remain meaningful when an inbox shortens the display.

Give the inbox preview one clear promise

Three elements, three jobs

Inbox previews answer three quick questions before the email is opened:

  • Sender name: Who is this from?
  • Subject line: What is this email promising?
  • Preview text: What useful detail adds context?

These elements work as a set. For this campaign, they should consistently introduce the free guide for active, permission-based subscribers interested in indoor plant care.

How an inbox preview is read

A simplified inbox row with separate highlighted areas for the sender, subject, and preview snippet.

The sender name supports recognition; the subject and preview text set expectations together.

Example

Aligned campaign specification

Sender name: Northstar Plants
Subject line: Free Small-Space Plant Care Guide
Preview text: Choose a spot, water with confidence, and check drainage.

The subject names the offer early. The preview text adds the guide’s topics instead of repeating the subject. Neither suggests a purchase, registration, deadline, or benefit that the guide does not provide.

Make the first words count

Plan for shortened displays

Inbox apps may shorten the subject line or preview text differently on each device, client, and setting. There is no character count that guarantees the full copy will show.

Put the meaningful words first. Write preview text deliberately so an accidental opening line, “view in browser” message, or footer language does not become the snippet.

Keep expectations honest: do not add a misleading reply prefix, false urgency, or personalization that the campaign does not actually have.

Tip

A useful clipping check

Use this quick review before drafting:

  • Can a recipient recognize the sender?
  • Does the subject accurately name the email’s main offer?
  • Does the preview text contribute a helpful detail rather than echoing the subject?
  • Would the beginning of each line still make sense if the rest were clipped?

A shortened display can hide detail, but it should not turn a clear offer into a vague or misleading one.

Check the roles

Match the inbox roles

Match each inbox element to its primary job.

Tap an item and then its matching pair.

Apply the inbox-preview rules

Draft an aligned inbox preview

Using the campaign scenario from the earlier screens, create an inbox-preview specification.

First, state the primary job of each of the three inbox elements in a short phrase. Then write labeled values for Sender name, Subject line, and Preview text.

Your draft must describe the same guide offer, make the sender recognizable, and place the essential offer meaning near the start of the subject and preview text so the set remains clear when shortened.

Write at least 120 characters (0/120).

Step 3 of 9

Build the Body Around One Action

Build a concise, accessible email body that explains one offer and leads to one clear action.

Create a logical reading path

One reader path, one campaign action

A promotional email body should lead a reader through one clear path: understand the offer, see the useful details, then take one action. A single-column structure makes that path easier to scan on a narrow screen.

Use live text for the heading, benefit, details, and CTA. Do not put essential words inside a decorative image. Where your editor provides structural heading and list formatting, use it instead of relying only on larger type, bold styling, or all caps.

A mobile email wireframe with a heading area, a short benefit statement, a bulleted details area, and one prominent CTA button arranged from top to bottom.

The reading order is: main heading, brief benefit, essential details, then the primary CTA.

Tip

Focus does not remove operational links

Keep the offer focused. A necessary footer or preference link can appear later in the email, but it does not need to compete with the one promotional CTA in the body.

Turn the offer into a concise body

Write live-text blocks that match the offer

The body must fulfill the promise made in the inbox. For this campaign, explain that the guide is free, what it covers, and what the reader can do next. Do not add a discount, a signup requirement, a deadline, or a second campaign goal.

A button-style CTA should be a real text link. Its words should describe the action or destination, rather than using vague wording such as “Click here.”

Example

Example: body specification

Body

Small-Space Plant Care Guide

Make a confident start with indoor plants in a small space.

This free online guide covers:

  • Choosing a spot
  • Watering basics
  • Checking drainage

No purchase, registration, or deadline.

Primary CTA

Read the plant care guide

Destination: https://northstarplants.example/plant-care-guide?utm_source=newsletter&utm_medium=email&utm_campaign=plant_care_guide

Practice the reading sequence

Sequence the body blocks

Arrange these body blocks in the most logical reading order for a reader encountering the campaign for the first time.

  1. List the guide’s essential topics
  2. Give one benefit of using the guide
  3. Place the guide-focused primary CTA
  4. State the guide in a clear main heading

Apply the body structure

Draft the body around one action

Draft a four-block email body for Northstar Plants. Put the blocks in the reading sequence you chose: a main heading, a brief benefit statement, essential guide details, and a descriptive primary CTA.

Use the supplied offer facts. Keep the message focused on the promised free guide, and make the CTA lead to that guide rather than to a competing action.

Write at least 80 characters (0/80).

Step 4 of 9

Keep Meaning Accessible Without Images

Specify image treatments and readable link styling so the campaign remains understandable and actionable when images are unavailable.

Make images optional to understanding

Give every image a job

Images can support this campaign, but they must not carry its only promise or action. Keep the guide’s purpose, its key topics, and the Primary CTA as live text in the Body. If images are blocked, a subscriber should still understand the offer and be able to act.

Use the Image alternatives field to record each image’s purpose. An informative image needs a short alternative that communicates why it is there in this email. A purely decorative flourish should be marked decorative, or given an empty alternative where the editor supports that treatment. Avoid filenames and avoid repeating nearby copy that already says the same thing.

When images are unavailable

Two versions of the same mobile email, one with a plant photo and one with the image blocked, while the text and action remain visible in both.

The image may add context, but the offer and action must survive without it.

Image treatment decisions

Choose treatment based on what the image contributes in context.

Record these choices in the draft’s `Image alternatives` field.
Email elementAppropriate treatment
Photo supporting drainage adviceBrief alternative that communicates the photo’s purpose
Leaf flourish between sectionsMark decorative or use an empty alternative where supported
Linked guide-cover imageGive the link an accessible name that states its action or destination

Keep links and controls usable

Specify readable styling

Do not rely on color, an icon, or a background image alone to communicate meaning. Make text links recognizable beyond color, such as with an underline, and keep the Primary CTA as a real text link rather than words inside an image.

Use readable text sizing, for example 16 px, and aim for sufficient contrast, such as 4.5:1 for normal text. Make tap targets generous and separated, for example 44 × 44 px. These are useful design targets, not proof that a particular email passes accessibility testing.

Tip

Choose the simpler accessible option

A text-only design is valid. If an optional editor cannot provide an accessible image treatment or a usable control, remove the nonessential image or use a simpler text-based layout. Do not assume an attractive preview is accessible.

If you practice with an image in your own editor, use your own file. Tutorial illustrations demonstrate the intended meaning and layout only; they are not campaign assets.

Draft styling notes

Add concise implementation notes to the draft rather than relying on appearance alone.

Example specifications for the Northstar Plants draft.
CheckDraft specification
Offer and guide topicsLive text in Body
Primary CTAReal text link with a descriptive label
Text linksRecognizable beyond color alone
Normal body textReadable size, for example 16 px
Touch controlsGenerous spacing and target, for example 44 × 44 px
Text contrastAim for sufficient contrast, such as 4.5:1

Practice: classify image roles

Choose the image treatment

Match each email element to its most appropriate accessibility treatment.

Tap an item and then its matching pair.

Apply the decisions to Northstar Plants

Annotate the accessible draft

In your local campaign draft, add an Image alternatives section and a short implementation note for this scenario: the email uses a photo that supports choosing a plant spot, a leaf divider between sections, and a linked guide-cover image near the Primary CTA.

Write three lines—one for each image—with the treatment and concise wording or accessible name you would specify. Then add one line under Body or Primary CTA explaining how the message and action remain usable when images are blocked. Use the existing CTA wording from your draft; do not write HTML.

Write at least 180 characters (0/180).

Step 5 of 9

Review Mobile and Client Variations

Review likely email rendering variations and separate observations from checks that remain unverified.

Expect variation, not one fixed display

One draft, different renderings

A single email draft can look different across email clients, screen widths, color modes, and image settings. Text may wrap differently; spacing and buttons may change; images may not load; and dark mode can alter color contrast.

Review a draft in more than one condition, but treat every preview as evidence about that condition—not proof that every recipient will see the same result.

Rendering can vary by context

Three versions of one plant-guide email: a narrow phone layout, an images-blocked layout that still shows text and a CTA, and a dark-mode layout.

Check the message under conditions that can change wrapping, image visibility, and color appearance.

Tip

Review mindset

Do not assume that a tutorial mockup or one editor preview proves universal compatibility. It illustrates a likely condition only.

Inspect what is visible—and name what is not

Two useful draft reviews

Use a narrow-screen review to look for a readable single-column flow, sensible text wrapping, visible live text, a usable CTA, and no awkward horizontal navigation.

Then review with images blocked. The offer, essential details, and CTA should still make sense and remain available. A text-only walkthrough can catch missing or contradictory specifications, but it cannot verify final markup or rendering.

What each review can establish

A visual preview can support a limited set of observations. If a needed check cannot be performed in the available editor or environment, record it as Unverified rather than assuming it passed.

Use evidence from the review you actually performed.
CheckWhat you can inspectIf not available
Narrow screenReading order, wrapping, visible text, CTA appearanceUnverified
Images blockedMessage and CTA remain understandableUnverified
Visual previewSpacing, obvious overflow, color appearanceUnverified
Keyboard or assistive technologyFocus behavior and announced contentUnverified

Example

Preview boundary

For example, an editor preview can show that a CTA is visible on a phone-sized canvas. It cannot, by itself, establish that keyboard focus reaches the CTA in a sensible order or that assistive technology announces it as intended.

Apply the review boundary

Diagnose the review result

A 320 px-wide visual preview of the Northstar Plants email has a horizontal scroll bar. Its opening message appears only inside a large header image. When images are blocked, the preview shows a blank rectangle, and neither the guide offer nor the CTA is available.

In three short sentences: identify one problem, propose one draft correction, and name one check that this visual preview alone cannot establish. State how you would record that unavailable check.

Write at least 120 characters (0/120).

Step 6 of 9

Specify Sender and Footer Details

Specify a coherent sender identity, a monitored reply path, and clear footer controls while preserving unresolved operational details for later verification.

Define the sender identity

Keep sender fields distinct

The inbox identity fields serve different purposes:

  • Sender name is the recognizable name recipients see.
  • From address is the address shown as the sender.
  • Reply-to is where a recipient’s reply is directed.

They should form a coherent identity, but they are separate fields. For this draft, use Northstar Plants as the Sender name and hello@northstarplants.example for both the From address and Reply-to.

The .example addresses are scenario placeholders, not verified sending identities. Before real use, the actual Reply-to must reach a mailbox that someone monitors; a no-reply address prevents a recipient from responding normally.

Sender identity and recipient controls

A diagram separates sender name, From address, and Reply-to fields at the top of an email from identity, contact, preferences, and unsubscribe controls in the footer.

Treat sender fields and footer controls as separate specifications, even when they appear in the same email.

Specify footer content without inventing details

Make the footer usable

The Footer identifies the sender and provides operational controls. Include clear sender identification and applicable contact details, including a valid postal address when required by law or the provider.

Recipients must be able to find and understand both preference management and a direct way to stop marketing email. A preference center can offer choices, but it must not hide or replace a clearly labeled unsubscribe option.

Do not treat a link that merely looks correct as complete. Before a real send, the email tool must generate or resolve the preference and unsubscribe links, and the unsubscribe process must honor the request without requiring an account sign-in or another authentication barrier.

Providers can impose additional footer, sender, or unsubscribe requirements. Applicable rules vary by provider and jurisdiction; this draft is not a legal-compliance determination.

Example

Draft specification example

Sender name: Northstar Plants
From address: hello@northstarplants.example
Reply-to: hello@northstarplants.example

Footer:
Northstar Plants
[Sender postal address]
Manage email preferences: [Preference center link]
Unsubscribe from marketing email: [Unsubscribe link]

The bracketed entries are intentionally unresolved operational details, not final customer-facing copy. Keep them visible until the actual postal address and tool-generated or verified destinations are available.

Practice: find the required control

Check the footer

Which footer control should appear alongside a preference-management link?

Apply: repair the sender and footer specification

Revise the incomplete draft

Review this incomplete specification. Rewrite the sender and Footer fields as a suitable no-send draft. Keep supplied information that is appropriate, correct misleading or incomplete entries, and leave unknown operational values visibly unresolved in square brackets. Then name one check that must remain unresolved before real use.

Sender name: Plant Deals
From address: hello@northstarplants.example
Reply-to: no-reply@northstarplants.example
Footer: Northstar Plants — Manage settings

Do not invent a postal address or live link destination.

Write at least 180 characters (0/180).

Step 7 of 9

Understand Sender Authentication

Distinguish SPF, DKIM, and DMARC roles and identify the domain-authentication checks that need administrator support.

Separate the domain roles

Three domains in one email

Authentication uses three related—but not interchangeable—domains. The visible From domain is what recipients see in the From address. In this scenario, the visible From domain is northstarplants.example.

The envelope sender domain works behind the scenes for mail handling. The DKIM signing domain is associated with the message signature. A sending platform may use domains that differ from the visible From domain, so check each role by name rather than assuming they are identical.

Where the domains appear

Diagram showing a sending platform delivering an email to a recipient, with separate callouts for the visible From domain, envelope sender domain, and DKIM signing domain.

These domains can be related without being the same domain.

Tip

Key distinction

Do not equate a recognizable From address with complete authentication. Each mechanism checks a different part of the sending and identity process.

Compare SPF, DKIM, and DMARC

Three mechanisms, three jobs

Use this comparison to keep the mechanisms distinct. These are roles, not a guide to creating DNS records.

Authentication roles in an email campaign
MechanismPrimary questionDomain involvedWhat it does not establish
SPFIs this sending system authorized?Envelope sender domainThat the visible From address is authenticated by itself
DKIMHas signed content remained unchanged?DKIM signing domainEncryption of the email content
DMARCDoes visible From align with passing SPF or DKIM?Visible From domain plus an authenticated domainGuaranteed receiver action or inbox placement

Read the comparison

SPF publishes which sending systems may send for the envelope sender domain.

DKIM adds a cryptographic signature associated with a signing domain. A receiver can verify that the signed content was not changed after signing. DKIM signing is not encryption.

DMARC evaluates whether the visible From domain aligns with a domain that passed SPF or DKIM. One passing, aligned mechanism can satisfy DMARC; both mechanisms are not required.

Interpret outcomes and ownership

Alignment is the DMARC test

DMARC can publish requested handling for authentication failures and support reporting. That does not force every receiver to act the same way, and it does not guarantee inbox placement.

For example, DMARC can pass when SPF passes and its authenticated domain aligns with the visible From domain—even if DKIM does not pass or does not align. The same principle applies when DKIM is the one passing, aligned mechanism.

Warning

Know when to involve an administrator

If a platform requests domain-authentication setup or a change to existing DNS, do not guess at values or overwrite records. Ask an authorized domain administrator to handle or approve the change and confirm the platform's instructions.

A marketer can document the platform request and request verification. Authentication still needs confirmation before a real send.

Apply the authentication rules

Authentication check

Match each authentication concept or situation to its correct role or next action.

Tap an item and then its matching pair.

Step 8 of 9

Separate Delivery from Inbox Placement

Separate provider acceptance from inbox placement, then identify practices that can create avoidable sender-reputation risk.

Acceptance and placement are different checks

Acceptance is not inbox placement

A receiving provider can accept an email without placing it in the inbox. Acceptance means the provider took responsibility for the message; it does not prove placement in the inbox, a particular inbox tab, or that a recipient read it.

Think of acceptance as one checkpoint, not the campaign outcome. Placement can still be affected by filtering decisions, recipient preferences, message relevance, and the sender’s reputation.

One accepted email, several possible placements

A diagram shows an email passing a receiving-provider checkpoint and then branching toward different mailbox locations.

Provider acceptance occurs before a provider’s later placement decision.

Protect reputation through relevant, consistent sending

Authentication helps; it does not guarantee

Authentication helps receivers assess domain identity, but it does not override every later decision. SPF authorizes sending systems for the envelope sender domain; DKIM signs content with a signing domain; DMARC evaluates alignment with the visible From domain. These checks can support trust, but they do not guarantee inbox placement.

There is no universal subject-word trick, formatting formula, or authentication badge that guarantees an inbox result. Keep the Northstar Plants message relevant to its eligible indoor-plant-care segment, use an accurate identity and promise, and follow existing suppression and opt-out rules.

Reputation-supporting choices

Avoidable practices can weaken a sender’s reputation. Use the campaign brief and eligibility rules to prevent these risks before a send.

Risk patterns and safer responses
Risk patternWhy it can harm trustSafer response
Recipient complaintsSignals unwanted or misleading mailSend relevant email only to eligible, permission-based subscribers
Poor list qualityMore unwanted or unreliable recipientsKeep the defined active segment; do not add questionable contacts
Misleading identity or promiseCreates a mismatch between expectation and contentUse a recognizable sender and accurate subject, preview text, and body
Ignored opt-outsDisregards recipient preferencesHonor suppression and unsubscribe requests
Abrupt unexplained volume changeCan look inconsistent or suspiciousUse a deliberate, consistent sending approach

Practice: correct an overclaim

Check the claim

True or false: If a receiving provider accepts an email and authentication passes, the sender can conclude that the email is guaranteed to appear in the recipient’s inbox.

Choose the best answer.

Practice: choose the safer response

Practice: respond to a reputation risk

A teammate proposes adding a large batch of unverified addresses to Northstar Plants’ usual campaign audience so the guide reaches more people. What is the most appropriate response?

Step 9 of 9

Complete the No-Send Preflight

Finalize the accessible campaign draft with evidence-based preflight records, without sending it.

Consolidate the specification

Assemble one no-send draft

A no-send preflight turns the specifications you created into one reviewable local draft. It does not prove that an email platform can send the email.

Copy the assembled draft into a local document using the required field labels. Keep unresolved operational details in square brackets. Treat every fictional .example address and URL as a scenario reference, not as a verified sending identity or live destination.

The goal is to separate what the draft already specifies well from what must be corrected or verified before real use. Keep the campaign unscheduled and unsent.

From draft to preflight record

A structured email draft flows into a checklist that reviews its inbox details, body, CTA, image treatment, and footer.

Review the whole specification together; a visually complete draft is not evidence that its operational parts work.

Example

Example: consolidated draft specification

Campaign brief: Audience: Active, permission-based subscribers who selected indoor plant care and are not suppressed. Message purpose: Invite eligible subscribers to use a practical small-space plant-care resource. Offer: The free online Small-Space Plant Care Guide, covering choosing a spot, watering basics, and checking drainage. No purchase, registration, or deadline applies. Destination action: Read the plant care guide.

Sender name: Northstar Plants
From address: hello@northstarplants.example
Reply-to: hello@northstarplants.example
Subject line: Free Small-Space Plant Care Guide
Preview text: Choose a spot, water with confidence, and check drainage.

Body: Small-Space Plant Care Guide
Make a confident start with indoor plants in a small space.
This free online guide covers choosing a spot, watering basics, and checking drainage. No purchase, registration, or deadline.

Primary CTA: Read the plant care guide
Destination: https://northstarplants.example/plant-care-guide?utm_source=newsletter&utm_medium=email&utm_campaign=plant_care_guide

Image alternatives: Any informative image has a concise alternative; essential offer copy and the CTA remain live text.

Footer: Northstar Plants
[Sender postal address]
Manage email preferences: [Preference center link]
Unsubscribe from marketing email: [Unsubscribe link]

Record what the draft can and cannot prove

Make statuses evidence-based

Use one status for each check:

  • Pass — available evidence supports the requirement at the draft-specification level.
  • Revise — a known draft issue must be corrected.
  • Unverified — the scenario, tool, or available evidence cannot establish the result.

A Pass is not a production approval. In particular, unverified authentication, operational links, or required sender details block a real send. Record evidence for Pass and a concrete next action for Revise or Unverified.

Example preflight records

This example separates copy, accessibility, operational, and tool checks. It documents a usable draft while preserving the boundaries of the fictional scenario.

Check | Status | Evidence or next action
CheckStatusEvidence or next action
Recipient eligibilityPassActive permission-based indoor-plant-care subscribers; not suppressed.
Offer and CTA accuracyPassFree guide, no purchase, registration, or deadline; CTA matches the stated guide.
Accessible structurePassSpecification calls for live text, logical single-column order, image alternatives, and a descriptive CTA.
Destination linkUnverifiedTracked URL is recorded; test resolution, redirects, and destination content in real use.
Sender and authenticationUnverified`.example` identity is fictional; an authorized administrator must verify sender setup and SPF, DKIM, and DMARC.
Footer controlsReviseReplace bracketed postal address and link placeholders; verify preference and unsubscribe access before real use.
Current tool restrictionsUnverifiedCheck the current plan for available previews, authentication options, footer controls, contact limits, and sending allowances.

Apply the preflight to the draft

Final application: write the preflight

Now review your own locally assembled Northstar Plants draft. Do not send, schedule, activate, or try to configure a domain. Use only evidence available in the draft and scenario. When a real-world check cannot be performed here, record the check as Unverified and state the next action rather than assuming it passed.

Submit your no-send preflight

Create seven separate checklist records for: recipient eligibility; offer and CTA accuracy; accessible structure; destination link; sender and authentication; footer controls, including preference and unsubscribe access; and current tool restrictions.

Use the exact format Check | Status | Evidence or next action for every record. Use only the statuses Pass, Revise, or Unverified.

Then add a 2–3 sentence readiness statement explaining what is complete, what must be corrected or verified, and why the draft must remain unsent. Your statement must recognize that the fictional .example identities and any unverified operational checks prevent a real send.

Write at least 550 characters (0/550).

Close the no-send review

Summary

No-send preflight recap

  • A no-send draft can align the Campaign brief, inbox preview, Body, Primary CTA, Image alternatives, sender identity, and Footer without proving live functionality.
  • Use Pass for supported draft evidence, Revise for known corrections, and Unverified for checks the scenario or tool cannot establish.
  • The tracked destination still needs real-world checks for resolution, redirects, and matching destination content.
  • Fictional .example identities, unverified SPF, DKIM, or DMARC, unresolved Footer details, and untested preference or unsubscribe behavior block a real send.
  • Check current tool restrictions rather than assuming a free plan provides required features. Keep the campaign unscheduled and unsent until blockers are resolved.

Tutorial complete

Congratulations! You completed: Draft an Accessible Email Campaign

You completed an accessible email campaign draft and documented what is ready, what needs revision, and what remains unverified before real use.

Download the App now to have access to + 5000 free courses, exercises, certificates and lots of content without paying anything!

  • 100% free online courses from start to finish

    Thousands of online courses in video, ebooks and audiobooks.

  • More than 60 thousand free exercises

    To test your knowledge during online courses

  • Valid free Digital Certificate with QR Code

    Generated directly from your cell phone's photo gallery and sent to your email

Cursa app on the ebook screen, the video course screen and the course exercises screen, plus the course completion certificate