diff --git a/_includes/techniques/about.html b/_includes/techniques/about.html
index a21e7c6107..1a6fba05cd 100644
--- a/_includes/techniques/about.html
+++ b/_includes/techniques/about.html
@@ -5,6 +5,11 @@ <h2 class="box-h">Obsolete</h2>
 </section>
 {% endif %}
 {% sectionbox "technique" "About this Technique" %}
+{% if technique.technology == "failures" %}
+  <p>Failure examples fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that <strong>does</strong> satisfy the normative requirements. See <a href="about">About WCAG Techniques</a>.</p>
+{% else %}
+  <p>Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are <strong>not required</strong> to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques. See <a href="about">About WCAG Techniques</a>.</p>
+{% endif %}
 {% include "techniques/applicability.html" %}
 {% case technique.technology %}
 {% when "aria" %}
diff --git a/techniques/about.html b/techniques/about.html
index c9ac384cc5..c14e78f8af 100644
--- a/techniques/about.html
+++ b/techniques/about.html
@@ -30,9 +30,11 @@
         <main id="main" class="main-content standalone-resource__main">
            <h1>About WCAG Techniques</h1>
               <aside class="box">
-                <header class="box-h ">Summary</header>
+                <header class="box-h">Summary</header>
                 <div class="box-i">
-                  <p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. To start learning about WCAG, see the <a href="https://www.w3.org/WAI/intro/wcag">WCAG Overview</a>. For important information about techniques, see the <a class="understanding" href="../Understanding/understanding-techniques">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG.</p>
+                  <p>Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are <strong>not required</strong> to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques.</p>
+                  <p>Failure examples fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that <strong>does</strong> satisfy the normative requirements.</p>
+                  <p>To start learning about WCAG, see the <a href="https://www.w3.org/WAI/intro/wcag">WCAG Overview</a>. For important information about techniques, see the <a class="understanding" href="../Understanding/understanding-techniques">Understanding Techniques for WCAG Success Criteria</a> section of Understanding WCAG.</p>
                 </div>
               </aside>
           <section id="aboutwcag">
diff --git a/techniques/index.html b/techniques/index.html
index dbf195fca7..57fa529d0d 100644
--- a/techniques/index.html
+++ b/techniques/index.html
@@ -41,7 +41,9 @@ <h1 id="title" class="title p-name">Techniques for WCAG {{ versionDecimal }}</h1
 		<aside class="box">
 			<header class="box-h ">Summary</header>
 			<div class="box-i">
-				<p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. For information, see <a href="about">About WCAG Techniques</a>.</p>
+				<p>Techniques are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are <strong>not required</strong> to meet WCAG. Content can satisfy the normative requirements of WCAG even if it does not use any of the documented techniques.</p>
+				<p>Failure examples fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that <strong>does</strong> satisfy the normative requirements.</p>
+				<p>For information, see <a href="about">About WCAG Techniques</a>.</p>
 			</div>
 		</aside>