{"id":1822,"date":"2021-03-16T15:01:20","date_gmt":"2021-03-16T19:01:20","guid":{"rendered":"https:\/\/new.umaine.edu\/userguide\/?p=1822"},"modified":"2021-07-09T15:03:41","modified_gmt":"2021-07-09T19:03:41","slug":"accessibility-and-inclusion-guidance-for-email-newsletters","status":"publish","type":"post","link":"https:\/\/umaine.edu\/userguide\/2021\/03\/16\/accessibility-and-inclusion-guidance-for-email-newsletters\/","title":{"rendered":"Accessibility and inclusion: Guidance for email newsletters"},"content":{"rendered":"<p><em>(Portions of this item originally appeared in our November 2018 newsletter)<\/em><br \/>\nWeb accessibility has always been a requirement for UMaine websites, and has been a regular feature in our monthly newsletter \u2014 and ensuring your content is accessible is part of an inclusive communication strategy.This month, we focus on email, and pitfalls to avoid when sending an email newsletter or\u00a0message.<\/p>\n<p>Email is an effective engagement tool\u2014 this newsletter, for example, has been well received and gives us opportunity to share our expertise in bite-sized, monthly updates. These days, emails can contain many of the same features as web pages, and therefore the same web accessibility concerns apply.<\/p>\n<h3><strong>Images for images, text for text<\/strong><\/h3>\n<p>If you have taken the time to create a flyer for a communication, it is tempting to use an image of the flyer for an email \u201cblast\u201d to your audience; we are all busy, and that certainly can save time. Unfortunately, it gives a poor experience for many of your recipients. Anyone who relies on their computer to resize text or even read the contents of an email to them would be unable to see the content of the image\u2014 and mobile users would be presented with the image on their phone screen, perhaps too small to easily read. Even worse, some email programs will load the message without the images, and your entire message would be obscured unless the recipient chose to view the image.<\/p>\n<p>A better tactic is to let images be images, and text be text. You can crop the interesting visual element from your flier and put that in your email\u2014 email programs like MailChimp and Constant Contact allow you to add \u201calt text\u201d to the image as well, which will display in place of the image until the image is loaded. You can then use text formatting underneath the image to convey your message in a way that is accessible, searchable, and visible even if the email program does not display images by default.<\/p>\n<h3><strong>Keep text easy to read<\/strong><\/h3>\n<p>Email formatting options allow you to change the text from the default &#8220;San Serif&#8221; font and &#8220;Normal&#8221; text size. It is generally best to keep these options as-is, and not alter the font of the body text. Headings in an email can be made larger, but using fonts for artistic\/aesthetic reasons can cause problems for readers who need a vision accommodation, or have set their own email preferences for text size and font.<\/p>\n<h3><strong>Color contrast is important<\/strong><\/h3>\n<p>The color of text and images in your email should have good contrast against the background color of your email. It is especially important to keep text color at the browser default for mobile device users, where &#8220;dark mode&#8221; may be a preference for the reader. Such an option typically displays the default background in an email as black, with the default text color as white, and overriding either option may result in a poor, difficult-to-read display.<\/p>\n<h3><strong>Use descriptive link text<\/strong><\/h3>\n<p>When using an email newsletter service such as MailChimp or Constant Contact, it is even more important to give descriptive link text for any links you provide, rather than the link address itself as the link text. Not only is that bad for web accessibility, it can trigger spam\/phishing warnings in email clients when the link address does not match the link address displayed in the message (typically links in email newsletters go to the service sending the email, which redirects to the final location.)<\/p>\n<p>If you have any questions about web accessibility, or want to see us cover an accessibility topic in a future newsletter, please get in touch with us at\u00a0<a href=\"mailto:um.weboffice@maine.edu?subject=Web%20Accessibility%20question%20or%20topic%20idea\" target=\"_blank\" rel=\"noopener noreferrer\">um.weboffice@maine.edu<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>(Portions of this item originally appeared in our November 2018 newsletter) Web accessibility has always been a requirement for UMaine websites, and has been a regular feature in our monthly newsletter \u2014 and ensuring your content is accessible is part of an inclusive communication strategy.This month, we focus on email, and pitfalls to avoid when [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"30","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":"","spc_primary_category":0},"categories":[30,6],"tags":[],"class_list":["post-1822","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-advice"],"taxonomy_info":{"category":[{"value":30,"label":"Accessibility"},{"value":6,"label":"Advice"}]},"featured_image_src_large":false,"author_info":{"display_name":"kirby","author_link":"https:\/\/umaine.edu\/userguide\/author\/kirby\/"},"comment_info":"","category_info":[{"term_id":30,"name":"Accessibility","slug":"accessibility","term_group":0,"term_taxonomy_id":30,"taxonomy":"category","description":"","parent":0,"count":60,"filter":"raw","cat_ID":30,"category_count":60,"category_description":"","cat_name":"Accessibility","category_nicename":"accessibility","category_parent":0},{"term_id":6,"name":"Advice","slug":"advice","term_group":0,"term_taxonomy_id":6,"taxonomy":"category","description":"","parent":0,"count":69,"filter":"raw","cat_ID":6,"category_count":69,"category_description":"","cat_name":"Advice","category_nicename":"advice","category_parent":0}],"tag_info":false,"_links":{"self":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts\/1822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/comments?post=1822"}],"version-history":[{"count":1,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts\/1822\/revisions"}],"predecessor-version":[{"id":1823,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/posts\/1822\/revisions\/1823"}],"wp:attachment":[{"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/media?parent=1822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/categories?post=1822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/umaine.edu\/userguide\/wp-json\/wp\/v2\/tags?post=1822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}