This week I’m digging deep into the details of what we need to do with our data tables to ensure they work for assistive tech users – we’re starting with testing and then we’ll talk layout/design differences.
Data tables in email – Part 2


This week I’m digging deep into the details of what we need to do with our data tables to ensure they work for assistive tech users – we’re starting with testing and then we’ll talk layout/design differences.

Welcome to my two part series on data tables in emails – aka – when not to use role=”presentation”! This week, we’re talking intro to the main structural elements needed in data tables, where data tables show up in emails, and some basic functional issues we run across in our email marketing efforts.

Let’s talk about dynamic images – oh yea! Everyone loves them, no one wants to think about alt text. Le sigh.

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

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…

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.

Accessible headings in email seem to be a bit of a side quest for many email marketers. On its face, it seems very straightforward: Wrap the main points of the email in a heading tag…