Change <ol> to <ul> when no order is intended

The understanding documents are oddly inconsistent when it comes to use of `<ol>` and `<ul>`. This edits all cases (particularly in the newer 2.2 understanding docs, but some older ones too) where a list does not have an explicit order and should just be an unordered list

conformance-challenges/index.html

@@ -1155,7 +1155,7 @@ <h3>Success Criteria Needing Special Treatment in Non-Accessibility Supported En
 	braille display in the device to support deaf-blind users, and then maintaining those braille displays to ensure their mechanisms don&apos;t get damaged).
 	</p>
 
-                <ol>
+        <ul>
 			<li><a href="https://www.w3.org/TR/WCAG21/#non-text-content">Non-Text Content</a> (Success Criterion 1.1.1)</li>
 			<li><a href="https://www.w3.org/TR/WCAG21/#audio-only-and-video-only-prerecorded">Audio-only and video-only (Prerecorded)</a> (Success Criterion 1.2.1)</li>
 		    <li><a href="https://www.w3.org/TR/WCAG21/#audio-description-or-media-alternative-prerecorded">Audio description or media alternative (Prerecorded)</a> (Success Criterion 1.2.3)</li>
@@ -1171,7 +1171,7 @@ <h3>Success Criteria Needing Special Treatment in Non-Accessibility Supported En
 		    <li><a href="https://www.w3.org/TR/WCAG21/#error-identification">Error Identification</a> (Success Criterion 3.3.1)</li>
 		    <li><a href="https://www.w3.org/TR/WCAG21/#parsing">Parsing</a> (Success Criterion 4.1.1)</li>
 		    <li><a href="https://www.w3.org/TR/WCAG21/#name-role-value">Name, Role, Value</a> (Success Criterion 4.1.2)</li>
-		</ol>
+		</ul>
 </section>
       </section>
 

guidelines/sc/22/accessible-authentication-minimum.html

@@ -19,10 +19,10 @@ <h4>Accessible Authentication (Minimum)</h4>
 
     <p class="note">"Object recognition" and "Personal content" may be represented by images, video, or audio.</p>
     <div class="note">Examples of mechanisms that satisfy this criterion include:
-        <ol>
+        <ul>
             <li>support for password entry by password managers to reduce memory need, and</li>
             <li>copy and paste to reduce the cognitive burden of re-typing.</li>
-        </ol>
+        </ul>
     </div>
 
  </section>

guidelines/terms/20/changes-of-context.html

@@ -7,7 +7,7 @@
 
    <p>Changes in context include changes of:</p>
 
-   <ol>
+   <ul>
 
       <li><a>user agent</a>;
       </li>
@@ -20,7 +20,7 @@
       <li><a>content</a> that changes the meaning of the <a>Web page</a>
       </li>
 
-   </ol>
+   </ul>
 
    <p class="note">A change of content is not always a change of context. Changes in content, such as
       an expanding outline, dynamic menu, or a tab control do not necessarily change the

guidelines/terms/20/general-flash-and-red-flash-thresholds.html

@@ -4,7 +4,7 @@
    <p>a <a>flash</a> or rapidly changing image sequence is below the threshold (i.e., content <strong>passes</strong>) if any of the following are true:
    </p>
 
-   <ol>
+   <ul>
 
       <li>there are no more than three <strong>general flashes</strong> and / or no more than three <strong>red flashes</strong> within any one-second period; or
       </li>
@@ -14,7 +14,7 @@
          degree visual field on the screen) at typical viewing distance
       </li>
 
-   </ol>
+   </ul>
 
    <p>where:</p>
 

guidelines/terms/20/structure.html

@@ -1,14 +1,14 @@
 <dt><dfn>structure</dfn></dt>
 <dd>
 
-   <ol>
+   <ul>
 
       <li>The way the parts of a <a>Web page</a> are organized in relation to each other; and
       </li>
 
       <li>The way a collection of <a>Web pages</a> is organized
       </li>
 
-   </ol>
+   </ul>
 
 </dd>

understanding/20/headings-and-labels.html

