Accessibility in email
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABC
1
Accessibility in emailNotesExtra
2
Standards and guidelines
3
Information and Communication technology (ICT) final standards and guidelinesHowever, compliance with the section 508-based standards is not required until January 18, 2018. United States Access Board (see section 1194.22 for web-based intranet and internet information and applications).
4
Section 508 standards for electronic and infomation technoogyFinally, if you’re based in the United States (or selling to customers residing there), you can skim the government’s Section 508 Standards for Electronic and Information Technology. These standards (particularly those in section 1194.22) provide requirements for accessible technology like websites, including alt text, items being viewable with color blindness, and alerts for timed responses.
5
Section508.govhttps://section508.gov/best-practiceshttps://www.w3.org/WAI/perspectives/layout.html
6
W3C - Web content accessibility guidelines (WCAG) 2.1For websites/emails there are three levels of compliance A, AA or AAA. Can provide link to a conforming alternate version within email e.g. in browser which has more support for ARIA but ideally you want the email itself to be accessible. Reminds me a lot of when mobile first came about and having mobile version links like then landing pages also need to be accessible.three levels of conformance, ‘easy’ and ‘invisible’ to impliment = A https://www.w3.org/WAI/GL/wiki/Talk:WCAG_2.1_Success_Criteria / Level A and Level AA Success Criteria and Conformance requirements of WCAG 2.0
7
W3C (WAI) Web Accessibility Initiative
(SC) success criteria (essential or not) https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria
8
Talk:WCAG 2.1 success criteria table (essential, easy, invisible)Table how are each item is characterisedUtilize the WCAG 2.0 A/AA/AAA level structure. WCAG 2.0 Levels A and AA
9
WCAG 2.1 success criteriaWCAG success criteria
10
WCAG where to start
11
WCAG overview
(WCAG) web content accessibility guidelines quick intro good place to start (tho web specfic not email).
12
W3C easy checks
13
ADA best practices tool kit
The Americans with Disabilities Act (ADA)
14
Cognitive learningtask force
15
low visiontask force
16
Mobile accessibilitytask force
17
Checklists
18
W3C - Web content accessibility guidelines (WCAG) 2.1
19
WCAG 2.0 checklist on Wuhcag
20
WebAIM's WCAG 2.0 checklist
21
WCAG 2.0 checklist bt w3c
22
Inclusive wen design checklist by @heydonworks
23
Email articles
24
How to test accessibility of emails
25
The easiest way to keep your web apps accessible: Just use text
26
What WCAG 2.1 Means for Email Marketers
27
HTML email and accessibilityJason Rodriguez on CSS Tricks
28
Accessibility and emailcampaign monitor
29
Beginners guide to email accessibility
30
Accessibility in email (1) by rebelmail
31
Accessibility in email (2) by rebelmail
32
Email Accessibility in 2017 by EOA
33
Email accessibility guidelines (2016)
34
Building emails for accessibility (part one) by shaw + scott
35
Building emails for accessibility (part two) by shaw + scott
36
Building emails for accessibility (part three) by shaw + scott
37
Sending an email with no css
38
Ulitimate guide to accessible emails
39
Discussion on webaim on HTML vs text emails"I personally like HTML e-mails as they have the links, bullets, numbers and other tabular information. However, some e-mails are way too large as far as content, which forces JAWS to take a long time to render the HTML. Those, I prefer them in plain text. If it is going to take my SR almost 2 minutes to respond to me, I am deleting that e-mail."Also mentions how plain text lacks easy navigation e.g. being able to scan headings and links. "In general, I think that plain text is only beneficial if the HTML version doesn't have accessibility implemented." Plain text not a great experince but a last resort if HTML isn't accessible. I prefer HTML based email but those that are composed in right way. Reason being that it will have a structure to navigate.
40
Non-email specfic accessibility articles
41
The 100% Easy-2-Read Standard
42
The ALLY project checklistSure, people can adjust the font size, but do you want to? Do you want to adjust your car seat every time you get in?
43
Mobile accessibility comparing TalkBack (Android) and VoiceOver (iOS)Site has a lot of accessibility articles.
44
iOS voice over lessonstest with real users
45
Small Tweaks That Can Make a Huge Impact on Your Website’s Accessibility
46
Changing definition of "Large text" to use px rather than pt
47
How to use TITLE attributes
48
Using Caption services with HTML5 Video
49
7 lessons from developing an accessible HTML5 video player by PayPal
50
Accessible and responsive HTML5 video player
51
Making images accessible for people on Twitter
52
ecommerce accessibility tipsmentions a bunch of tools
53
A List Apart ally tag
54
Smashingmag ally tag
55
Dos and don'ts on desogning for accessibility by goc.uk
56
Videos and slides
57
Accessibility in HTML emailMark Robbins 2017 talk for #ID24 deck http://bit.ly/2ioO2jt
58
Inclusive Design 24Free online 24hr conference all about accessibility, lots of videos.
59
Accessibility in email webinar by EOAExpand on the preheader tag for suri on iOS
60
Email Accessibility: How to Captivate and Connect with Every Subscribereoa
61
Baking accessibility invideo from clarity conf (abt design systems)
62
A Type of Accessibility deck by paul Airy (2016)
63
Litmus design conference videos
See Paul Airy talk breaks down foundational elements: Typography, Layout, Buttons and links, Images and color
64
Accessibility for animated gifs
65
Perspectives videos on various issues
66
Links vs buttons
67
Examples
68
TypeEAccessibility email issue
69
G email
70
Provincie email
71
Arriva emailhttps://litmus.com/builder/e5103b3
72
emailweekly
73
Contest by Litmus to create an accessible email
74
Accessible SVG on codepen
75
Accessible HTML5 video player on github by PayPal
76
Tools
77
Chrome settings minimum font-sizeTo test what your email would look like with larger minimum font sizes (works in browser and Gmail): Chrome settings/Customize fonts/Minimum font size
78
Android phoneFor Android phones go to the settings and accessibility menu then turn on talk back.
79
iOS phoneFor iOS go to settings, general, accessibility, voiceover
80
brunildoTool for calculating aspect ratio of a font
81
WC3 WAI Tablin FormAdd the URL of the web version of the email, and check the results of the order of your email. Order of tables see: https://www.w3.org/WAI/Resources/Tablin/
82
Vision AustraliaVarious ALLY tools
83
W3C markup validation
84
WebAIM contrast checker
85
Lighthouse
86
wave
87
Contrast ratioEnter bg value and foreground text value and calculates ratio for you.
88
Color contrast check by SnookTells you if your contrast check is AA or AAA compliant
89
Contrast finder
If you have foreground and background brand colors that fail WCAG SC it will give you close alternatives that pass
90
Color safeHelps you choose accessible color combinations that are contrast-compliant
91
Colorblind web page filter
92
Chrome extension accessibility dev tools
93
WAVE web accessibility eval tool
94
Jawsscreen reader
95
Test using a screen reader
96
Test using a keyboard only
97
Accessible email tool
98
SVG
99
W3C accessibility features of SVGlonger doc
100
W3C SVG accessibility support Unlike many of the newer technologies, SVG actually has a fairly large and well thought out accessibility component. The W3C has a short list of accessibility points for SVG, and a much longer document explaining the concepts in more detail. (short list)
Loading...
 
 
 
Accessibility
 
 
Main menu