Fixes #565 -- Refers to WCAG 2.2 consistently throughout (#568)

SHA: 6eaff33
Reason: push, by daniel-montalvo

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

act-rules-format.html

@@ -6,7 +6,7 @@
   <meta content="ED" name="w3c-status">
   <meta content="Bikeshed version 82ce88815, updated Thu Sep 7 16:33:55 2023 -0700" name="generator">
   <link href="https://www.w3.org/TR/act-rules-format/" rel="canonical">
-  <meta content="6760691a53c91da3312b357c75bbbc3033653ae9" name="document-revision">
+  <meta content="6eaff33dc896cceff5757e402ddfa56e2935fa02" name="document-revision">
 <style>
   .rfc2119 {
     text-transform: uppercase;
@@ -608,7 +608,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Accessibility Conformance Testing (ACT) Rules Format 1.1</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2024-07-01">1 July 2024</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2024-08-29">29 August 2024</time></p>
    <details open>
     <summary>More details about this document</summary>
     <div data-fill-with="spec-metadata">
@@ -925,15 +925,15 @@ <h5 class="heading settled" data-level="4.4.1.1" id="conformance-requirements"><
    <div class="note" role="note">
     <p><strong>Note:</strong> In the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines</a> <a data-link-type="biblio" href="#biblio-wcag22" title="Web Content Accessibility Guidelines (WCAG) 2.2">[WCAG22]</a>, success criteria do not evaluate to <code>passed</code>, <code>failed</code> or <code>inapplicable</code>. Rather they can be <em>satisfied</em> (or not). (See the <a href="https://www.w3.org/TR/WCAG22/#dfn-satisfies">WCAG 2.2 definition: satisfies a success criterion</a>.) If a success criterion is <em>not satisfied</em>, a web page can only conform if there is a conforming alternative version, as described in <a href="https://www.w3.org/TR/WCAG22/#cc1">WCAG 2.2 Conformance Requirement 1</a>.</p>
    </div>
-   <aside class="example" id="example-0fd4e5d3">
-    <a class="self-link" href="#example-0fd4e5d3"></a> 
+   <aside class="example" id="example-e101bc5a">
+    <a class="self-link" href="#example-e101bc5a"></a> 
     <header>Example accessibility requirements mapping for a rule that was designed to test if an image button has an accessible name maps success criteria 1.1.1 Non-text content and 4.1.2 Name, Role, Value as conformance requirements:</header>
     <blockquote>
      <ul>
       <li>
         <a href="https://www.w3.org/TR/WCAG22/#non-text-content">Success criterion 1.1.1: Non-text content</a> 
        <ul>
-        <li><strong>Required for conformance</strong> to WCAG 2.0 and WCAG 2.2 level A and higher
+        <li><strong>Required for conformance</strong> to WCAG 2.0, 2.1, and 2.2 level A and higher
         <li>
          Outcome mapping: 
          <ul>
@@ -945,7 +945,7 @@ <h5 class="heading settled" data-level="4.4.1.1" id="conformance-requirements"><
       <li>
         <a href="https://www.w3.org/TR/WCAG22/#name-role-value">Success criterion 4.1.2: Name, Role, Value</a> 
        <ul>
-        <li><strong>Required for conformance</strong> to WCAG 2.0 and WCAG 2.2 level A and higher
+        <li><strong>Required for conformance</strong> to WCAG 2.0, 2.1, and 2.2 level A and higher
         <li>
          Outcome mapping:
          <ul>
@@ -1041,15 +1041,15 @@ <h5 class="heading settled" data-level="4.4.1.2" id="secondary-requirements"><sp
    </aside>
    <h4 class="heading settled" data-level="4.4.2" id="mapping-outside-wcag"><span class="secno">4.4.2. </span><span class="content">Mapping Outside WCAG</span><a class="self-link" href="#mapping-outside-wcag"></a></h4>
    <p>ACT Rules can be used to test accessibility requirements that are not part of a W3C accessibility standard, such as accessibility requirements in <a href="https://www.w3.org/TR/html/">Hypertext Markup Language</a> <a data-link-type="biblio" href="#biblio-html" title="HTML Standard">[HTML]</a>, or tests in a methodology like <a href="https://disic.github.io/rgaa_referentiel_en/criteria.html">RGAA 3 2016</a>. An ACT Rule <em class="rfc2119">must</em> indicate whether or not the <a data-link-type="dfn" href="#accessibility-requirement" id="ref-for-accessibility-requirement⑤">accessibility requirement</a> it maps to is required for conformance in its <a data-link-type="dfn" href="#accessibility-requirements-document" id="ref-for-accessibility-requirements-document④">accessibility requirements document</a>. Examples of accessibility requirements that are not required for conformance are WCAG sufficient techniques, or a company style guide that includes both requirements and optional "best practices". The distinction between what is required and what is optional has to be clear.</p>
-   <aside class="example" id="example-18e1d695">
-    <a class="self-link" href="#example-18e1d695"></a> 
+   <aside class="example" id="example-341c15ad">
+    <a class="self-link" href="#example-341c15ad"></a> 
     <header>Example accessibility requirements mapping for a rule that tests that each <code>img</code> element has an <code>alt</code> attribute:</header>
     <blockquote>
      <ul>
       <li>
         <a href="https://www.w3.org/TR/WCAG20-TECHS/H37.html">Technique H37: Using alt attributes on img elements</a> 
        <ul>
-        <li><strong>Not required</strong> for conformance to WCAG 2.0 and WCAG 2.2 at any level
+        <li><strong>Not required</strong> for conformance to WCAG 2.0, 2.1, and 2.2 at any level
         <li>
          Outcome mapping: 
          <ul>