Back to main menu


Email accessibility mistakes that annoy subscribers & how to fix them

Sometimes ensuring we're following email accessibility best practices is not easy. Here are 14 common email accessibility mistakes and how to fix them.



Email accessibility is a pretty simple concept: Everyone who receives your email should be able to read it and engage with it. Everyone. Making this happen, however, is a bit more complicated, which is why so many companies struggle to get it right.

But they have to get it right. Why? Over 12 million people in the US alone have some form of vision impairment, including color blindness. Hearing impairment is the third most reported chronic problem among the aged population, but 65% of people with hearing loss are younger than retirement age. And as much as 10% of the global population is dyslexic.

With millions of people encountering less-than-stellar email experiences, companies and developers who lead through accessibility will thrive over the coming years. It takes some extra effort, but it will pay off.

Here are 14 ways your emails might be inaccessible to certain subscribers. Most of them have to do with vision impairments, one of the most common accessibility needs.

1. Unreadable color contrast

WCAG standards suggest a 4.5:1 contrast ratio for digital text. If your background is anything other than white, you have to be very selective in which colors you choose for text, buttons, and other elements. It’s very hard to distinguish between the foreground and background when they’re similar shades. 


Even if you’re using a white background, you can still gum up the readability. Using yellow and pure green for text will irritate everyone, even subscribers with full vision. That’s because they have very low contrast ratios against white - less than 2:1. Black on white has the highest contrast, at 21:1. It may be “boring”, but it’s the easiest to read, by far. Ultimately, what matters more than that? 

But, if you feel the need to use colored text, or if you have text or buttons that change colors when you hover over them, choose wisely. Use an accessibility testing tool like Email on Acid’s Campaign Precheck. Color contrast is one aspect of email accessibility that is tested by Campaign Precheck, so you’ll know if you’re ever sending out an email with text that is hard to read. 

2. Microscopic or ‘creative’ fonts

You might be tempted to use goofy or wacky fonts if your brand guidelines allow it – Halloween themes are notorious for this. But it’s no fun if no one can read it, and reading crazy fonts is always harder on screens than on paper, especially on tiny screens.

Opt for simple and easily readable fonts rather than scripts or themed fonts (letters that look like dinosaurs or like they belong on a ransom note might not be the best choice).

Also, use fonts that are larger than 14px in size. Again, it’s harder for everyone to read small fonts on screens. For anyone with even partial vision impairment, it becomes too much work, and they’ll abandon the effort.

3. Bunched up text

A properly formatted email, even if it’s pretty long, is fine. But an email with text all bunched up in large paragraphs, or with not enough kerning, is hard to read, especially on a smaller screen. 

Instead, break text up into smaller paragraphs, and use headers and bullets so it’s easier to engage with. This also allows screen readers to make more sense of the email and get through it faster. And speaking of screen readers…

4. Not using semantic HTML

Screen readers are tools used to help people with vision impairments or other cognitive challenges read and engage with online content. They’re not just for blind people, but also for those with conditions like glaucoma and cataracts. But you must have accessible content in order for the screen reader to give a good experience to the subscriber, and semantic HTML is the key to doing this well.

However, in the Accessibility in the Inbox survey from Pathwire (a Sinch Company), just 4% of respondents said they use semantic HTML markup when designing and coding their emails. 

That’s only one out of 25!

Semantic HTML tells a screen reader how to interpret various elements such as headings, buttons, and paragraphs. 

Using semantic tags such as <h1>, <p>, <button>, and <nav> enables the screen reader to tell the subscriber what those various elements are. It also allows for quicker scanning of the email. Otherwise, they have to wait for the reader to go through the entire email. 

But with headings, they can skip faster to various sections. Other tags, such as <b> and <div>, are non-semantic HTML, and screen readers don’t respond to them. Here’s a list of more semantic and non-semantic HTML elements. 

5. Sending image-only emails

This is one of the most annoying email experiences and one of the most unwise mistakes you can make. For one, many people with normal vision have their email client set to not render images. So if you send an email that’s just an image, they’ll see nothing when they open it up. That’s bad.

