Skip to content

Commit 6e2100f

Browse files
Apply suggestions from code review
Co-authored-by: Patrick H. Lauke <[email protected]>
1 parent 970cf66 commit 6e2100f

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

techniques/about.html

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,9 @@ <h1>About WCAG Techniques</h1>
3232
<aside class="box">
3333
<header class="box-h">Summary</header>
3434
<div class="box-i">
35-
<p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. Content can satisfy the normative requirements of WCAG success criteria even if it does not use any of the documented techniques. Similarly, common failure examples do fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that does satisfy the normative requirements. 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>
35+
<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>
36+
<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>
37+
<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>
3638
</div>
3739
</aside>
3840
<section id="aboutwcag">

techniques/index.html

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,9 @@ <h1 id="title" class="title p-name">Techniques for WCAG {{ versionDecimal }}</h1
4141
<aside class="box">
4242
<header class="box-h ">Summary</header>
4343
<div class="box-i">
44-
<p><em>Techniques</em> are examples of ways to meet Web Content Accessibility Guidelines (WCAG). They are not required to meet WCAG. Content can satisfy the normative requirements of WCAG success criteria even if it does not use any of the documented techniques. Similarly, common failure examples do fail particular WCAG success criteria in isolation, but content can still pass those criteria if it includes additional content or functionality that does satisfy the normative requirements. For information, see <a href="about">About WCAG Techniques</a>.</p>
44+
<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>
45+
<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>
46+
<p>For information, see <a href="about">About WCAG Techniques</a>.</p>
4547
</div>
4648
</aside>
4749

0 commit comments

Comments
 (0)