Stop using images of text – use live text instead – people use browser extensions to adjust the text on their page and that can’t work with images of text!
Re: Image Based Emails – Your brand font is dead


Stop using images of text – use live text instead – people use browser extensions to adjust the text on their page and that can’t work with images of text!

Email clients do support landmarks and they should definitely be used (sparingly) to let users navigate emails more easily.

TLDR; Just don’t.

Today, in Part 4, I’m taking a bit of a step back and asking a broader question about why we feel the need to link everything. That’s right, I’m talking about an accessible linking strategy.

We’ve already talked about the functional side of links and how different users activate them. Today, we’re taking that info and expanding on it.

Because links are such critical elements of our emails, we should think about all the different parts of them that need accessibility support.

Links (technically hyperlinks) are the foundation of the internet. In its simplest form, a link is already accessible. You’d think that would mean that we wouldn’t have to think that much about them, but you’d be wrong.

There are few things as confounding in email development as the CTA link. Historically, getting anything other than an image to render has had considerable challenges. Many email developers have spent hours and hours tweaking their code to get a CTA link to visually render…

An aria-label is an ARIA attribute that supports assistive technologies by helping to name elements on a page or application. Many elements in our emails need an “accessible name,” which is a way for AT to define the element to AT users.

Every once in a while, people will bring up adding ARIA to their emails, and quite often, my response is, “NO!!” and I thought I’d go into a bit of detail to explain that.