Update to new WAI website links

2024/aria-charter.html

@@ -211,7 +211,7 @@ <h2>
         Deliverables
       </h2>
 
-      <p>In order to maximize the likelihood of achieving the success criteria described below, the ARIA Working Group will follow a <a href="https://www.w3.org/WAI/ARIA/workflow">work flow</a> designed to see each feature from its <a href="https://www.w3.org/WAI/ARIA/roadmap">road map</a> through to completion, with ARIA feature development, platform accessibility API mapping, implementation, <a href="https://github.com/w3c/testing-how-to/#test-as-you-commit-pointer-event-whatwg-webperf">testing</a>, and authoring guidance taking place at the same time.</p>
+      <p>In order to maximize the likelihood of achieving the success criteria described below, the ARIA Working Group will follow a <a href="https://www.w3.org/WAI/about/groups/ariawg/workflow">work flow</a> designed to see each feature from its <a href="https://www.w3.org/WAI/about/groups/ariawg/roadmap">road map</a> through to completion, with ARIA feature development, platform accessibility API mapping, implementation, <a href="https://github.com/w3c/testing-how-to/#test-as-you-commit-pointer-event-whatwg-webperf">testing</a>, and authoring guidance taking place at the same time.</p>
       <p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to
         become a Recommendation, or otherwise reach a stable state.
     </p>
@@ -365,7 +365,7 @@ <h3>
         <h3>
           Other Deliverables
         </h3>
-        <p>As described above and in the <a href="https://www.w3.org/WAI/ARIA/workflow">work flow</a>, the Working Group will create a test suite and implementation report for each specification. In addition, other non-normative documents may be created such as use case and requirement documents.</p>
+        <p>As described above and in the <a href="https://www.w3.org/WAI/about/groups/ariawg/workflow">work flow</a>, the Working Group will create a test suite and implementation report for each specification. In addition, other non-normative documents may be created such as use case and requirement documents.</p>
         <p>The Working Group intends to collaborate with other Working Groups and relevant stakeholders to update ARIA modules as needed.</p>
         <p> The Working Group will also produce WAI-ARIA Authoring Practices, a comprehensive support resource for the WAI-ARIA suite but not published as a Technical Report itself. In further support of that guidance, the Working Group will work with developers of the <a href="https://aria-at.w3.org/">ARIA-AT application</a> to help achieve consistent implementation of the guidance across tools.</p>
         <p>Other non-normative documents may be created such as: </p>
@@ -378,7 +378,7 @@ <h3>
 
       <section id="timeline">
         <h3>Timeline</h3>
-        <p>The Working Group maintains a <a href="https://www.w3.org/WAI/ARIA/project">detailed project plan</a> that provides target dates, updated as needed.</p>
+        <p>The Working Group maintains a <a href="https://www.w3.org/WAI/about/groups/ariawg/planning">detailed project plan</a> that provides target dates, updated as needed.</p>
       </section>
     </section>
 
@@ -520,7 +520,7 @@ <h2>
       </p>
       <p>
         Information about the group (including details about deliverables, issues, actions, status, participants, and
-        meetings) will be available from the <a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications
+        meetings) will be available from the <a href="https://www.w3.org/WAI/about/groups/ariawg/">Accessible Rich Internet Applications
           Working Group home page.</a>
       </p>
       <p>
@@ -651,8 +651,8 @@ <h3>
                       <li>Clarified dependency on other groups for several ARIA modules;</li>
                       <li>Updated Success Criteria to describe successful testing procedure for ARIA and AAMs;</li>
                       <li>Removed User Context as a deliverable; the evolution of it, Personalization Semantics; is being transferred to the <a href="https://www.w3.org/WAI/APA/">APA Working Group</a>;</li>
-                      <li>Produced annual dot-release publications of ARIA and supporting specifications beginning Q4 2019, with features prioritized according to the <a href="https://www.w3.org/WAI/ARIA/roadmap">roadmap</a>;</li>
-                      <li>Adopted a concrete <a href="https://www.w3.org/WAI/ARIA/workflow">workflow</a> for feature acceptance to add predictability to timelines;</li>
+                      <li>Produced annual dot-release publications of ARIA and supporting specifications beginning Q4 2019, with features prioritized according to the <a href="https://www.w3.org/WAI/about/groups/ariawg/roadmap">roadmap</a>;</li>
+                      <li>Adopted a concrete <a href="https://www.w3.org/WAI/about/groups/ariawg/workflow">workflow</a> for feature acceptance to add predictability to timelines;</li>
                       <li>Clarified participation and communication procedures;</li>
                       <li>Added licensing section to specify the W3C Document license for Recommendation-track deliverables and the W3C Software and Document license for others; </li>
                       <li>Staff effort increased from .25 FTE to .4 FTE to provide additional support for project management, inter-group coordination on related ARIA specifications, and publication.</li>