Replace straggler WAI/WCAG21 links to WAI/WCAG22

Closes #3635

Author: patrickhlauke

guidelines/terms/20/accessibility-supported.html

@@ -80,7 +80,7 @@
 
    <p class="note">The Accessibility Guidelines Working Group and the W3C do not specify which or how much support by assistive
       technologies there must be for a particular use of a web technology in order for it
-      to be classified as accessibility supported. (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#support-level">Level of Assistive Technology Support Needed for "Accessibility Support"</a>.)
+      to be classified as accessibility supported. (See <a href="https://www.w3.org/WAI/WCAG22/Understanding/conformance#support-level">Level of Assistive Technology Support Needed for "Accessibility Support"</a>.)
    </p>
 
    <p class="note">Web technologies can be used in ways that are not accessibility supported as long
@@ -100,7 +100,7 @@
 
    <p class="note">One way for authors to locate uses of a technology that are accessibility supported
       would be to consult compilations of uses that are documented to be accessibility supported.
-      (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#documented-lists">Understanding Accessibility-Supported Web Technology Uses</a>.) Authors, companies, technology vendors, or others may document accessibility-supported
+      (See <a href="https://www.w3.org/WAI/WCAG22/Understanding/conformance#documented-lists">Understanding Accessibility-Supported Web Technology Uses</a>.) Authors, companies, technology vendors, or others may document accessibility-supported
       ways of using web content technologies. However, all ways of using technologies in
       the documentation would need to meet the definition of accessibility-supported Web
       content technologies above.

guidelines/terms/20/conforming-alternate-version.html

@@ -64,6 +64,6 @@
       the preferences is accessibility supported.
    </p>
 
-   <p>See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versions</a></p>
+   <p>See <a href="https://www.w3.org/WAI/WCAG22/Understanding/conformance#conforming-alt-versions">Understanding Conforming Alternate Versions</a></p>
 
 </dd>

guidelines/terms/20/text-alternative.html

@@ -10,7 +10,7 @@
       text alternative for the chart indicates that a description follows.
    </p></aside>
 
-   <p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#text-alternatives">Understanding Text Alternatives</a> for more information.
+   <p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG22/Understanding/conformance#text-alternatives">Understanding Text Alternatives</a> for more information.
    </p>
 
 </dd>

techniques/html/H4.html

@@ -6,7 +6,7 @@
       <p>HTML and XHTML</p>
    </section><section id="description"><h2>Description</h2>
       <p>The objective of this technique is to provide a logical tab order when the default tab
-            order does not suffice. Often, <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G59">placing the
+            order does not suffice. Often, <a href="https://www.w3.org/WAI/WCAG22/Techniques/general/G59">placing the
               interactive elements in an order that follows sequences and relationships within the
               content</a> is sufficient and this technique is not necessary. It can be very easy
             to introduce usability bugs when setting the tab order explicitly.</p>

techniques/html/H70.html

@@ -21,7 +21,7 @@
       <p>This technique is appropriate when framesets are already used to organize the content
             of the page; other techniques are preferred for pages that are not already using
             framesets, because many people using assistive technology have trouble with frames . An
-            advisory technique about using noframes is available in <a href="https://www.w3.org/WAI/WCAG21/Understanding/non-text-content">Success Criterion 1.1.1</a>. </p>
+            advisory technique about using noframes is available in <a href="https://www.w3.org/WAI/WCAG22/Understanding/non-text-content">Success Criterion 1.1.1</a>. </p>
       <p>In HTML5 the <code class="el">frame</code> element is marked as obsolete.</p>
    </section><section id="examples"><h2>Examples</h2>
       <section class="example">

techniques/html/H73.html

@@ -27,7 +27,7 @@
                is null. The purpose of a layout table is simply to control the placement of content;
                the table itself is “transparent" to the user. A <code class="att">summary</code> would “break" this
                transparency by calling attention to the table. A null <code class="att">summary</code>
-                 (<code class="att">summary</code>="") on layout tables is acceptable. See <a href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F46">F46</a> for details.</p>
+                 (<code class="att">summary</code>="") on layout tables is acceptable. See <a href="https://www.w3.org/WAI/WCAG22/Techniques/failures/F46">F46</a> for details.</p>
       </div>
    </section><section id="examples"><h2>Examples</h2>
       <section class="example">

techniques/html/H74.html

@@ -62,7 +62,7 @@ <h2>Resources</h2>
                   <a href="https://html.spec.whatwg.org/multipage/syntax.html#the-doctype">HTML - The <code class="language-html">doctype</code></a>.
                </li>
                <li>
-                  <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G134">Validating web pages</a>.
+                  <a href="https://www.w3.org/WAI/WCAG22/Techniques/general/G134">Validating web pages</a>.
                </li>
                <li>
                   <a href="https://validator.w3.org/nu/">The W3C's Nu HTML Checker</a>.

techniques/html/H75.html

@@ -75,7 +75,7 @@ <h3></h3>
                     Entities</a> in Extensible Markup Language (XML) 1.1, W3C Recommendation 04
                   February 2004.</li>
          </ul>
-         <p> For other resources, see <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G134">Validating web
+         <p> For other resources, see <a href="https://www.w3.org/WAI/WCAG22/Techniques/general/G134">Validating web
               pages</a>. </p>
 
    </section></body></html>

techniques/html/H88.html

@@ -56,7 +56,7 @@ <h2>Related Techniques</h2>
       <li><a href="../html/H75">H75</a></li>
    </ul></section><section id="resources"><h2>Resources</h2>
 
-         <p>Refer to the resources section of <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G134">Validating web
+         <p>Refer to the resources section of <a href="https://www.w3.org/WAI/WCAG22/Techniques/general/G134">Validating web
                         pages</a>. </p>
 
    </section></body></html>

understanding/20/parsing.html

@@ -160,7 +160,7 @@ <h3>Sufficient Techniques for Parsing</h3>
 
                   <li>
 
-                     <a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H75" class="html">Ensuring that 
+                     <a href="https://www.w3.org/WAI/WCAG22/Techniques/html/H75" class="html">Ensuring that 
                         web pages are well-formed
                      </a>