But beyond that, image-only emails are about the most inaccessible emails you could possibly send because screen readers can’t engage with any of the content within the image (unless you use alt text, which we’ll discuss in a bit). So if you create a big beautiful graphic, filled with text, images, and a CTA, anyone using a screen reader will miss your entire message. 

Can’t do much worse than that when the goal is email marketing.

Instead, make sure your most important information is included as live text. You can still include images to enhance key points or draw attention to specific things. You can even find ways to tastefully repeat your call to action in both live text and on images. But if you have to choose only one — live text is the way to go. 

Ask yourself: “If none of these images load and I’m only left with text, will people still understand my message?” 

An email accessibility check, like one from Email on Acid, can also help you spot gaps. 

6. Burying key text on images

Image-only emails are one thing. But if you do send images as part of your email, you still need to make sure your key messages and CTAs appear in the text portion of the email too.

Why? Because if the CTA only shows up in the image, then anyone using a screen reader will not see it. If they don’t see it, they can’t click on it. 

So, it’s okay if you want to put a CTA on the image to engage everyone else, but you should also put it elsewhere in the email where everyone will be sure to see it. And that goes for any other messaging or critical text elements that you want everyone to see.

And while we’re on the topic, even if you do incorporate messaging onto images, don’t forget about color contrast. In general, it’s risky to combine text with images, unless it’s done very delicately.

7. Hard to read buttons

Like images, color contrast on buttons is a common cause of poor email accessibility. The color of the button, the color of the text on it, and the color of the background all work together to deliver either an easy reading experience or a frustrating one. 

Also, for anyone using a screen reader, the screen reader needs to know this is a button. Otherwise, it won’t communicate it in a clear way to the subscriber. Use the code role=”button” so the screen reader knows this is a button.

8. Invisible links 

It’s common to make links appear as different colors from the rest of the text. But for subscribers who have any form of color blindness, this increases the risk they’ll not see the link. Red-green color blindness is the most common form, but there are others. 

To avoid this, use other visual cues, such as underlining it, putting stars around it, or using arrows or other graphic elements to draw attention to it. 

9. Invisible images - no alt text

People relying on screen readers won’t be able to see your images. So, what can you do? The only way around this is to write alt text for every image. Without this, they might as well be invisible to a person with a vision impairment.

Alt text describes the image, but you must use enough detail so the subscriber has a clear understanding of what it’s showing, and if there’s any text on it, what it says. 

An example of alt text for this image might be: “A single hot dog with yellow mustard and green onions sitting on an orange background.”

Why doesn’t this solve the image-only email problem mentioned earlier? Because if the entire email is an image, then the alt text would basically have to express the entire message of the email, as contained in the image. If you’re going to do that, then why not just…write it in the email. Alt text isn’t the place for an entire email message. 

10. Reading Spanish emails with an English accent

Email accessibility isn’t just about visual impairments. If you have email segments that include people who speak different languages, what will someone in that segment experience if they also rely on a screen reader? 

You can tell a screen reader which language the email is written in, and this will affect how it communicates the email to the subscriber. It’s another detail that’s easy to overlook. It’s another thing that Email on Acid’s accessibility tool does automatically so you never have to worry about it. 

11. Centering all your text

This generally looks terrible, so just don’t do it. It’s harder to read for everyone. But centered text, especially when we’re talking about entire paragraphs, is especially hard to read for people with dyslexia. 

Left-aligned text is generally the route you should take. Why? It creates a straight left edge where the first letters of each word line up, rather than a jagged edge. This means that subscribers don’t have to work so hard to read your content because they know exactly where each line begins.


Still want to use centered text? Try to keep it just to headlines or short, standalone sentences.

12. Not coding tables correctly

This is a really bad one if you mess it up. If you use tables in emails, screen readers have a hard time with them. If you don’t do anything about it, the screen reader will vocalize all the HTML code in the table to the subscriber, out loud! You can imagine what this would do to a person relying on the screen reader to engage with your email. 