@@ -116,14 +116,14 @@ <h2>Techniques for Headings and Labels</h2>
       <section id="sufficient">
          <h3>Sufficient Techniques for Headings and Labels</h3>
 
-         <ol>
+         <ul>
             <li>
                <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G130" class="general">Providing descriptive headings</a>
             </li>
             <li>
                <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G131" class="general">Providing descriptive labels</a>
             </li>
-         </ol>
+         </ul>
 
 
          <div class="note">

understanding/20/use-of-color.html

@@ -105,7 +105,7 @@ <h2>Intent of Use of Color</h2>
 
         <p>Most user agents provide users with a color-only cue that a link has been previously activated by them ("visited"). However, several technical constraints result in authors having very limited control over these color-only indications of visited links.  The technical constraints are as follows:</p>
 
-        <ol>
+        <ul>
            <li> 
               User agents constrain the exposure of a link's visited state due to <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector">privacy concerns</a>. Author queries to user agents will indicate all links have not been visited.
            </li>
@@ -119,7 +119,7 @@ <h2>Intent of Use of Color</h2>
               Authors also cannot set the visited state of links. The anchor element does not include a "visited" attribute; therefore the author has no ability to alter the state through an attribute setting. As such, authors cannot achieve <a href="info-and-relationships">1.3.1 Info and Relationships</a> or
               <a href="name-role-value">4.1.2 Name, Role, Value</a> in regard to visited links.
            </li>
-        </ol>
+        </ul>
 
          <p>For these reasons, setting or conveying a link's visited status is not an author responsibility. Where color alone distinguishes between visited and unvisited links, it does not result in a failure of this Success Criterion, even where the contrast between the two link colors is below 3:1. Note that authors must continue to ensure that all text links meet contrast minimums against the page background (SC 1.4.3).</p>
       </div>

understanding/21/content-on-hover-or-focus.html

@@ -20,11 +20,11 @@ <h2>In brief</h2>
 		<section id="intent">
 			<h2>Intent</h2>
 			<p>Additional content that appears and disappears in coordination with keyboard focus or pointer hover often leads to accessibility issues. Reasons for such issues include:</p>
-			<ol>
+			<ul>
 			<li>the user may not have intended to trigger the interaction</li>
 			<li>the user may not know new content has appeared</li>
 			<li>the new content may intefere with a user's ability to do a task</li>
-		</ol>
+		</ul>
 
 			<p>Examples of such interactions can include custom tooltips, sub-menus and other nonmodal popups which display on hover and focus. The intent of this success criterion is to ensure that authors who cause additional content to appear and disappear in this manner must design the interaction in such a way that users can:</p>
 				<ul>

understanding/21/interruptions-minimum.html

@@ -11,12 +11,12 @@ <h1>Understanding Interruptions (Minimum)</h1>
 			<h2>Intent</h2>
 			<p>The intent of this Success Criterion is to avoid interrupting users during their interaction with a Web page. When users are distracted, especially users with impaired attention or memory, they may forget what they were doing and abandon the task. This can happen even when the original task is extremely important.</p>
 			<p>Where a site may generate interruptions, the user must be able to postpone or suppress them, such that: </p>
-			<ol>
+			<ul>
 				<li>Popups and other interruptions can be easily delayed or turned off [Editor: do we need a definition for popup?]</li>
 				<li>Media events can be easily delayed or turned off [Editor: how is this different from Pause, Hide, Stop?]</li>
 				<li>Chat functions can be easily turned off and on again </li>
 				<li>Non-critical messages can easily be turned off and on again </li>
-			</ol>
+			</ul>
 			<p>Changes in content that are not initiated by the user must be avoided. Secondary content (such as special offers or complementary material) should be easily identified, controlled and turned off.</p>
 			<p>Other potential distractions are covered by existing WCAG Success Criteria <a href="pause-stop-hide" class="sc">Pause, Stop, Hide</a>, <a href="audio-control" class="sc">Audio Control</a>, <a href="three-flashes-or-below-threshold" class="sc">Three Flashes or Below Threshold</a>, <a href="low-or-no-background-audio" class="sc">Low or No Background Audio</a>, <a href="timing-adjustable" class="sc">Timing Adjustable</a>. These success criteria are aimed at specific considerations which can have repercussions on certain user groups, but also have a broader effect of reducing distractions for all users.</p>
 

