Fix links in WG/TF pages (#1105)

* Use HTTPS

* WAI IG: update link to Code of conduct

* AGWG & ARIAWG: Fix links

pages/about/groups/agwg.md

@@ -54,7 +54,7 @@ Work on developing WCAG 3 takes place in many task forces and subgroups of the A
 
 ### WCAG 2.2
 
-The [WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog) maintains WCAG 2.x (WCAG versions 2.0, 2.1, and 2.2) for the AG Working Group. This includes reviewing public comments on WCAG 2.x and improving the following supporting documents:
+The [WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog/) maintains WCAG 2.x (WCAG versions 2.0, 2.1, and 2.2) for the AG Working Group. This includes reviewing public comments on WCAG 2.x and improving the following supporting documents:
 
 * [Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/)
 * [Techniques for WCAG 2.2](https://www.w3.org/WAI/WCAG22/Techniques/)
@@ -72,7 +72,7 @@ There are ways you can contribute without being a member of the working group:
 * **Comment on publications:** During development, the group publishes working drafts for public comment — these are announced on the [WAI News pages](/news/) and on the [WAI Interest Group mailing lists](/about/groups/waiig/#mailinglist).
 * **Raise, comment on, or propose fixes to WCAG issues:** If you’re aware of an issue with any of the published WCAG 2.x resources, W3C welcomes you to [raise a new issue on GitHub](https://github.com/w3c/wcag/issues/) — you can also comment on and, even better, propose solutions for existing issues.
 * **Contribute to WCAG 3 discussions:** As WCAG 3 develops, many topics are being discussed — to contribute your views, see the list of [open WCAG 3 discussions in GitHub](https://github.com/w3c/wcag3/discussions) and [mailing list discussions](https://lists.w3.org/Archives/Public/w3c-wai-gl/).
-* **Participate in a community group:** W3C hosts a small number of active community groups that focus on digital accessibility issues — for details, search for ‘accessibility’ on [Current Groups — W3C Community and Business Groups](https://www.w3.org/community/groups).
+* **Participate in a community group:** W3C hosts a small number of active community groups that focus on digital accessibility issues — for details, search for ‘accessibility’ on [Current Groups — W3C Community and Business Groups](https://www.w3.org/community/groups/).
 
 ### Become a participant in the group
 

pages/about/groups/ariawg.md

@@ -51,7 +51,7 @@ To learn about the group’s focus, scope and deliverables, see the [ARIA Workin
 
 ## Current work 
 
-For details of the current work, see the [ARIA Working Group README on GitHub](https://www.github.com/w3c/aria/#readme).
+For details of the current work, see the [ARIA Working Group README on GitHub](https://github.com/w3c/aria/#readme).
 
 The ARIA Working Group follows a set process for developing ARIA guidelines and resolving ARIA issues — for details, see [ARIA Working Group Process Document](https://github.com/w3c/aria/blob/main/documentation/process.md).
 

pages/about/groups/ig.md

@@ -54,7 +54,7 @@ The WAI Interest Group has two mailing lists.
 
 ### Announcements List
 
-The Announcements List is for WAI announcements only — see the [Announcement List Mail Archive](http://lists.w3.org/Archives/Public/public-wai-announce/).
+The Announcements List is for WAI announcements only — see the [Announcement List Mail Archive](https://lists.w3.org/Archives/Public/public-wai-announce/).
 
 If you want to send a message to this list, you must send it from an email address that is subscribed to the list.
 
@@ -105,7 +105,7 @@ Make sure your email is related to digital accessibility and is appropriate for
 
 In summary, before you send an email, think about how it will come across to the people around the world who are on the list and who can read your publicly archived message.
 
-See additional guidance in [Positive Work Environment at W3C: Code of Conduct](https://www.w3.org/Consortium/cepc/).
+See additional guidance in [Positive Work Environment at W3C: Code of Conduct](https://www.w3.org/policies/code-of-conduct/).
 
 ##### Asking about vendors or products
 

pages/about/groups/task-forces/conformance-testing.md

@@ -79,7 +79,7 @@ Once you are a member of the AG Working Group, email the [W3C Staff Contact for
 
 * [Calendar of meetings](https://www.w3.org/groups/tf/wcag-act/calendar/)
 * [Minutes from previous meetings](https://www.w3.org/WAI/GL/task-forces/conformance-testing/minutes)
-* [Mailing list archive](http://lists.w3.org/Archives/Public/public-wcag-act/)
+* [Mailing list archive](https://lists.w3.org/Archives/Public/public-wcag-act/)
 
 ## Publications
 

pages/about/groups/task-forces/low-vision-a11y-tf/work-statement.md

@@ -57,7 +57,7 @@ The Low Vision Accessibility Task Force will also coordinate with the [Accessibl
 
 Low Vision Accessibility Task Force communications are publicly visible. Communication mechanisms for the Low Vision Accessibility Task Force include:
 
-- Low Vision Accessibility Task Force mailing list [email protected] and [mailing list archive](http://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/) ;
+- Low Vision Accessibility Task Force mailing list [email protected] and [mailing list archive](https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/) ;
 - Use of a [wiki](https://www.w3.org/WAI/GL/task-forces/low-vision-a11y-tf/wiki/) to share development of resources;
 - [Web-based surveys](https://www.w3.org/2002/09/wbs/81151/) to poll group opinion;
 - IRC discussion on the [#lvtf](irc://irc.w3.org/lvtf) IRC channel, used largely for minute-taking;

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

@@ -88,7 +88,7 @@ Once you are a member of the AG Working Group, email the [W3C Staff Contact for
 The Mobile A11y Task Force develops and maintains the following resources for the AG Working Group;
 
 * [Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile — 2015 First Public Working Draft](https://www.w3.org/TR/mobile-accessibility-mapping/)
-* [Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile — 2018 Editor's Draft](http://w3c.github.io/Mobile-A11y-TF-Note/)
+* [Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile — 2018 Editor's Draft](https://w3c.github.io/Mobile-A11y-TF-Note/)
 * [Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile) — 2024 Editor's Draft](https://w3c.github.io/matf/)
 
 ## Contact the chair

pages/about/groups/task-forces/pdf-aam.md

@@ -80,7 +80,7 @@ Once you are a member of the ARIA Working Group, email the [W3C Staff Contact fo
 
 * [Calendar of meetings](https://www.w3.org/groups/tf/pdf-aam/calendar/)
 * [Minutes from previous meetings](https://www.w3.org/WAI/ARIA/task-forces/pdf-aam/minutes)
-* [Mailing list archive](http://lists.w3.org/Archives/Public/public-pdf-aam/)
+* [Mailing list archive](https://lists.w3.org/Archives/Public/public-pdf-aam/)
 
 ## Publications
 

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

@@ -82,7 +82,7 @@ Once you are a member of the ARIA Working Group, email the [W3C Staff Contact fo
 
 * [Calendar of meetings](https://www.w3.org/groups/tf/aria-practices/calendar/)
 * [Minutes from previous meetings](https://www.w3.org/WAI/ARIA/task-forces/practices/minutes)
-* [Mailing list archive](http://lists.w3.org/Archives/Public/public-aria-practices/)
+* [Mailing list archive](https://lists.w3.org/Archives/Public/public-aria-practices/)
 
 ## Publications
 

pages/about/groups/task-forces/practices/work-statement.md

@@ -36,7 +36,7 @@ The APG Task Force was [approved on 14 September 2017](https://lists.w3.org/Arch
 
 ## Objective
 
-The mission of the APG Task Force is to develop [WAI-ARIA Authoring Practices](http://w3c.github.io/aria-practices/), in consultation with the ARIA Working Group. The task force provides a focused forum for this work while the Working Group continues its work on ARIA development.
+The mission of the APG Task Force is to develop [WAI-ARIA Authoring Practices](https://w3c.github.io/aria-practices/), in consultation with the ARIA Working Group. The task force provides a focused forum for this work while the Working Group continues its work on ARIA development.
 
 ## Scope of Work
 

pages/about/groups/task-forces/wcag2ict/work-statement.md

@@ -69,7 +69,7 @@ Explicitly out of scope for the WCAG2ICT Task Force work are:
 
 WCAG2ICT is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. Draft content is periodically taken to the AG WG for review as it progresses.
 
-The primary effort of this Task Force is to describe how to interpret WCAG 2.x and its principles, guidelines, success criteria and conformance requirements when applying them to non-web ICT; and evaluating what WCAG Conformance means in the context of non-Web ICT. The resulting Working Group Note will include a discussion of the application of each of the criteria in WCAG 2.x to non-Web ICT, including their interface components and platforms, and the extent to which [WCAG Conformance](http://www.w3.org/TR/WCAG22/#conformance) is meaningful to non-Web ICT.
+The primary effort of this Task Force is to describe how to interpret WCAG 2.x and its principles, guidelines, success criteria and conformance requirements when applying them to non-web ICT; and evaluating what WCAG Conformance means in the context of non-Web ICT. The resulting Working Group Note will include a discussion of the application of each of the criteria in WCAG 2.x to non-Web ICT, including their interface components and platforms, and the extent to which [WCAG Conformance](https://www.w3.org/TR/WCAG22/#conformance) is meaningful to non-Web ICT.
 
 To efficiently develop the Working Group Note, work is sometimes broken down into sub-groups, under the coordination of the Task Force facilitators following established AG WG procedures for sub-groups.
 
@@ -129,7 +129,7 @@ The list of liaisons can be found in the [WCAG2ICT participants](https://www.w3.
 
 WCAG2ICT Task Force communications are publicly visible. Communication mechanisms for the WCAG2ICT Task Force include:
 
-1.  [WCAG2ICT Task Force public mailing list](mailto:[email protected]), [mailing list archive](http://lists.w3.org/Archives/Public/public-wcag2ict-tf/), and [GitHub issue tracker](https://github.com/w3c/wcag2ict/issues)
+1.  [WCAG2ICT Task Force public mailing list](mailto:[email protected]), [mailing list archive](https://lists.w3.org/Archives/Public/public-wcag2ict-tf/), and [GitHub issue tracker](https://github.com/w3c/wcag2ict/issues)
 2.  [WCAG2ICT subpage](/about/groups/task-forces/wcag2ict/) off of the [AG Working Group](/about/groups/agwg/) home page
 3.  Weekly (and at times twice-weekly) teleconferences, with teleconference minutes sent to AG WG mailing list and linked from the [WCAG2ICT TF minutes](https://www.w3.org/WAI/GL/task-forces/wcag2ict/minutes) page
 4.  Regular updates and feedback to AG WG and to the [WAI Coordination Call](https://www.w3.org/WAI/cc/wiki/Main_Page), as needed
@@ -139,7 +139,7 @@ WCAG2ICT Task Force communications are publicly visible. Communication mechanism
 
 ## Participation
 
-WCAG2ICT Task Force participants must join the Task Force through the AG WG, which includes representatives of [W3C Member Organizations](http://www.w3.org/Consortium/Member/List) as well as [Invited Experts](https://www.w3.org/participate/invited-experts/) ([agreement for Invited Experts](https://www.w3.org/Consortium/Legal/2015/06-invited-expert.html)). Task Force participants must agree to actively contribute to the work of WCAG2ICT Task Force, including:
+WCAG2ICT Task Force participants must join the Task Force through the AG WG, which includes representatives of [W3C Member Organizations](https://www.w3.org/Consortium/Member/List) as well as [Invited Experts](https://www.w3.org/participate/invited-experts/) ([agreement for Invited Experts](https://www.w3.org/Consortium/Legal/2015/06-invited-expert.html)). Task Force participants must agree to actively contribute to the work of WCAG2ICT Task Force, including:
 
 *   Minimum 4 hours per week of WCAG2ICT Task Force work through the end of the project
 *   Time contributed on WCAG2ICT Task Force counts towards AG WG participation requirement
@@ -155,7 +155,7 @@ Contact [Daniel Montalvo](mailto:[email protected]) to become a participant of th
 Staff contacts from the Accessibility Guidelines Working Group oversee 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 liaison to the Working Group.
 
 *   **Co-facilitators:** [Mary Jo Mueller](mailto:[email protected]) and [Chris Loiselle](mailto:[email protected])
-*   **Staff Contact:** [Daniel Montalvo](http://www.w3.org/People#dmontalvo)
+*   **Staff Contact:** [Daniel Montalvo](https://www.w3.org/People#dmontalvo)
 *   **Editorial Team:**
     *   Mary Jo Mueller
     *   Phil Day