chore: fix some typos flagged by cSpell

index.html

@@ -119,7 +119,7 @@
         </li>
         <li>
           <a href="https://github.com/w3c/html-aria/pull/469">29 June 2023 - Addition:</a>
-          Update the <a href="#el-s">`s`</a> element allowed roles to indicate use of `role=deletion` on the element would be considered redundnat.
+          Update the <a href="#el-s">`s`</a> element allowed roles to indicate use of `role=deletion` on the element would be considered redundant.
         </li>
         <li>
           <a href="https://github.com/w3c/html-aria/pull/435">31 May 2023 - Correction:</a>
@@ -326,7 +326,7 @@ <h3>
         </pre>
         <p>
           An author would need to take additional steps to ensure the default functionality and presentation of 
-          the `button` was removed, and even doing so may still not be enough to fully supress the element's 
+          the `button` was removed, and even doing so may still not be enough to fully suppress the element's 
           implicit features depending on how the user chooses to engage with the web page. E.g., by turning on 
           Windows high contrast themes, or viewing the web page in a browser's reader mode.
         </p>
@@ -411,7 +411,7 @@ <h3>Adhere to the rules of ARIA</h3>
         <p>
           In the following example, rather than using a `generic` role, authors are advised to use a `div` in 
           place of the `article` element. If changing the HTML element is not possible, specifying a role of 
-          `presentation` or `none` would be acceptable alternaties to remove the implicit role of the `article`.
+          `presentation` or `none` would be acceptable alternatives to remove the implicit role of the `article`.
         </p>
         <pre class="HTML example" title="Do not specify elements as generic">
           &lt;!-- Avoid doing this! -->
@@ -2258,7 +2258,7 @@ <h2 id="docconformance">
                 <a><strong class="nosupport">no `role`</strong></a>
               </p>
               <p>
-                Otherwise, if the `label` is not associted with an element then <a><strong>any `role`</strong></a>, 
+                Otherwise, if the `label` is not associated with an element then <a><strong>any `role`</strong></a>, 
                 though <code><a href="#index-aria-generic">generic</a></code> SHOULD NOT be used.
               </p>
               <p><a>Naming Prohibited</a> if exposed as the `generic` role, or if exposed as another role which prohibits naming.</p>
@@ -3757,7 +3757,7 @@ <h3 id="docconformance-attr">
                 </div>
                 <div class="note">
                   Using `aria-hidden="true"` on an element that has the `hidden` attribute is at best an unnecessary redundancy. At worst its usage can 
-                  prevent access to the content if the `hidden` attribute's default UA style of `display: none` has been purposeuflly overwritten by an author or user style sheet.
+                  prevent access to the content if the `hidden` attribute's default UA style of `display: none` has been purposefully overwritten by an author or user style sheet.
                   Finally, if the `hidden` attribute is in the Hidden Until Found state, the use of `aria-hidden=true` will prevent this content from being discoverable to users 
                   of assistive technology when it is found via a browser's in-page find feature and visually rendered to users.
                 </div>

tests/img-allowed-roles.html

@@ -148,7 +148,7 @@ <h3>Test 1</h3>
 				</div>
 
 				<p><strong>Expected result:</strong>
-				<br>No failures for use of ARIA roles would be flagged for any of the above examples. Use of img on a named image element is NOT RECOMMENDED. Confornamce checkers may indicate this as a warning.</p>
+				<br>No failures for use of ARIA roles would be flagged for any of the above examples. Use of img on a named image element is NOT RECOMMENDED. Conformance checkers may indicate this as a warning.</p>
 			</div>
 
 			<div class="widgetDemo">

tests/input-image-reset-submit.html

@@ -124,7 +124,7 @@ <h3>
 				</div>
 
 				<p><strong>Expected result:</strong>
-					These test cases would pass checks for an allowed role, but other failures would be expected for the instances where the elements are not contained or owned by their expected accessibility parents, or where they lack other expected properties required by authors. Note: there is no need to use a role=button on one of these elements, so while it's use is not recommended due to unnecessary redundncy, it is also not likely to cause issues.
+					These test cases would pass checks for an allowed role, but other failures would be expected for the instances where the elements are not contained or owned by their expected accessibility parents, or where they lack other expected properties required by authors. Note: there is no need to use a role=button on one of these elements, so while it's use is not recommended due to unnecessary redundancy, it is also not likely to cause issues.
 				</p>
 			</div>
 

tests/label-element.html

@@ -56,7 +56,7 @@ <h2>Tests:</h2>
 				<h3>Test 1</h3>
 				<p>
                     Authors MUST NOT use any <code>role</code> or <code>aria-*</code> attribute on the <code>label</code> element when it
-                    associted with a labelable element.</p>
+                    associated with a labelable element.</p>
 
 				<div class="testcase">
           <p>

tests/selectedcontent.html

@@ -91,7 +91,7 @@ <h3>Test 2</h3>
 				</div>
 
 				<p><strong>Expected result:</strong>
-				    <br> while the use of the <code>seletedcontent</code> element is incorrectly used in this example, the use of ARIA is allowed
+				    <br> while the use of the <code>selectedcontent</code> element is incorrectly used in this example, the use of ARIA is allowed
                     so authors may correct for misuse of the element, thus no errors related to the use of ARIA attributes should be flagged in this case.</p>
 			</div>
 		</div>

tests/summary-allowances.html

@@ -83,7 +83,7 @@ <h3>Test 1</h3>
 
       <div class="widgetDemo">
          <h3>Test 2</h3>
-				<p>Authors MAY specify any role on a summary element, so long as that summary element is not the 'summay for its parent details'.</p>
+				<p>Authors MAY specify any role on a summary element, so long as that summary element is not the 'summary for its parent details'.</p>
 
 				<div class="testcase">
 					<p>The summary elements beyond the first instance do not pass the algorithm to be a summary for its parent details,