An HTML email template that remains readable in different mail clients
Test email content, images, dark mode and long values in agreed mail clients and reading conditions.
Article language: English

In this article
'It looks fine to me' is a particularly short email acceptance report. The author sees a preview in a browser. The recipient sees an empty rectangle where instructions should be, dark text on a dark background and a button two letters wide. Both are looking at the same message. Only one received the presentation version.
Imagine a fictional workshop that services instruments. It sends a technician visit confirmation, short room-preparation instructions and a link to details. HTML, the structure of the message, does not guarantee identical appearance. Well-organised content can become unreadable in the recipient's mail client. Test the template with long names and missing illustrations.
The scope of Aeneia Design's visual communication work can be discussed using such real messages and reading conditions. Ordering a rectangle with a logo and an example sentence is not enough. The sent material must accommodate instructions, a time and room name, and the recipient should be able to use it on their screen.
A message needs its own design version
A website header may have an elaborate background, a special font and behaviour dependent on screen width. Copying its code into email does not establish that those elements work in mail. First decide what must remain meaningful without decoration: sender name, purpose of the visit, date, instructions and an accessible link.
Gmail's CSS documentation lists supported selectors, properties and queries including screen width. It notes that unsupported rules may be ignored. One provider's list is a reference for that service, not a guarantee of the same result in other clients.
For the workshop's first acceptance, the team might choose the specific Outlook version used by staff, Gmail in a browser and the mail app on the approver's phone. This starts an agreed test list. If the company's customers use other tools, adapt it. The word 'Outlook' alone does not identify the version or reading conditions.
Also agree which differences are acceptable. A slightly different paragraph gap may be fine. A cut-off appointment time or a button missing the end of its label is not. These conditions focus discussion on consequences for the reader rather than disputes over every pixel of a screenshot.
The WooCommerce HTML email guide notes that mail clients display messages differently and recommends testing, simpler layouts and care with CSS support. Choose a concrete implementation for the sending system and agreed acceptance scope.
Do not promise 'compatibility with every mail client' from a single mock-up. State the clients, versions, widths and states to be checked within the agreed scope. The recipient then knows what was actually assessed. A later change of client or message-generation method may justify another trial.
Include reading the message with a screen reader. The tester should be able to associate the appointment time with the right room while navigating text and links. Bold styling alone will not explain relationships if names and values are separated in an unexpected order. In the agreed screen-reader trial, check link names and the route to the instructions. 'Readable message' needs that meaning too, not just a good-looking preview image.
The purpose should remain clear when images are off
In the first confirmation, the workshop placed the time and address on a beautiful panel with an instrument photograph. Without the image, only a greeting remained. The recipient does not need a better photograph now. They need ordinary text with the information for preparing the room and admitting the technician.
Microsoft's Outlook for Mac guidance says internet-stored images are not automatically downloaded by default, distinguishing them from attached or embedded images. Do not transfer that description to every Outlook variant without checking.
Keep the date and time as text. An illustration may show the right entrance, but the address and directions to the room should remain understandable if it does not load. If an image conveys information unavailable elsewhere, provide an appropriate description and check how it is presented in the agreed client.
Do not put the entire message paragraph into every image description. A logo needs an identifiable sender label; decoration may contribute no separate information. A photograph of a side entrance has a different purpose. These are different jobs even when all elements arrive as image files from a library.
The button for visit details should retain readable text and a working link without the graphic. If designed as an image containing words, test without the image. The recipient should not have to press an empty box hoping it has something to do with their case.
Check the images again after they load. A photograph should not widen the whole message beyond the available screen or change reading order. Also test an invalid image address. Readers must be able to distinguish a missing illustration from a missing time or instruction. Visual emptiness should not remove the action they need.
Use approved versions from the logo package (in Polish) for brand marks. Guidance on a small symbol and app icon (in Polish) illustrates limits on detail, but a favicon does not replace the correct logo version in a message. Different uses require different files.

