In partnership with

LUXE PROMPTING

LUXE PRACTICAL WORKSHOP

Make Your Visuals Work Without the Image.

A graphic can clarify a message, but it should not be the only place the message exists. Readers may use assistive technology, enlarge text or encounter blocked images. Review your next newsletter visual by asking what remains useful when the picture is unavailable, then repair the missing meaning.

The daily newsletter for finding AI tools worth trying

New AI tools launch every day. A few will change how you work. The rest will be forgotten by next month.

TLDR AI is the free newsletter that tells you which is which. Every morning, Anthropic and ex-Google engineers pick the new tools, updates, and open source releases worth trying, with a quick note on what each one does and who it's for.

You find the good ones early, without testing all of them.

One email, 5 minutes a day, read by 1.1M+ people. Get tomorrow's picks.

The Short Version

  • Write alternatives for the image’s purpose in this specific context.
  • Keep important instructions, numbers and actions available as real text.
  • Check contrast and actual reading size, then review the page with images unavailable.

Describe the job the image does

W3C’s image decision tree distinguishes informative, decorative, functional and complex images. Those roles lead to different text alternatives. A linked logo, a chart and a decorative flourish should not all receive the same kind of description. Start with what the reader needs to understand or do, not an inventory of visible objects.

For example, a crop comparison might demonstrate that a face is lost in the narrow version. The useful explanation is that the smaller crop removes the subject, not simply that two photographs appear side by side. Nearby copy can carry the lesson, with concise alternative text helping identify the comparison.

1. Put essential information in the article

If a graphic contains a deadline, a price or a sequence of instructions, repeat that important information as readable text. For a complex chart, provide the main conclusion and relevant values nearby. This also makes revision easier: a correction should not require readers to decipher a replacement screenshot before they understand what changed.

2. Give linked images a clear destination

A picture used as a link needs to make the action understandable. Review the link label and surrounding sentence together. “View the sizing guide” tells someone where they are going; “image” does not. Avoid making a tiny icon the only route to a critical action. Keep the main next step visible even when the asset fails to load.

3. Test the words at their real size

W3C’s minimum-contrast guidance uses 4.5:1 for ordinary text, with 3:1 for qualifying large text and specific exceptions. Do not assume a pale brand color is readable because it looks refined in a large design canvas. Inspect captions, button labels and overlaid words at the size a phone reader will actually encounter.

4. Remove the image and follow the story

In a preview or local copy, hide images and read from the headline to the action. Can you still identify the promise, understand the essential steps and choose the next action? Then enlarge the text and check that the layout does not hide content. Keep this separate from a real screen-reader review, which can expose different problems.

Make the review easy to repeat

Use a small record with the asset name, its role, the nearby explanation and the chosen alternative text. Have a second person explain the visual’s lesson without seeing it. If their explanation differs from yours, revise the copy before spending time on decorative improvements.

This does not mean every image needs a long description. Redundant narration can create its own friction, especially for purely decorative assets. The useful standard is that the reader gets the information and controls they need. Make each image earn its place, and keep its essential contribution available beyond the pixels.

Source Desk

Primary documentation checked October 26, 2026. The practical workflow is Luxe editorial guidance, not a measured performance claim. These checks are not a full accessibility audit or certification of any email client. Recheck product details before use.

W3C WAI: An alt decision tree

W3C: Contrast minimum

A clearer brief. A more useful result.

Privacy policy