[wg/aria] Various improvements. Remove WebPlatformWG coordination

2024/aria-charter.html

@@ -74,7 +74,7 @@
 
 
   <main>
-    <h1 id="title">PROPOSED Accessible Rich Internet Applications Working Group Charter</h1>
+    <h1 id="title">DRAFT Accessible Rich Internet Applications Working Group Charter</h1>
     <!-- delete PROPOSED after AC review completed -->
 
     <p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/groups/wg/aria">Accessible Rich Internet Applications Working Group</a> is to enhance the
@@ -398,7 +398,7 @@ <h2>Success Criteria</h2>
           them. For specifications which are not split apart in this fashion, no platform will be dropped out of the
           specification without prior consultation with that platform's owners.</li>
       </ul>
-      <p> Modules that reach <a href="https://www.w3.org/2020/Process-20200915/#rec-publication">W3C Recommendation</a> are
+      <p> Modules that reach <a href="https://www.w3.org/policies/process/#transition-rec">W3C Recommendation</a> are
         considered successful when all of the following are present:</p>
       <ul>
         <li>Production of stable documents addressing the work items listed in the Deliverables section</li>
@@ -424,7 +424,7 @@ <h2>Coordination</h2>
       <p>For all specifications, this Working Group will seek <a
           href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
         accessibility, internationalization, privacy, and security with the relevant Working and
-        Interest Groups, and with the <a href="https://www.w3.org/2001/tag/"
+        Interest Groups, and with the <a href="https://www.w3.org/groups/other/tag/"
           title="Technical Architecture Group">TAG</a>.
         Invitation for review must be issued during each major standards-track document transition, including
         <a href="https://www.w3.org/policies/process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
@@ -443,31 +443,29 @@ <h2>Coordination</h2>
       <section>
         <h3 id="w3c-coordination">W3C Groups</h3>
         <dl>
-          <dt><a href="http://www.w3.org/WAI/GL/">Accessibility Guidelines (WCAG) Working Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/wg/ag/">Accessibility Guidelines (WCAG) Working Group</a></dt>
           <dd>Work on HTML 5 and ARIA <a href="http://www.w3.org/WAI/WCAG22/Techniques/">Techniques for WCAG 2.2</a>.</dd>
-          <dt><a href="https://www.w3.org/WAI/APA/">Accessible Platform Architectures Working Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/wg/apa/">Accessible Platform Architectures Working Group</a></dt>
           <dd>Collaborate on overall accessibility architectural aspects of ARIA.</dd>
-          <dt><a href="http://www.w3.org/Style/CSS">CSS Working Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/wg/css/">CSS Working Group</a></dt>
           <dd>Coordinate media queries support for context awareness. Provide requirements for future WAI-ARIA support. Coordinate on general CSS accessibility topics. Include CSS-AAM requirements in the hTML-AAM specification.</dd>
-          <dt><a href="https://www.w3.org/publishing/groups/epub-wg/">EPUB 3 Working Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/wg/pm/">Publishing Maintenance Working Group</a></dt>
           <dd>Coordinate development of digital publishing roles and EPUB Accessibility.</dd>
-          <dt><a href="https://www.w3.org/International/">Internationalization Working Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/wg/i18n-core/">Internationalization Working Group</a></dt>
           <dd>Coordinate how to address accessibility and internationalization in W3C specs.</dd>
-          <dt><a href="https://tag.w3.org/">Technical Architecture Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/other/tag/">Technical Architecture Group</a></dt>
           <dd>Confirm the ARIA relationship to various host languages is interoperable and forwards-compatible.</dd>
-          <dt><a href="http://www.w3.org/Privacy/">Privacy Interest Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/ig/privacy/">Privacy Interest Group</a></dt>
           <dd>Identify and resolve privacy implications of features of the technology that capture user environment information, particularly specific assistive technology being used, in order to customize the user experience.</dd>
-          <dt><a href="http://www.w3.org/Graphics/SVG/">SVG Working Group</a></dt>
+          <dt><a href="https://www.w3.org/groups/wg/svg/">SVG Working Group</a></dt>
           <dd>Coordinate on graphics role module and SVG Accessibility API Mappings.</dd>
-          <dt><a href="http://www.w3.org/WebPlatform/WG/">Web Platform Working Group</a></dt>
-          <dd>Implementation of ARIA and HTML Accessibility API Mappings, coordinate development of APIs that address accessibility use cases, and work on other joint deliverables including <a href="http://www.w3.org/TR/2dcontext2/">Canvas 2D Context</a>.</dd>
         </dl>
       </section>
 
       <section>
         <h3 id="external-coordination">External Organizations</h3>
         <dl>
-          <dt><a href="http://www.daisy.org/">DAISY Consortium</a></dt>
+          <dt><a href="https://daisy.org/">DAISY Consortium</a></dt>
           <dd>Coordinate on publishing and math accessibility API mappings.</dd>
           <dt><a href="http://www.imsglobal.org/">IMS Global Learning Consortium</a></dt>
           <dd>Coordinate on features that impact e-learning and testing.</dd>
@@ -500,7 +498,7 @@ <h2 id="participation">
       </p>
       <p>Participants in the group are required (by the <a
           href="https://www.w3.org/policies/process/#ParticipationCriteria">W3C Process</a>) to follow the
-        W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
+        W3C <a href="https://www.w3.org/policies/code-of-conduct/">Code of Conduct</a>.</p>
     </section>