A dark mail interface does not always mean the same message background
Test in light and dark surroundings. Pay particular attention to marks with transparent areas, button labels and regions intended to stay light. Do not adjust only text colour if a remaining background or image still makes the pair unreadable.
Microsoft's Outlook dark-mode help distinguishes client versions and describes switching the background of a message being read. The interface setting and the way the content itself appears are therefore not one inseparable choice. Record what was actually viewed in the test.
In the workshop's message, a dark instrument outline may disappear on a changed dark background while the heading remains readable. Conversely, a logo on its own light rectangle may become a heavy patch in an otherwise calm layout. Check both and choose an approved solution before distributing the file as a finished template.
Do not require recipients to change their client settings to read the appointment time. The design should work under agreed conditions. 'Switch the background to white' may help diagnosis, but it does not replace fixing an unreadable combination when that state is in the agreed scope.
Website dark-mode design (in Polish) also assesses particular surface-content pairs. Email adds the recipient's client as an influence. A website's own palette switch does not control their mail. Do not transfer a website test result directly into the message acceptance report.
Check links within paragraphs too. They should remain recognisable after colours change, retaining their text and another distinction where colour alone could fail. The recipient should find room-preparation details without probing every sentence with a pointer. Following the link should lead to those details.
Fallback fonts and long data are part of the design
A mail client may not use the company font. Prepare a fallback stack and assess the entire message with it. A longer line can move a button or increase section height. If the design fits only in one specific font, the fallback still needs design work.
In the example, enter 'Maria Szymanowska Chamber Room - entrance from the courtyard'. This reveals more than 'Room A'. Add a long contact address and a full appointment time including the weekday. Check wrapping, spacing and whether any information lies outside the visible area.
Premium website typography (in Polish) is a starting point for hierarchy and type choice. But the message needs its own layout acceptance. Heading, appointment and preparation instructions may need different proportions from a wide website section. Brand resemblance can remain without copying dimensions.
A message with two appointments reveals whether the layout preserves the right order on a narrow screen. If data were in columns, each date should still belong to the right time and room after rearrangement. Two readable rows paired incorrectly are as troublesome as text too small to read.
Also prepare an empty optional value. A missing additional note should not leave the heading 'Notes' above a large blank field. The version with no photo and no note should still look intentional. Not every blank space is elegant breathing room; sometimes it is simply unhandled data.
Another language version must include the button and footer too. Translation length can change the layout. One screenshot with short English text does not establish that Polish instructions and a room name fit the same pattern. Long interface names (in Polish) similarly need an appropriate sample.
Send for acceptance exactly what the customer will receive
A sending tool's preview helps during work. Make the final trial on a generated message delivered to the agreed client. Record the data set, template version and reading conditions. Then changing one rule does not force the team to guess which variant an old screenshot came from.
After pasting text into the editor, check the generated result too. The tool may add its own formatting or transform part of the markup. Accept the message after it has passed through that route. A pretty editing field does not establish the recipient's view. (in Polish)
If a room organiser usually forwards the confirmation, test that too. The first recipient adds a note for the building manager and forwards it to the agreed client. Open the result: is the boundary between the new note and the original instruction visible? Does the link described as visit details remain with the right appointment? Quoting depends on the tools used, so a real run is needed rather than assuming the forwarded message preserves the entire layout.
With several replies, check which part an added correction refers to. A message may have the old appointment in a quote and the new one in a comment. The template does not itself settle the conversation's content, but should let people distinguish its parts. In our example the manager must prepare the room according to the current agreement without comparing two nearly identical logo panels.
Compare working links with their labels. 'Prepare the room' should lead to preparation instructions; 'Change the appointment' should lead to an available way to change it. Open them in the trial instead of checking button colour alone. Transactional messages (in Polish) develops the information structure; here you also accept the actual presentation and usability.
Return to the message with images off and the long room name. If a person can read the appointment, prepare the place and open the right instruction without guessing, the template has done its work. The beautiful instrument in the photograph can then remain a beautiful instrument, without a second job as the only carrier of the address.








