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.
@@ -411,7 +411,7 @@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`.
<!-- Avoid doing this! -->
@@ -2258,7 +2258,7 @@
no `role`
- Otherwise, if the `label` is not associted with an element then any `role`,
+ Otherwise, if the `label` is not associated with an element then any `role`,
though generic SHOULD NOT be used.
Naming Prohibited if exposed as the `generic` role, or if exposed as another role which prohibits naming.
@@ -3757,7 +3757,7 @@
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.
diff --git a/tests/img-allowed-roles.html b/tests/img-allowed-roles.html
index a4e26ca..32d7512 100644
--- a/tests/img-allowed-roles.html
+++ b/tests/img-allowed-roles.html
@@ -148,7 +148,7 @@ Test 1
Expected result:
-
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.
+
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.
Expected result:
- 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.
diff --git a/tests/label-element.html b/tests/label-element.html
index 73b9b4e..edfa792 100644
--- a/tests/label-element.html
+++ b/tests/label-element.html
@@ -56,7 +56,7 @@ Tests:
Test 1
Authors MUST NOT use any role or aria-* attribute on the label element when it
- associted with a labelable element.
+ associated with a labelable element.
diff --git a/tests/selectedcontent.html b/tests/selectedcontent.html
index 56a970c..c7f2c25 100644
--- a/tests/selectedcontent.html
+++ b/tests/selectedcontent.html
@@ -91,7 +91,7 @@
Test 2
Expected result:
-
while the use of the seletedcontent element is incorrectly used in this example, the use of ARIA is allowed
+
while the use of the selectedcontent 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.
diff --git a/tests/summary-allowances.html b/tests/summary-allowances.html
index 4d398f9..6e3f155 100644
--- a/tests/summary-allowances.html
+++ b/tests/summary-allowances.html
@@ -83,7 +83,7 @@ Test 1