understanding/21/text-spacing.html

@@ -95,10 +95,10 @@ <h2>Benefits</h2>
       <section id="examples">
          <h2>Examples</h2>
         <p>When spacing is being overridden to the SC's metrics:</p>
-        <ol>
+        <ul>
             <li>Text fits within the bounds of its containing box without being cut off.</li>
             <li>Text fits within the bounds of its containing box without overlapping other boxes.</li>
-         </ol>
+         </ul>
       </section>
       <section id="resources">
          <h2>Resources</h2>
@@ -108,11 +108,11 @@ <h3>Research</h3>
       		<section>
          <h4 id="lang">Languages and Scripts</h4>
          <p>Roughly 480 different languages and scripts <a href="https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2018Feb/0001.html">have been tested</a>.  Maximum spacing adjustments allowed by the SC were set on the following 3 pages:</p>
-         <ol>
+         <ul>
            <li><a href="http://www.geonames.de/languages.html">Languages in their own writing systems</a></li>
             <li><a href="https://www.omniglot.com/language/names.htm">Online Encyclopedia of writing systems and languages &#8211; language names</a></li>
            <li><a href="https://www.omniglot.com/language/phrases/index.htm">Universal Declaration of Human Rights (Article 1)</a></li>
-         </ol>
+         </ul>
       		</section>
       			<section>
          <h4 id="results">Results</h4>

understanding/22/accessible-authentication-enhanced.html

@@ -95,7 +95,7 @@ <h2>Techniques for Accessible Authentication (Enhanced)</h2>
          <h3>Sufficient Techniques for Accessible Authentication</h3>
 
 
-         <ol>
+         <ul>
             <li>
                 <a href="../../techniques/general/G218.html" class="general">Email link authentication</a>
             </li>
@@ -111,7 +111,7 @@ <h3>Sufficient Techniques for Accessible Authentication</h3>
             <li>
                 Using two techniques to provide 2 factor authentication (Potential future technique)
             </li>
-         </ol>
+         </ul>
 
       </section>
 
@@ -122,11 +122,11 @@ <h3>Additional Techniques (Advisory) for Accessible Authentication (Enhanced)</h
 
       <section id="failure">
         <h3>Failures for Accessible Authentication (Enhanced)</h3>
-        <ol>
+        <ul>
            <li>
               <a href="../../techniques/failures/F109.html">Failure of Success Criterion 3.3.8 and 3.3.9 due to forcing transcription of individual password characters</a>
            </li>
-        </ol>
+        </ul>
      </section>
 
    </section>

understanding/22/accessible-authentication-minimum.html

@@ -36,11 +36,11 @@ <h2>Accessible Authentication (Minimum) Success Criteria text</h2>
             </dl>
             <p class="note">"Object recognition" and "Personal content" may be represented by images, video, or audio.</p>
             <div class="note">Examples of mechanisms that satisfy this criterion include:
-                <ol>
+                <ul>
                     <li>support for password entry by password managers to reduce memory need;</li>
                     <li>copy and paste to reduce the cognitive burden of re-typing;</li>
                     <li>Support for on-device biometric authentication.</li>
-                </ol>
+                </ul>
             </div>
 
         </blockquote>
@@ -168,7 +168,7 @@ <h2>Techniques for Accessible Authentication</h2>
         <section id="sufficient">
             <h3>Sufficient Techniques for Accessible Authentication</h3>
 
-            <ol>
+            <ul>
                 <li>
                     <a href="../../techniques/general/G218" class="general">Email link authentication</a>
                 </li>
@@ -184,7 +184,7 @@ <h3>Sufficient Techniques for Accessible Authentication</h3>
                 <li>
                     Using two techniques to provide 2 factor authentication (Potential future technique)
                 </li>
-            </ol>
+            </ul>
 
         </section>
 
