Categories
Crossposts Ladyguides

Ladyguide: Creating Accessible Emails

Creating accessible organizing is challenging. I know that for me, text-based communication is usually preferred. But there are major difficulties for a wide range of people with text.

The go-to as far as access tends to be face-to-face meetings. A lot of orgs and advisories are facing defunding or under-funding because of budget issues. In many cases, this means that fewer face-to-face meetings are doable.

I recently had one of the advisories I’m involved with run into issues. I can’t do phone calls without support if I want to be actively involved. One person was having issues with too many emails. Face-to-face wasn’t in the budget. Another person’s learning disabilities made many emails very difficult.

In response, I sent an email with some suggestions for writing accessible emails. I’ve decided to share most of what I sent, as it seems to be an issue. I even had an incoming search term about making something accessible.

Basic tips for making emails accessible
  • The first one is that we often ask people to stay on topic in emails. If sending multiple emails is an issue, utilize bullet points. This allows for a visual separation of information. If bullet points don’t work, divide your email into sub-headers that are bolded or underlined. This will create visual sections that let people organize the information better.
  • Use short words and short sentences. It is said that brevity is the soul of wit. It’s also the soul of writing in accessible language. Using short sentences makes it easier to process. Using short words makes those sentences even easier to read. If you do need to use complicated words, either explain or provide a link to a definition.
  • If you use inline hyperlinks (links), don’t have the text be non-descriptive. This is doubly true when you deal with folks who use screen readers. Instead of using “here” or “at their site”, use the title of the article. For example: “On their site, NYLN has resources on things like Disability History and Disability Pride.” Or, “One good resource is Opera’s Guide to Accessibility for Cognitive and Learning Disabilities.”
  • Use white space. White space is the space where you don’t have anything, like the space between paragraphs or at margins. This makes it easier for those with ADHD, ASDs, and so on to organize information and avoid distraction. When there is little white space, it is visually confusing for any number of people.
  • Formatting. Making sure that text lines aren’t too long is important. This isn’t so much an issue for email, unless you have a habit of writing in huge text and forcing people to scroll over. Make sure text is tall enough to be legible, but not so tall that it becomes an issue. This is usually between 12pt and 14pt font.
  • Use short paragraphs that stay on topic. Paragraphs visually divide chunks of information. By writing relatively short paragraphs that are on topic, you make it easier for the reader to sort information.
  • Try to use spell check and grammar, and double check that spell check was right. The wrong words can make things extremely difficult to navigate for those with LDs.
  • Use image descriptions. Some people can’t see, but others have processing issues with images. Providing a basic description of images can be really helpful. And use images sparingly unless requested otherwise.
  • Create an environment that is welcoming. Don’t act defensive when someone asks for an accommodation. I know that we have some negative role models in this area. Some of us were even shamed and forcibly trained out of asking for our access needs to be met. Make sure you create an environment that isn’t modeled after that. One good way of doing this is to mention what your access needs are. For example, I might need certain information in chart or graph form. Don’t just say “Some people might need x,” when you are talking about yourself, if you can help it. We live in a world where alternative access needs are shamed enough without us internalizing that shame. Instead, add, “For example, I have difficulties sorting out what information is important in long emails.”

These are based on a number of different access guides. Some of them are internal standards we use at Autism Women’s Network. Some of them are from things like the Opera Accessibility article linked above.

Working with multiple access needs

When working in groups with multiple access needs, one need doesn’t mean all others are invalid. It means we work together to find solutions.
For example, I’m generally not okay with phone calls. But for NYLN meetings we have someone who gets on Google Chat and who can say my comments for me while I listen. Listening can still sometimes be hard for me, but it’s enough that I can do it. For people who can’t do face-to-face meetings, there are interfaces that can be used within reason. Making all our meetings in person isn’t accessible for many people for financial reasons.
For emails, if we write accessibly, we can create something doable.


See this article in its original context at Cracked Mirror in Shalott.


 

By Savannah Logsdon-Breakstone

Savannah Logsdon-Breakstone.

Advocate, Writer, Geek.
Multiply Disabled, Queer, and proudly Autistic.
Primary Obsession: Institutions, History of Care of people with MH/DDs
Also obsessed with: Social Justice, Cats, Victorian Romanticism, and Doctor Who.

http://crackedmirrorinshalott.wordpress.com/

4 replies on “Ladyguide: Creating Accessible Emails”

I echo Anna’s sentiment, this is great! I’ll be honest when I say that I have never really considered these things when writing emails. As you know, I work with students with disabilities, and these are all things I would consider in, say, a class handout, but never in a broader context.

Additionally, these points are really useful to many people in general. I love bullet points! And I also love when links are described. :)

Leave a Reply
https://persephonemagazine.com/2011/03/ladyguide-creating-accessible-emails/
persephonemagazine.com
crawl=CC-MAIN-2021-21
113399
application/http; msgtype=response
sha1:WFIEQH23DYJDDR6X423MRBVIHM5LK6MD
<urn:uuid:ff76cad9-392e-4914-88c0-39a8c6069ee0>
2021-05-12T13:21:39Z
45.56.68.160
text/html
sha1:3VYHDGJVP6BQMWBV2WGG3LHVQUPLMRQG
<urn:uuid:ab614e4a-ab86-434d-84fb-a96a43984a54>
https://persephonemagazine.com/2011/03/ladyguide-creating-accessible-emails/
response
<urn:uuid:af1355a9-5895-416c-aadd-1fef5b4b5192>
isPartOf: CC-MAIN-2021-21
publisher: Common Crawl
description: Wide crawl of the web for May 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-185.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/