Ensure 411 ids are unique

Author: daniel-montalvo

update-wcag-json.mjs

@@ -23,7 +23,7 @@ compatible.successcriteria[0].handle =
 const parsing21 = wcag21.principles[3].guidelines[0].successcriteria[0];
 parsing21.id += "21";
 parsing21.handle += " (WCAG 2.1)";
-console.log(parsing21.content);
+parsing21.content = parsing21.content.replace(/-27/g, "-27-411-21");
 compatible.successcriteria.unshift(parsing21);
 
 // Prune unneeded fields

wcag.json

@@ -723,7 +723,7 @@
                         {
                             "id": "parsing21",
                             "num": "4.1.1",
-                            "content": "<p>In content implemented using markup languages, elements have complete start and end\n      tags, elements are nested according to their specifications, elements do not contain\n      duplicate attributes, and any IDs are unique, except where the specifications allow\n      these features.\n   </p>\n   \n   <div class=\"note\" role=\"note\" id=\"issue-container-generatedID-26\"><div role=\"heading\" class=\"note-title marker\" id=\"h-note-26\" aria-level=\"5\"><span>Note 1</span></div><p class=\"\">This success criterion should be considered as always satisfied for any content using HTML or XML.</p></div>\n\n   <div class=\"note\" role=\"note\" id=\"issue-container-generatedID-27\"><div role=\"heading\" class=\"note-title marker\" id=\"h-note-27\" aria-level=\"5\"><span>Note 2</span></div><div class=\"\">\n      <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. [<cite><a href=\"https://www.w3.org/TR/WCAG21/#bib-html\" title=\"HTML Standard\">HTML</a></cite>]</p>\n      \n      <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>\n      \n      <p>Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different success criteria and should be reported under those criteria rather than as issues with 4.1.1.</p>\n   </div></div>",
+                            "content": "<p>In content implemented using markup languages, elements have complete start and end\n      tags, elements are nested according to their specifications, elements do not contain\n      duplicate attributes, and any IDs are unique, except where the specifications allow\n      these features.\n   </p>\n   \n   <div class=\"note\" role=\"note\" id=\"issue-container-generatedID-26\"><div role=\"heading\" class=\"note-title marker\" id=\"h-note-26\" aria-level=\"5\"><span>Note 1</span></div><p class=\"\">This success criterion should be considered as always satisfied for any content using HTML or XML.</p></div>\n\n   <div class=\"note\" role=\"note\" id=\"issue-container-generatedID-27-411-21\"><div role=\"heading\" class=\"note-title marker\" id=\"h-note-27-411-21\" aria-level=\"5\"><span>Note 2</span></div><div class=\"\">\n      <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. [<cite><a href=\"https://www.w3.org/TR/WCAG21/#bib-html\" title=\"HTML Standard\">HTML</a></cite>]</p>\n      \n      <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>\n      \n      <p>Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different success criteria and should be reported under those criteria rather than as issues with 4.1.1.</p>\n   </div></div>",
                             "handle": "Parsing (WCAG 2.1)",
                             "level": "A"
                         },