@@ -195,11 +195,11 @@ <h3>Additional Techniques (Advisory) for Accessible Authentication</h3>
 
         <section id="failure">
             <h3>Failures for Accessible Authentication (Minimum)</h3>
-            <ol>
+            <ul>
                <li>
                   <a href="../../techniques/failures/F109.html">Failure of Success Criterion 3.3.8 and 3.3.9 due to forcing transcription of individual password characters</a>
                </li>
-            </ol>
+            </ul>
          </section>
 
     </section>

understanding/22/consistent-help.html

@@ -150,9 +150,9 @@ <h2>Techniques for Consistent Help</h2>
 
       <section id="sufficient">
          <h3>Sufficient Techniques for Consistent Help</h3>
-         <ol>
+         <ul>
             <li><a href="../../techniques/general/G220" class="general">Provide a contact-us link in a consistent location</a></li>
-         </ol>
+         </ul>
       </section>
 
       <section id="advisory">

understanding/22/dragging-movements.html

@@ -110,11 +110,11 @@ <h2>Techniques for Dragging</h2>
       <section id="sufficient">
          <h3>Sufficient Techniques for Dragging Movements</h3>
 
-         <ol>
+         <ul>
             <li>
                 <a href="../../techniques/general/G219" class="general">Ensuring that an alternative is available for dragging movements that operate on content</a>
             </li>
-         </ol>
+         </ul>
 
       </section>
 

understanding/22/focus-appearance.html

@@ -464,7 +464,7 @@ <h2>Techniques</h2>
         <section id="sufficient">
             <h3>Sufficient Techniques</h3>
 
-            <ol>
+            <ul>
                 <li>
                     <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G195" class="general">Using an author-supplied, highly visible focus indicator</a>
                 </li>
@@ -474,16 +474,16 @@ <h3>Sufficient Techniques</h3>
                 <li>
                     <a href="../../techniques/css/C41">Creating a contrasting focus indicator inside the component</a>
                 </li>
-            </ol>
+            </ul>
         </section>
 
         <section id="failure">
             <h3>Failures</h3>
-            <ol>
+            <ul>
                 <li>
                     Using a CSS border for inline text which can wrap (Potential future technique)
                 </li>
-            </ol>
+            </ul>
         </section>
     </section>
 </body>

understanding/22/focus-not-obscured-enhanced.html

@@ -59,9 +59,9 @@ <h2>Resources</h2>
   <h2>Techniques for Focus Not Obscured (Enhanced)</h2>
   <section id="sufficient">
     <h3>Sufficient Techniques</h3>
-    <ol>
+    <ul>
       <li> <a href="../../techniques/css/C43">C43: Using CSS scroll-padding to un-obscure content</a></li>
-    </ol>
+    </ul>
   </section>
   <section id="advisory">
     <h3>Additional Techniques (Advisory)</h3>

understanding/22/focus-not-obscured-minimum.html

@@ -173,11 +173,11 @@ <h2>Techniques for Focus Not Obscured (Minimum)</h2>
       <section id="sufficient">
          <h3>Sufficient Techniques</h3>
 
-         <ol>
+         <ul>
             <li>
               <a href="../../techniques/css/C43">C43: Using CSS scroll-padding to un-obscure content</a>
             </li>
-         </ol>
+         </ul>
 
       </section>
 
@@ -188,11 +188,11 @@ <h3>Additional Techniques (Advisory)</h3>
 
       <section id="failure">
          <h3>Failures</h3>
-         <ol>
+         <ul>
             <li>
                <a href="../../techniques/failures/F110">F110 - Failure due to a sticky footer hiding focused elements</a>
             </li>
-         </ol>
+         </ul>
       </section>
 
    </section>

understanding/22/target-size-minimum.html

@@ -193,11 +193,11 @@ <h2>Techniques for Target Size (Minimum)</h2>
         <section id="sufficient">
             <h3>Sufficient Techniques for Target Size (Minimum)</h3>
 
-            <ol>
+            <ul>
                 <li>
                     <a href="../../techniques/css/C42" class="css">Using min-height and min-width to ensure sufficient target spacing</a>
                 </li>
-            </ol>
+            </ul>
 
         </section>