Merge pull request #1777 from w3c/Issue1758-conformance-requirements

alastc · web-flow · commit d122d55e2234 · 2022-01-04T17:28:22.000Z
Conformance requirements, not criteria
diff --git a/guidelines/terms/20/accessibility-supported.html b/guidelines/terms/20/accessibility-supported.html
@@ -84,7 +84,7 @@
    </p>
    
    <p class="note">Web technologies can be used in ways that are not accessibility supported as long
-      as they are not <a>relied upon</a> and the page as a whole meets the conformance requirements, including <a href="#cc4">Conformance Criterion 4</a> and <a href="#cc5">Conformance Criterion 5</a>, are met.
+      as they are not <a>relied upon</a> and the page as a whole meets the conformance requirements, including <a href="#cc4">Conformance Requirement 4</a> and <a href="#cc5">Conformance Requirement 5</a>.
    </p>
    
    <p class="note">When a <a>Web Technology</a> is used in a way that is "accessibility supported," it does not imply that the entire

-Original file line number
+Diff line change
    p>
    <p class="note">Web technologies can be used in ways that are not accessibility supported as long
 -      as they are not <a>relied upona> and the page as a whole meets the conformance requirements, including <a href="#cc4">Conformance Criterion 4a> and <a href="#cc5">Conformance Criterion 5a>, are met.
 +      as they are not <a>relied upona> and the page as a whole meets the conformance requirements, including <a href="#cc4">Conformance Requirement 4a> and <a href="#cc5">Conformance Requirement 5a>.
    p>
    <p class="note">When a <a>Web Technologya> is used in a way that is "accessibility supported," it does not imply that the entire