But the fix is easy. Simply add the code role=”presentation” to the table, and the screen reader will recognize this as a table and read it to the person in a way they can understand. This is also yet another small detail that’s very easy to overlook, and that Email on Acid’s  Campaign Precheck does for you automatically. 

13. Missing or unclear subject lines and preheaders

This one again affects far more people than just those with vision impairments. Anyone relying on Siri or Alexa to read their emails to them will know if you make this mistake.

Screen readers, as well as voice readers, use your subject and preheader to tell the subscriber (listener) what the email is about. If you write unclear subjects and preheaders (or don’t include one at all) it makes it harder for the person to decide if they want to hear the rest of the email.

First of all, never leave the subject line blank or let the pre-header text fill automatically. It won’t be inspiring to anyone reading or listening. 

Instead, be intentional about what you write. Even if you don’t think what you’ve written is award-winning, studies show anywhere from a 3-8% increase in open rates when you include even any sort of intentional preheater text.

For subject lines, aim for something exciting and engaging, but don’t be dishonest or overly cheesy (unless that’s your brand, of course!). Subscribers have become wise to click-bait and sensational headlines. And if you promise something that the email doesn’t contain, your next email’s click-through rate is going to suffer… and so will your deliverability. 

Don’t waste space with something like a repeat of the subject line. Instead, the preheader text should complement the subject. For example, if the subject line poses a question, the pre-header text could start to answer the question. 

Need some inspiration: See five email preheader text ideas to get you started

14. Not testing your emails for accessibility

Nobody can become an accessibility expert overnight, but even fixing basic issues will push you ahead of many in the industry.

A good place to start is by understanding how easily your current emails can be consumed. This gives you a baseline to improve upon. But trying to figure things out yourself is not only more cumbersome, but it leaves a lot of room for error. Like anything with email efficiency. finding the right tools is key. 

Email on Acid’s campaign precheck tool is designed to immediately identify potential issues and even offer instant solutions. And email accessibility is at the top of the list. Not only will it help you determine what needs more work, but it’ll also give you peace of mind that when you do finally hit send, everything is perfect.  Learn more about the Email Accessibility Campaign Precheck tool and how it helps you send ADA-compliant emails. 

Wrapping up

As you may have realized by now, there’s a lot more to creating fully accessible emails - for everyone - than simply using easy-to-read colors. The more elements you add to your emails, the more likely you might be creating an accessibility problem for some of your subscribers. 

Want to learn more about email accessibility? Download our free guide, Accessibility in the Inbox, and sign up for our newsletter to get the best tips and tricks in your inbox.

Related readings

5 ideas for better developer-designer collaboration

Developing an app is a team sport, requiring teamwork from a number of players, including...

Read more

Dark mode for email survey: What do email senders think?

Does the possibility of dark mode email disasters give you nightmares, or has your team...

Read more

The basics of email dark mode

We all know that light tends to win over dark. Just look at Star Wars or Lord of the Rings… or The Divine Comedy, for that matter. Pop culture – or just culture, really – has taught us...

Read more

Popular posts

Email inbox.

Build Laravel 10 email authentication with Mailgun and Digital Ocean

When it was first released, Laravel version 5.7 added a new capability to verify user’s emails. If you’ve ever run php artisan make:auth within a Laravel app you’ll know the...

Read more

Mailgun statistics.

Sending email using the Mailgun PHP API

It’s been a while since the Mailgun PHP SDK came around, and we’ve seen lots of changes: new functionalities, new integrations built on top, new API endpoints…yet the core of PHP...

Read more

Statistics on deliverability.

Here’s everything you need to know about DNS blocklists

The word “blocklist” can almost seem like something out of a movie – a little dramatic, silly, and a little unreal. Unfortunately, in the real world, blocklists are definitely something you...

Read more

See what you can accomplish with the world's best email delivery platform. It's easy to get started.Let's get sending
CTA icon