Merge pull request w3c#775 from w3c/iadawn-fix404s

Fix a variety of 404s

pages/about/groups/agwg.md

@@ -65,7 +65,7 @@ The Accessibility Guidelines Working Group engages with stakeholders in a variet
 
 The AG WG conducts its work using a variety of synchronous and asynchronous tools. The [communication page](/about/groups/agwg/communication/) provides details about:
 
-* Teleconferences of the Working Group and its task forces (also see [upcoming agendas](2/WAI/GL/wiki/Upcoming_agendas), meeting minutes);
+* Teleconferences of the Working Group and its task forces (also see [upcoming agendas](/WAI/GL/wiki/Upcoming_agendas), meeting minutes);
 * Face to face meetings (also see face-to-face [meeting pages](https://www.w3.org/WAI/GL/wiki/Meetings));
 * Email lists;
 * [Wiki](https://www.w3.org/WAI/GL/wiki/);
@@ -90,7 +90,7 @@ The AG WG maintains the following operational resources:
 
 * [Decision policy](decision-policy);
 * [Record of decisions made by the WG](https://www.w3.org/WAI/GL/wiki/Decisions);
-* [meeting minutes](minutes).
+* [meeting minutes](https://www.w3.org/WAI/GL/minutes-history).
 
 W3C maintains a [public list of any patent disclosures](https://www.w3.org/groups/wg/ag/ipr/) made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.
 

pages/about/groups/apawg/deliverables.md

@@ -15,7 +15,7 @@ The [Working Group charter](https://www.w3.org/2015/10/apa-charter.html#mileston
 | --- | --- | --- |
 | FPWD | CR | PR | Rec |
 | --- | --- | --- | --- |
-| [Personalization Semantics Content Module](https://w3c.github.io/personalization-semantics/content/) | FPWD published by ARIA WG; IP being transferred to APA. |   
+| [WAI-Adapt: Symbols Module]([WAI-Adapt: Symbols Module](https://w3c.github.io/adapt/symbols/)) | FPWD published by ARIA WG; IP being transferred to APA. |   
  | Feb 2019 | Jun 2019 | Sep 2019 |
-| [Personalization Semantics Help and Support Module](https://w3c.github.io/personalization-semantics/help/) | FPWD planned Q3 2018 | Oct 2018 | Nov 2019 | Apr 2020 | Dec 2020 |
-| [Personalization Semantics Tools Module](https://w3c.github.io/personalization-semantics/tools/) | FPWD planned Q3 2018 | Oct 2018 | Nov 2020 | Apr 2021 | Dec 2021 |
+| [WAI Adapt: Help and Support Module](https://w3c.github.io/adapt/help/) | FPWD planned Q3 2018 | Oct 2018 | Nov 2019 | Apr 2020 | Dec 2020 |
+| [WAI Adapt: Tools Module](https://w3c.github.io/adapt/tools/) | FPWD planned Q3 2018 | Oct 2018 | Nov 2020 | Apr 2021 | Dec 2021 |

pages/about/groups/apawg/participate.md

@@ -17,6 +17,6 @@ Employees of Member organizations automatically have the right to participate. T
 
 ## Individuals
 
-If you do **not** work for a [W3C Member organization](http://www.w3.org/Consortium/Member/List), but you feel you have the expertise and availability to participate, you should first use [public contribution channels](/about/groups/apaw/contribute/) to familiarize yourself with the work and make yourself known to the group. If your contribution suggests a higher level of participation is warranted, you can be invited to join the group as an Invited Expert. Please [contact the WG chairs](mailto:[email protected]) to discuss this. If you work for an organization whose business is related to that of the W3C, we may instead ask your organization to join and nominate you as a Member representative.
+If you do **not** work for a [W3C Member organization](http://www.w3.org/Consortium/Member/List), but you feel you have the expertise and availability to participate, you should first use [public contribution channels](/about/groups/apawg/contribute/) to familiarize yourself with the work and make yourself known to the group. If your contribution suggests a higher level of participation is warranted, you can be invited to join the group as an Invited Expert. Please [contact the WG chairs](mailto:[email protected]) to discuss this. If you work for an organization whose business is related to that of the W3C, we may instead ask your organization to join and nominate you as a Member representative.
 
 If the chairs support it, you may complete the [invited expert application](https://www.w3.org/ieapp/new) form, indicating the Accessible Platform Architectures WG as the group you wish to join. Make sure you have read and accepted the policies referenced from that form, and include details about your relevant expertise, interest in the work, and your employer. _If you have not made yourself known to the chairs, or your application does not provide information about your expertise and expected contribution, it may be rejected._

pages/about/groups/apawg/task-forces.md

@@ -27,7 +27,7 @@ The [Cognitive and Learning Disabilities Accessibility Task Force](/about/groups
 
 ## WAI-Adapt Task Force
 
-The work of [WAI-Adapt Task Force](/about/groups/task-forces/personalization/) enables users to use adaptive widgets and user preferences to customize their user experience. It enables content authors to provide a default design and enable user adaptation with minimal work.
+The work of [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) enables users to use adaptive widgets and user preferences to customize their user experience. It enables content authors to provide a default design and enable user adaptation with minimal work.
 
 ## Research Questions Task Force
 

pages/about/groups/apawg/video-examples.md

@@ -9,7 +9,7 @@ The following videos highlight the work being performed in APA and within our ta
 
 ## WAI-Adapt Video Example
 
-The [WAI-Adapt Task Force](/about/groups/task-forces/personalization/) created a video to demonstrate a semantic overlay approach to enable user driven personalization, eg. the association of user-preferred symbols with elements having those semantics.
+The [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) created a video to demonstrate a semantic overlay approach to enable user driven personalization, eg. the association of user-preferred symbols with elements having those semantics.
 
 ### Video Recording
 

pages/about/groups/ariawg/task-forces.md

@@ -24,13 +24,10 @@ The ARIA Working Group conducts some of its work via the following task forces.
 
 The [ARIA Authoring Practices task force](/about/groups/task-forces/practices/) to develop WAI-ARIA Authoring Practices, which describes considerations that might not be evident to most authors from the WAI-ARIA specification alone and recommends approaches to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties.
 
-## CSS Accessibility Task Force
 
-The [CSS Accessibility Task Force](/about/groups/task-forces/css-a11y/) is a joint task force of the ARIA WG, the [Accessible Platform Architectures Working Group](/about/groups/apawg/), and the [Cascading Style Sheets Working Group](https://www.w3.org/Style/CSS/). It will focus effort on identifying accessibility problems that can be created by use of Cascading Style Sheets (CSS), and to develop solutions.
+## WAI-Adapt Task Force
 
-## Personalization Task Force
-
-The [Personalization Task Force](/about/groups/task-forces/personalization/) has been moved to the APA Working Group.
+The [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) has been moved to the APA Working Group.
 
 ## WAI-ARIA User Agent Implementation Task Force
 
@@ -42,4 +39,4 @@ This task force has closed.
 
 ## Digital Publishing ARIA Task Force
 
-This task force has closed.
+This task force has closed.

pages/about/groups/index.md

@@ -50,7 +50,7 @@ See also:
 -   [**Task Forces**](/about/groups/task-forces/) - Lists some active Task Forces that
     operate under WAI Working Groups, and/or jointly between WAI groups
     and other W3C groups.
--   **[Participating in WAI](/about/participate/)** - Describes participation
+-   **[Participating in WAI](/about/participating/)** - Describes participation
     opportunities ranging from volunteering to implement, promote, and
     review guidelines, to occasional participation in an interest group,
     to dedicated participation in a working group.

pages/about/groups/task-forces.md

@@ -76,7 +76,7 @@ Task Forces operate under specific Working Groups.
 
 :   The Spoken Pronunciation Task Force has been exploring technical options for content authors to provide pronunciation information.
 
-**[WAI-Adapt Task Force](/about/groups/task-forces/personalization/)** under the [APA Working Group](/about/groups/apawg/)
+**[WAI-Adapt Task Force](/about/groups/task-forces/adapt/)** under the [APA Working Group](/about/groups/apawg/)
 
 :   WAI-Adapt specifications enable users to personalize how content is presented in order to meet their needs and preferences.
 

pages/about/groups/task-forces/personalization.md → pages/about/groups/task-forces/adapt.md

@@ -1,7 +1,7 @@
 ---
 title: WAI-Adapt Task Force of the APA WG
-permalink: /about/groups/task-forces/personalization/
-ref: /about/groups/task-forces/personalization/
+permalink: /about/groups/task-forces/adapt/
+ref: /about/groups/task-forces/adapt/
 lang: en
 ---
 
@@ -48,7 +48,7 @@ The WAI-Adapt Task Force conducts its work using a variety of synchronous and as
 
 - Teleconferences of the Working Group and its task forces (also see [meeting minutes](https://www.w3.org/WAI/APA/task-forces/adapt/minutes));
 - Face to face meetings;
-- [Email lists](/about/groups/task-forces/personalization/#mailing-lists);
+- [Email lists](/about/groups/task-forces/adapt/#mailing-lists);
 - IRC discussion on the [#adapt](irc://irc.w3.org/adapt) IRC channel, used largely for minute-taking;
 - [WAI-Adapt source repository](https://github.com/w3c/adapt/);
 - [Wiki](https://github.com/w3c/adapt/wiki);
@@ -88,7 +88,7 @@ See also the [WAI-Adapt Task Force GitHub repository](https://github.com/w3c/ada
 
 ## How to Comment, Contribute, and Participate
 
-To join the WAI-Adapt Task Force, individuals must be participants of the [APA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/personalization/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the WAI-Adapt Task Force, please send e-mail to: [Lionel Wolberger](mailto:[email protected]?subject=WAI-Adapt%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi Ran (Roy)](mailto:[email protected]) to add you to the task force.
+To join the WAI-Adapt Task Force, individuals must be participants of the [APA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/adapt/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the WAI-Adapt Task Force, please send e-mail to: [Lionel Wolberger](mailto:[email protected]?subject=WAI-Adapt%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi Ran (Roy)](mailto:[email protected]) to add you to the task force.
 
 To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/adapt/).
 
@@ -105,4 +105,4 @@ The WAI-Adapt Task Force is a Task Force of the [Accessible Platform Architectur
 
 ### Work Statement
 
-The [WAI-Adapt Task Force Work Statement](/about/groups/task-forces/personalization/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force.
+The [WAI-Adapt Task Force Work Statement](/about/groups/task-forces/adapt/work-statement/) defines the initial objective, scope, approach, and participation of the Task Force.

pages/about/groups/task-forces/personalization/work-statement.md → pages/about/groups/task-forces/adapt/work-statement.md

@@ -1,15 +1,15 @@
 ---
 title: WAI-Adapt Task Force Work Statement
-permalink: /about/groups/task-forces/personalization/work-statement/
-ref: /about/groups/task-forces/personalization/work-statement/
+permalink: /about/groups/task-forces/adapt/work-statement/
+ref: /about/groups/task-forces/adapt/work-statement/
 lang: en
 ---
 
 {::nomarkdown}
 {% include box.html type="start" title="Summary" class="" %}
 {:/}
 
-The [WAI-Adapt Task Force](/about/groups/task-forces/personalization/) is a task force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). It assists this Working Group with the work identified below.
+The [WAI-Adapt Task Force](/about/groups/task-forces/adapt/) is a task force of the [Accessible Platform Architectures (APA) Working Group](/about/groups/apawg/). It assists this Working Group with the work identified below.
 
 {::nomarkdown}
 {% include box.html type="end" %}
@@ -48,12 +48,12 @@ In addition to the features defined in WAI-Adapt, other work also addresses the
 
 ## Communication
 
-WAI-Adapt Task Force communications and discussions are visible to the public. The [task force home page](/about/groups/task-forces/personalization/) details communication mechanisms in use. The task force will:
+WAI-Adapt Task Force communications and discussions are visible to the public. The [task force home page](/about/groups/task-forces/adapt/) details communication mechanisms in use. The task force will:
 
 - Support synchronous (e.g., teleconferences, face-to-face meetings) and asynchronous (e.g., mailing list discussions, issue trackers, wiki, surveys, etc.) methods of communication;
 - Use the procedures of the [APA Working Group Decision Policy](/about/groups/apawg/decision-policy/) to make decisions;
 - Provide updates and feedback to APA Working Group teleconferences, as appropriate. These liaisons are primarily the responsibility of the WAI-Adapt Task Force Facilitators;
-- Maintain information resulting from its activities (deliverables, participants, face-to-face meetings, teleconferences, etc.) on the [WAI-Adapt Task Force home page](/about/groups/task-forces/personalization/).
+- Maintain information resulting from its activities (deliverables, participants, face-to-face meetings, teleconferences, etc.) on the [WAI-Adapt Task Force home page](/about/groups/task-forces/adapt/).
 
 ## Participation
 

pages/about/groups/task-forces/matf.md

@@ -39,12 +39,10 @@ _4 January 2024_ **New facilitator appointed**: Jan Jaap de Groot has been appoi
 The Mobile Accessibility Task Force conducts its work using a variety of synchronous and asynchronous tools. Most work is done via email and issues as shown below, supplemented by occasional teleconferences.
 
 - [Email lists](#mailing-lists);
-- [wiki](https://www.w3.org/WAI/GL/task-forces/matf/wiki);
-- [Tracker](https://www.w3.org/WAI/GL/task-forces/matf/track/);
 - IRC discussion (server: **irc.w3.org**, port: **6665,** channel: **#matf**) is used by some members during the teleconferences. Please type "present+" _your name_ in the IRC channel when joining a meeting.;
 - [Web-Based Surveys (WBS)](https://www.w3.org/2002/09/wbs/66524/);
 
-These tools are used by participants of the Task Force. For ways non-participants can contribute, see how to [participate in the Working Group](/about/groups/agwg/participate/) and [file comments](https://www.w3.org/WAI/GL/WCAG20/comments/).
+These tools are used by participants of the Task Force. For ways non-participants can contribute, see how to [participate in the Working Group](/about/groups/agwg/participate/).
 
 ### Online Meetings
 

pages/about/groups/task-forces/maturity-model.md

@@ -76,7 +76,7 @@ See also the [Maturity Model Task Force GitHub repository](https://github.com/w3
 
 ## How to Comment, Contribute, and Participate
 
-To join the Maturity Model Task Force, individuals must be participants of the [APA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/maturity-model/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the Maturity Model Task Force, please send e-mail to: [Janina Sajka, Sheri Byrne-Haber, David Fazio](mailto:[email protected],[email protected],[email protected]?subject=Maturity Model%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/particpate/) procedures to join the Working Group, and once you have joined ask [Ruoxi Ran (Roy)](mailto:[email protected]) to add you to the task force.
+To join the Maturity Model Task Force, individuals must be participants of the [APA WG](/about/groups/apawg/). Participants are expected to [actively contribute](/about/groups/task-forces/maturity-model/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the Maturity Model Task Force, please send e-mail to: [Janina Sajka, Sheri Byrne-Haber, David Fazio](mailto:[email protected],[email protected],[email protected]?subject=Maturity Model%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi Ran (Roy)](mailto:[email protected]) to add you to the task force.
 
 To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/maturity-model/).
 

pages/about/groups/task-forces/research-questions.md

@@ -72,7 +72,7 @@ When the Task Force develops publications, they will be listed here. See also th
 
 ## How to Comment, Contribute, and Participate
 
-To join the RQTF, individuals must be participants of the APA WG. Participants are expected to [actively contribute](/about/groups/task-forces/research-questions/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the RQTF, please send e-mail to: [Janina Sajka, Jason White](mailto:[email protected],[email protected]?subject=Research%20Questions%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participation/) procedures to join the Working Group, and once you have joined ask [Ruoxi(Roy) Ran](mailto:[email protected]) to add you to the task force.
+To join the RQTF, individuals must be participants of the APA WG. Participants are expected to [actively contribute](/about/groups/task-forces/research-questions/work-statement/#participation) to the work of the Task Force. If you are interested in participating in the RQTF, please send e-mail to: [Janina Sajka, Jason White](mailto:[email protected],[email protected]?subject=Research%20Questions%20Task%20Force%20Enquiry) and include a little bit about what you’re interested in and how you think that you may be able to contribute to the Task Force. Then follow the [APA Working Group participation](/about/groups/apawg/participate/) procedures to join the Working Group, and once you have joined ask [Ruoxi(Roy) Ran](mailto:[email protected]) to add you to the task force.
 
 To contribute without joining the task force, see the [APA Working Group contribute page](/about/groups/apawg/contribute/) for general instructions. To contribute to documents under development, see [how to contribute to the source repository directly](https://github.com/w3c/rqtf/).
 

pages/about/groups/task-forces/wcag2x-backlog.md

@@ -59,6 +59,6 @@ If you are interested in becoming a participant of the WCAG 2 Task Force or have
 ## Facilitation
 The AG Working Group chair liaison oversees attention to W3C Process with respect to the chartered requirements of the Working Group. The Facilitators set agenda, lead meetings, determine consensus, and are the primary reporters of progress to the Working Group.
 
-* Facilitators: [Bruce Bailey]([email protected]), US Access Board; [Michael Gower]([email protected]), IBM Corporation
+* Facilitators: Bruce Bailey, US Access Board; Michael Gower, IBM Corporation
 
-* AG WG chair liaison: [Alastair Campbell]([email protected]), Nomensa
+* AG WG chair liaison: Alastair Campbell, Nomensa