Text Email Newsletter "Standard" | August 11, 2004
The people behind the E-access Bulletin Newsletter have suggested a format to increase the accessibility of email newsletters. The format, which they are calling the Text Email Newsletter Standard includes suggestions such as
- Making the first text in the email the name of the newsletter.
- Having a contents section at the top.
- Dividing the newsletter into numbered sections and including text in square brackets at the end of each section to say that the section has finished.
- Using the + symbol to denote heading hierarchy.
- And possibly the most important thing for screen reader users, avoiding long lines of symbols for graphical formatting.
Most of these suggestions make sense, although a couple of issues were raised on a WAI mailing list recently. I’d be interested to see what you folks make of these recommendations, especially if you’re involved in the accessibility community or the writing of email newsletters.
Posted at August 11, 2004 5:26 PM
Derek Featherstone said on August 11, 2004 8:31 PM
Hi Andy,
I recall discussing this a while back in a conversation with Laura Carlson about her weekly newsletter. At first I was a bit skeptical, and found it to be a bit clumsy to look at. I’ve been reading her newsletter every week for close to a year now, and I had honestly forgotten about all of the extra + signs [section ends] that were in there. Essentially, they’ve disappeared - I just skim on past them, not noticing them at all.
Which means, if it helps screenreaders, then I don’t see it as a big issue.
What I’ve never been sure about is how they arrived at these guidelines? I’m not saying that it isn’t good advice — some points seem very relevant. However, I’d question some of them:
I’d be very interested in any other information as well — like how/why/when they came up with the guidelines. Maybe this is a case where some of their guidelines apply to older versions of screen readers? It would be great if we could see some results of testing with screen reader users. I asked a few of our testers about it when I first heard of TEN, and they didn’t have much to say either way — a case where they are simply used to “coping” with what they get?