Merge pull request #3404 from w3c/Adding-living-standard-link

alastc · web-flow · commit bb56d1180541 · 2023-09-19T13:50:41.000+01:00
Adding informative link - HTML
diff --git a/guidelines/sc/20/parsing.html b/guidelines/sc/20/parsing.html
@@ -13,7 +13,7 @@ <h4>Parsing</h4>
    <p class="note">This Success Criterion should be considered as always satisfied for any content using HTML or XML.</p>
 
    <div class="note">
-      <p>Since this criterion was written, the HTML Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs.</p>
+      <p>Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [[HTML-Living]]</p>
       
       <p>Although the HTML Standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this Success Criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.</p>
       

-Original file line number
+Diff line change
    <p class="note">This Success Criterion should be considered as always satisfied for any content using HTML or XML.p>
    <div class="note">
 -      <p>Since this criterion was written, the HTML Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs.p>
 +      <p>Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [[HTML-Living]]p>
       <p>Although the HTML Standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this Success Criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.p>