{"id":71320,"date":"2022-01-26T19:00:00","date_gmt":"2022-01-26T08:00:00","guid":{"rendered":"https:\/\/elements.blog-cms.envato.net\/?p=43527"},"modified":"2025-11-11T17:46:58","modified_gmt":"2025-11-11T06:46:58","slug":"how-to-conform-to-wcag-web-content-accessibility-guidelines-in-email","status":"publish","type":"post","link":"https:\/\/elements.envato.com\/learn\/how-to-conform-to-wcag-web-content-accessibility-guidelines-in-email","title":{"rendered":"How to Conform to WCAG (Web Content Accessibility Guidelines) in Email"},"content":{"rendered":"\n<p><a href=\"https:\/\/www.w3.org\/WAI\/standards-guidelines\/wcag\/\" target=\"_blank\" rel=\"noopener\">WCAG<\/a> (the Web Content Accessibility Guidelines) make the web a more accessible place for everyone. They\u2019re written for web content, not email content, but as the two have a lot in common, conforming to WCAG lays a good foundation for applying accessibility to email.<\/p>\n\n\n\n<p>How do you conform to WCAG when developing email? In this tutorial, I\u2019ll show you how!<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Choose a WCAG Version<\/h2>\n\n\n\n<p>There are several versions of WCAG. The current version is WCAG 2.1, and it\u2019s referred to as a \u2018recommendation\u2019. The next version will be WCAG 2.2, and this is currently referred to as a \u2018working draft\u2019. It\u2019s due to become a recommendation soon.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"850\" height=\"445\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/wcag.jpg\" alt=\"WCAG website\" class=\"wp-image-86617\" srcset=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/wcag.jpg 850w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/wcag-300x157.jpg 300w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/wcag-768x402.jpg 768w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><\/figure>\n\n\n\n<p>While the World Wide Web Consortium (W3C), the creators of WCAG, encourage the use of WCAG 2.2, most conform to WCAG 2.1. Indeed, WCAG 2.1 is the version that public sector websites and mobile apps in the UK must conform to by law.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What Does \u201cConformance\u201d Mean?<\/h3>\n\n\n\n<p><a href=\"https:\/\/www.w3.org\/TR\/UNDERSTANDING-WCAG20\/conformance.html#uc-conformance-whatis-head\" target=\"_blank\" rel=\"noreferrer noopener\">According to the W3C<\/a>:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>\u201cConformance to a standard means that you meet or satisfy the \u2018requirements\u2019 of the standard. In [WCAG 2.1] the \u2018requirements\u2019 are the Success Criteria. To conform to [WCAG 2.1], you need to satisfy the Success Criteria, that is, there is no content which violates the Success Criteria.\u201d<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">2. Choose a WCAG Conformance Level<\/h2>\n\n\n\n<p>There are three levels of WCAG conformance: A, AA, and AAA.<\/p>\n\n\n\n<p>A is the lowest level of conformance, and AAA is the highest level of conformance. AA is the level that\u2019s conformed to the most. Indeed, AA is the level that public sector websites and mobile apps in the UK must conform to by law. If you claim to conform to AA, you must conform to A as well. It\u2019s rare to see AAA conformed to in full.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"368\" height=\"130\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/wcag2_1AA_v.gif\" alt=\"Conformance logo for WCAG 2.1 AA.\" class=\"wp-image-86618\" \/><figcaption class=\"wp-element-caption\">Conformance logo for WCAG 2.1 AA.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">3. Familiarize Yourself With Each Success Criterion\u2019s Conformance Level<\/h2>\n\n\n\n<p>Each guideline\u2019s Success Criterion has been assigned a conformance level by the W3C (A, AA, or AAA), which helps you identify which Success Criterion your email content needs to meet. For example, if you\u2019ve chosen level A, your email content needs to meet all the relevant guidelines with a level A Success Criterion. If you\u2019ve chosen level AA, your email content needs to meet all the relevant guidelines with a level A and a level AA Success Criterion. If you\u2019ve chosen level AAA, your email content needs to meet all the relevant guidelines with a level A, a level AA, and a level AAA Success Criterion.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What Is a \u201cSuccess Criterion\u201d?<\/h3>\n\n\n\n<p><a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21#x0-2-wcag-2-layers-of-guidance\" target=\"_blank\" rel=\"noopener\">The W3C explains that<\/a>:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p>\u201cFor each guideline, testable success criteria are provided to allow [WCAG 2.1] to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest). Additional information on WCAG levels can be found in <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Understanding\/conformance#levels\" target=\"_blank\" rel=\"noopener\">Understanding Levels of Conformance<\/a>.\u201d<\/p>\n<\/blockquote>\n\n\n\n<p>To understand what the W3C\u2019s explanation means, it\u2019s helpful to look at an example of a Success Criterion. So let\u2019s look at <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#language-of-page\" target=\"_blank\" rel=\"noopener\">Success Criterion 3.1.1 Language of Page<\/a>:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"850\" height=\"183\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/3_1_1_Language_of_Page.gif\" alt=\"Success Criterion 3.1.1 Language of Page as shown in WCAG 2.1.\" class=\"wp-image-86619\" \/><figcaption class=\"wp-element-caption\">Success Criterion 3.1.1 Language of Page as shown in WCAG 2.1.<\/figcaption><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Success Criterion 3.1.1 Language of Page<\/strong><\/h4>\n\n\n\n<p>(Level A)<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Understanding\/language-of-page.html\" target=\"_blank\" rel=\"noreferrer noopener\">Understanding Language of Page<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/quickref\/#language-of-page\" target=\"_blank\" rel=\"noopener\">How to Meet Language of Page<\/a><\/li>\n<\/ul>\n\n\n\n<p>The default <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#dfn-human-language-s\" target=\"_blank\" rel=\"noreferrer noopener\">human language<\/a> of each <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#dfn-web-page-s\" target=\"_blank\" rel=\"noreferrer noopener\">Web page<\/a> can be <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#dfn-programmatically-determinable\" target=\"_blank\" rel=\"noreferrer noopener\">programmatically determined<\/a>.<\/p>\n\n\n\n<p>As you can see, Success Criterion 3.1.1 Language of Page states its:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Number<\/strong> \u2013 <strong>3.1.1<\/strong>\n<ul class=\"wp-block-list\">\n<li>Denotes its \u2018sub-guideline\u2019 (my terminology), which in this example is number 1, within guideline number 1, within principle number 3 (which I\u2019ll come to later).<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Name<\/strong> \u2013 <strong>Language of Page<\/strong>\n<ul class=\"wp-block-list\">\n<li>As we\u2019re working with email, we can \u2018translate\u2019 this to mean \u2018Language of Email\u2019.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Level<\/strong> \u2013 <strong>(Level A)<\/strong>\n<ul class=\"wp-block-list\">\n<li>A level A Success Criterion, which has to be conformed to, as it\u2019s the lowest level.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Success criteria<\/strong> \u2013 <strong>The default human language of each Web page can be programmatically determined<\/strong>\n<ul class=\"wp-block-list\">\n<li>These are the requirements for meeting this Success Criterion.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p>You\u2019ll note that there are two links: <a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Understanding\/language-of-page.html\" target=\"_blank\">Understanding Language of Page<\/a> and <a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/quickref\/#language-of-page\" target=\"_blank\">How to Meet Language of Page<\/a>. These \u2018Understanding\u2019 and \u2018How to Meet\u2019 links accompany each Success Criterion and link to two useful documents to help you understand and meet each one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Meet the Success Criterion for Each Piece of Content Within Your Email<\/h2>\n\n\n\n<p>Work through your email and meet the Success Criterion for each piece of content within it, reading the \u2018Understanding\u2019 and \u2018How to Meet\u2019 documents to help you. The guidelines have been broken down into four sections to help you identify which Success Criterion relates to which piece of content within your email. WCAG calls these sections \u2018Principles\u2019, and the \u2018Principles\u2019 are \u2018Perceivable\u2019, \u2018Operable\u2019, \u2018Understandable\u2019, and \u2018Robust\u2019, also known as <strong>POUR<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Perceivable<\/strong> guidelines deal with content your recipient perceives, such as images and text, and help you to make them visible and audible.<\/li>\n\n\n\n<li><strong>Operable<\/strong> guidelines deal with content your recipient interacts with, such as links and buttons, and help you to make them easy to use.<\/li>\n\n\n\n<li><strong>Understandable<\/strong> guidelines deal with content your recipient needs to understand, such as your email&#8217;s text, and help you to make it understandable by considering language and reading age.<\/li>\n\n\n\n<li><strong>Robust<\/strong> guidelines help you ensure your content can be accessed using a variety of user agents and assistive technologies, such as email clients, webmail clients, apps, and screen readers on mobile, laptop, and desktop devices.<\/li>\n<\/ul>\n\n\n\n<p>Let\u2019s look at each principle and the content their guidelines apply to in a little more detail.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Perceivable<\/h3>\n\n\n\n<p>There are four guidelines within \u2018Perceivable\u2019, all with their own \u2018sub-guidelines\u2019. They are \u2018Text Alternatives\u2019, \u2018Time-based Media\u2019, \u2018Adaptable\u2019, and \u2018Distinguishable\u2019. The types of email content they apply to, in the order they appear, include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Images<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#non-text-content\" target=\"_blank\" rel=\"noopener\">Success Criterion 1.1.1 Non-text Content<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Content Structure and Hierarchy<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#info-and-relationships\" target=\"_blank\" rel=\"noopener\">Success Criterion 1.3.1 Info and Relationships<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Content Sequence<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#meaningful-sequence\" target=\"_blank\" rel=\"noopener\">Success Criterion 1.3.2 Meaningful Sequence<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Link and Button Color<\/strong> \u2013 <a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#sensory-characteristics\" target=\"_blank\">Success Criterion 1.3.3 Sensory Characteristics<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Color Contrast<\/strong> \u2013 <a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#contrast-minimum\" target=\"_blank\">Success Criterion 1.4.3 Contrast (Minimum)<\/a> \u2013 (Level AA)<\/li>\n\n\n\n<li><strong>Text Spacing<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#text-spacing\" target=\"_blank\" rel=\"noopener\">Success Criterion 1.4.12 Text Spacing<\/a> \u2013 (Level AA)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operable<\/h3>\n\n\n\n<p>There are five guidelines within \u2018Operable\u2019, all with their own \u2018sub-guidelines\u2019. They are \u2018Keyboard Accessible\u2019, \u2018Enough Time\u2019, \u2018Seizures and Physical Reactions\u2019, \u2018Navigable\u2019, and \u2018Input Modalities\u2019. The types of email content they apply to, in the order they appear, include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Animated Images<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#three-flashes-or-below-threshold\" target=\"_blank\" rel=\"noopener\">Success Criterion 2.3.1 Three Flashes or Below Threshold<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Document Title<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#page-titled\" target=\"_blank\" rel=\"noopener\">Success Criterion 2.4.2 Page Titled<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Link Text (inside paragraph)<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#link-purpose-in-context\" target=\"_blank\" rel=\"noopener\">Success Criterion 2.4.4 Link Purpose (In Context)<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Headings<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#headings-and-labels\" target=\"_blank\" rel=\"noopener\">Success Criterion 2.4.6 Headings and Labels<\/a> \u2013 (Level AA)<\/li>\n\n\n\n<li><strong>Link and Button Text (outside paragraph)<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#link-purpose-link-only\" target=\"_blank\" rel=\"noopener\">Success Criterion 2.4.9 Link Purpose (Link Only)<\/a> \u2013 (Level AAA)<\/li>\n\n\n\n<li><strong>Link and Button Size<\/strong> \u2013 <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#target-size\" target=\"_blank\" rel=\"noopener\">Success Criterion 2.5.5 Target Size<\/a> \u2013 (Level AAA)<\/li>\n<\/ul>\n\n\n\n<p>Note: the copy (words) often get overlooked, but the W3C also provides some useful tips for <a rel=\"noopener\" href=\"https:\/\/www.w3.org\/WAI\/tips\/writing\/\" target=\"_blank\">writing for accessibility<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Understandable<\/h3>\n\n\n\n<p>There are three guidelines within \u2018Understandable\u2019, all with their own \u2018sub-guidelines\u2019. They are \u2018Readable\u2019, \u2018Predictable\u2019, and \u2018Input Assistance\u2019. The types of email content they apply to, in the order they appear, include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Language Attribute<\/strong> \u2013 <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#language-of-page\" target=\"_blank\" rel=\"noreferrer noopener\">Success Criterion 3.1.1 Language of Page<\/a> \u2013 (Level A)<\/li>\n\n\n\n<li><strong>Reading Level<\/strong> \u2013 <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#reading-level\" target=\"_blank\" rel=\"noreferrer noopener\">Success Criterion 3.1.5 Reading Level<\/a> \u2013 (Level AAA)<\/li>\n\n\n\n<li><strong>Consistent Elements<\/strong> \u2013 <a href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#consistent-identification\" target=\"_blank\" rel=\"noreferrer noopener\">Success Criterion 3.2.4 Consistent Identification<\/a> \u2013 (Level AA)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Robust<\/h3>\n\n\n\n<p>There is one guideline \u2013 \u2018Compatible\u2019 \u2013 within \u2018Robust\u2019, with its own \u2018sub-guidelines\u2019.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Techniques to Help You Meet Each Success Criterion<\/h2>\n\n\n\n<p>Within the \u2018How to Meet\u2019 documents that accompany each Success Criterion are listed the techniques that can be used to meet them. Not all the techniques need to be used\u2014only the ones relevant to the content and relevant to email.<\/p>\n\n\n\n<p>The techniques relevant to email are \u2018General\u2019, \u2018ARIA\u2019, \u2018HTML\u2019, \u2018CSS\u2019, and \u2018Failure\u2019. The techniques not relevant to email are \u2018Flash\u2019, \u2018PDF\u2019, and \u2018Silverlight\u2019. In the documents, the techniques are prefixed with the appropriate technique type, making it easy to identify each one:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>G:<\/strong> General<\/li>\n\n\n\n<li><strong>ARIA<\/strong>: Aria<\/li>\n\n\n\n<li><strong>FLASH:<\/strong> Flash<\/li>\n\n\n\n<li><strong>H:<\/strong> HTML<\/li>\n\n\n\n<li><strong>C:<\/strong> CSS<\/li>\n\n\n\n<li><strong>PDF:<\/strong> PDF<\/li>\n\n\n\n<li><strong>SL:<\/strong> Silverlight<\/li>\n\n\n\n<li><strong>F:<\/strong> Failure<\/li>\n<\/ul>\n\n\n\n<p>To understand how the prefixes are applied, it\u2019s helpful to look at a \u2018How to Meet\u2019 document. So let\u2019s look at <a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/quickref\/?showtechniques=111#non-text-content\" target=\"_blank\">Success Criterion 1.1.1 Non-text Content<\/a>:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"850\" height=\"622\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/1_1_1_Non_text_Content.gif\" alt=\"Excerpt from 1.1.1 Non-text Content \u2018How to Meet\u2019 document.\" class=\"wp-image-86620\" \/><figcaption class=\"wp-element-caption\">Excerpt from 1.1.1 Non-text Content \u2018How to Meet\u2019 document.<\/figcaption><\/figure>\n\n\n\n<p>You can meet this Success Criterion using General, ARIA, Flash, HTML, PDF, and Silverlight techniques, indicated by their prefixes. Of these, General, ARIA, and HTML are relevant to email.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6. Situations to Help You Determine the Technique<\/h2>\n\n\n\n<p>Some techniques sit under situations to help you determine the appropriate technique for your content.<\/p>\n\n\n\n<p>The techniques for <a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#non-text-content\" target=\"_blank\">Success Criterion 1.1.1 Non-text Content<\/a> sit under six situations, labelled A to F. The first situation in this example is <strong>\u2018Situation A: If a short description can serve the same purpose and present the same information as the non-text content\u2019<\/strong>, and its email-relevant techniques are as follows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Techniques\/aria\/ARIA6.html\" target=\"_blank\" rel=\"noopener\">ARIA6: Using aria-label to provide labels for objects<\/a> \u2013 This technique refers to the use of object labels that can be read by assistive technologies. A common use in email is the implementation of <code>role=\"presentation\"<\/code> into each opening &lt;table&gt; tag.<\/li>\n\n\n\n<li><a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Techniques\/general\/G196.html\" target=\"_blank\" rel=\"noopener\">G196: Using a text alternative on one item within a group of images that describes all items in the group<\/a> \u2013 This technique refers to content that combines multiple images.<\/li>\n\n\n\n<li><a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Techniques\/html\/H2.html\" target=\"_blank\" rel=\"noopener\">H2: Combining adjacent image and text links for the same resource<\/a> \u2013 This technique refers to content that combines images and links.<\/li>\n\n\n\n<li><a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/WAI\/WCAG21\/Techniques\/html\/H37.html\" target=\"_blank\" rel=\"noopener\">H37: Using alt attributes on img elements<\/a> \u2013 This technique refers to content such as imagery. Therefore, it should be applied to each image in your email.<\/li>\n<\/ul>\n\n\n\n<p>The other techniques that sit under Situation A, such as Flash and Silverlight, have no relevance to email.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Tools to Help You Test Your Email\u2019s Accessibility<\/h2>\n\n\n\n<p>There are several tools that will help you test your email\u2019s accessibility. Let\u2019s look at a few of them:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WAVE Web Accessibility Evaluation Tool<\/h3>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/wave.webaim.org\/\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" width=\"850\" height=\"522\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WAVE.jpg\" alt=\"WAVE \u2013 Web Accessibility Evaluation Tool.\" class=\"wp-image-86621\" srcset=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WAVE.jpg 850w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WAVE-300x184.jpg 300w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WAVE-768x472.jpg 768w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><\/a><figcaption class=\"wp-element-caption\">WAVE \u2013 Web Accessibility Evaluation Tool.<\/figcaption><\/figure>\n\n\n\n<p>The \u2018WAVE Web Accessibility Evaluation Tool\u2019 provides snapshots of web page accessibility, and it can be used to provide snapshots of email accessibility too. Simply insert the email&#8217;s \u2018View in browser\u2019 URL into the \u2018Web page address\u2019 field.<\/p>\n\n\n\n<p>The tool features five tabs: <strong>\u2018Summary\u2019<\/strong> \u2013 <strong>\u2018Details\u2019<\/strong> \u2013 <strong>\u2018Reference\u2019<\/strong> \u2013 <strong>\u2018Structure\u2019<\/strong> \u2013 <strong>\u2018Contrast\u2019<\/strong>. Each tab contains a report on its accessibility.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Summary<\/h4>\n\n\n\n<p>A brief report. It presents the number of \u2018Errors\u2019, \u2018Alerts\u2019, \u2018Structural Elements\u2019, \u2018Contrast Errors\u2019, \u2018Features\u2019, and the use of ARIA.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Details<\/h4>\n\n\n\n<p>A detailed report. It presents the number of \u2018Errors\u2019, \u2018Alerts\u2019, \u2018Structural Elements\u2019, \u2018Contrast Errors\u2019, \u2018Features\u2019, and the use of ARIA, listing each one. Accompanying each one is a useful information icon, which, when selected, opens up a \u2018Reference\u2019 tab, providing contextual information about that specific piece of content, including references to WCAG.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Reference<\/h4>\n\n\n\n<p>Presents valuable information about the item that you selected within the \u2018Details\u2019 tab. It explains \u2018What it Means\u2019, \u2018Why it Matters\u2019, \u2018What to Do\u2019, \u2018The Algorithm\u2026 in English\u2019, and \u2018Standards and Guidelines\u2019. The latter cross-references its own \u2018<a class=\"editor-rtfLink\" rel=\"noopener\" href=\"https:\/\/webaim.org\/standards\/wcag\/checklist#sc1.1.1\" target=\"_blank\">WCAG 2 Checklist<\/a>\u2019.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Structure<\/h4>\n\n\n\n<p>Presents any HTML sectioning elements (e.g. &lt;main&gt;, &lt;nav&gt;, &lt;aside&gt;, &lt;header&gt;, &lt;footer&gt;) and heading hierarchy. If there isn\u2019t a structure (as I\u2019ve found on multiple emails I\u2019ve looked at), it simply states, \u2018This page has no heading structure!\u2019<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Contrast<\/h4>\n\n\n\n<p>Presents color contrast failures it identifies, measured against WCAG 2.1 A and WCAG 2.1 AAA. The sliders within this tab allow you to adjust the colors to ones that pass, which you can then apply to your CSS.<\/p>\n\n\n\n<p>Finally, you can switch styles on and off to understand whether the content follows a meaningful sequence as per <a class=\"editor-rtfLink\" href=\"https:\/\/www.w3.org\/TR\/WCAG21\/#meaningful-sequence\" target=\"_blank\" rel=\"noopener\">Success Criterion 1.3.2 Meaningful Sequence<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WebAIM Contrast Checker<\/h3>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" width=\"850\" height=\"970\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WebAIM_Contrast_Checker.jpg\" alt=\"WebAIM Contrast Checker.\" class=\"wp-image-86622\" srcset=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WebAIM_Contrast_Checker.jpg 850w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WebAIM_Contrast_Checker-263x300.jpg 263w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/WebAIM_Contrast_Checker-768x876.jpg 768w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><\/a><figcaption class=\"wp-element-caption\">WebAIM Contrast Checker.<\/figcaption><\/figure>\n\n\n\n<p>The WebAIM Contrast Checker is the same tool as the one \u2018built in\u2019 to the \u2018WAVE Web Accessibility Evaluation Tool\u2019, except that you have to insert the hexadecimal color codes manually.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">accessible-email.org<\/h3>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.accessible-email.org\" target=\"_blank\" rel=\"noreferrer noopener\"><img decoding=\"async\" width=\"850\" height=\"436\" src=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/accessible_email_org.jpg\" alt=\"accessible-email.org Email Accessibility Evaluation Tool.\" class=\"wp-image-86623\" srcset=\"https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/accessible_email_org.jpg 850w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/accessible_email_org-300x154.jpg 300w, https:\/\/elements.envato.com\/learn\/wp-content\/uploads\/2024\/02\/accessible_email_org-768x394.jpg 768w\" sizes=\"(max-width: 850px) 100vw, 850px\" \/><\/a><figcaption class=\"wp-element-caption\">accessible-email.org Email Accessibility Evaluation Tool.<\/figcaption><\/figure>\n\n\n\n<p>Built by Maarten Lierop and Jordie van Rijn, this email accessibility evaluation tool allows you to validate an email before it\u2019s sent, by inserting its HTML, and after it\u2019s sent, by inserting its \u2018View in browser\u2019 URL. Like the WAVE Web Accessibility Evaluation Tool, it presents a valuable report.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">In Summary<\/h2>\n\n\n\n<p>As you\u2019ve seen, conforming to WCAG in email requires effort. However, if you follow the process I\u2019ve outlined in this tutorial, you\u2019ll achieve it with minimal effort. I\u2019ll leave you with a summary of that process:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Choose a WCAG version<\/strong> \u2013 I recommend WCAG 2.1 until WCAG 2.2 becomes a recommendation.<\/li>\n\n\n\n<li><strong>Choose a conformance level<\/strong> \u2013 I recommend AA, but if you can meet AAA with any of your content, do so.<\/li>\n\n\n\n<li><strong>Become familiar with the Success Criterion<\/strong> \u2013 The more familiar you become with them, the easier it will be to apply WCAG to your content.<\/li>\n\n\n\n<li><strong>Use appropriate techniques<\/strong> \u2013 Only use the techniques appropriate to your content \u2013 you don\u2019t need to use Flash techniques in an email!<\/li>\n\n\n\n<li><strong>Use tools<\/strong> \u2013 Tools will help you evaluate the conformance of your email.<\/li>\n<\/ul>\n\n\n\n<p>Get off to a solid start in your next email project by using a <a href=\"https:\/\/elements.envato.com\/web-templates\/email-templates\">professionally designed email template<\/a> from Envato Elements.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to make your emails more accessible by following the Web Content Accessibility Guidelines.<\/p>\n","protected":false},"author":199,"featured_media":86624,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[207],"tags":[],"class_list":["post-71320","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-design"],"acf":[],"_links":{"self":[{"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/posts\/71320","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/users\/199"}],"replies":[{"embeddable":true,"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/comments?post=71320"}],"version-history":[{"count":0,"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/posts\/71320\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/media\/86624"}],"wp:attachment":[{"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/media?parent=71320"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/categories?post=71320"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/elements.envato.com\/learn\/wp-json\/wp\/v2\/tags?post=71320"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}