CivicActions · mgifford · Mar 13, 2024 · Mar 13, 2024 · Mar 13, 2024 · Mar 13, 2024
diff --git a/_playbook/checklists.md b/_playbook/checklists.md
@@ -39,7 +39,6 @@ There are lots of checklists, rotating through a few of them will help give diff
 * [W3C's Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/test-evaluate/preliminary/)
 * [18F - USA Government](https://accessibility.18f.gov/checklist/)
 * [UK's Government Digital Services (GDS)](https://gds.blog.gov.uk/2014/01/13/a-checklist-for-digital-inclusion-if-we-do-these-things-were-doing-digital-inclusion/)
-* [Government of Canada](https://canada-ca.github.io/digital-playbook-guide-numerique/views-vues/standards-normes/en/6-build-in-accessibility-from-start.html#services-should-meet-or-exceed-accessibility-standards)
 * [WebAim](https://webaim.org/standards/wcag/checklist)
 * [Elsevier's WCAG 2.1 Checklist](https://romeo.elsevier.com/accessibility_checklist/)
 * [A11yProject](https://www.a11yproject.com/checklist/)

diff --git a/_playbook/follow-global-initiatives.md b/_playbook/follow-global-initiatives.md
@@ -23,7 +23,7 @@ They are also investing in prevention by participating in and leading initiative
 
 While we have yet to uniformly implement global accessibility standards, the European Commission strategy has started working more closely with the W3C's Web Accessibility Initiative (WAI) to implement best practices.
 
-[A handful of organizations are sponsoring WAI projects](https://www.w3.org/WAI/about/sponsoring/). The European Commission is giving substantial contributions to the [authoritative guide (the WAI-Guide)](https://ec.europa.eu/digital-single-market/en/content/wai-guide) and [accessibility tools (WAI-Tools)](https://ec.europa.eu/digital-single-market/en/content/wai-tools) for scalable assessments. This public-facing work both contributes to the practice of open government, and ensures that the tools they develop can be maintained by a broader community.
+[A handful of organizations are sponsoring WAI projects](https://www.w3.org/WAI/about/sponsoring/). This public-facing work both contributes to the practice of open government, and ensures that the tools they develop can be maintained by a broader community.
 
 ## Checklist
 

diff --git a/_playbook/roles.md b/_playbook/roles.md
@@ -71,7 +71,7 @@
     * Did you have someone review your work? 
     * Is it easy to scan and pick out the main points? Are headings clear and descriptive? 
     * Are you using inclusive language? 
-* Resources: [CivicAction's Plain Language Guide](https://accessibility.civicactions.com/guide/plain-language), [W3C -  Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/), [Blog post for content authors](https://www.digitala11y.com/authoring-the-authors-accessibility-best-practices-for-content-authors/), [Content Design London - Readability Guidelines](https://readabilityguidelines.co.uk), [Singapore Government Design System - Accessibility for Content](https://www.designsystem.tech.gov.sg/guides/writers-accessibility/), [USA OPM Information Management](https://www.opm.gov/information-management/plain-language/), [Canada: Writing principles for web content](https://www.canada.ca/en/treasury-board-secretariat/services/government-communications/canada-content-style-guide.html#toc5), [The Book on Accessibility](https://www.thebookonaccessibility.com/roles/cms-authors/) and [plainlanguage.gov](https://www.plainlanguage.gov).
+* Resources: [CivicAction's Plain Language Guide](https://accessibility.civicactions.com/guide/plain-language), [W3C -  Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/), [Blog post for content authors](https://www.digitala11y.com/authoring-the-authors-accessibility-best-practices-for-content-authors/), [Content Design London - Readability Guidelines](https://readabilityguidelines.co.uk), [Singapore Government Design System - Accessibility for Content](https://www.designsystem.tech.gov.sg/guides/writers-accessibility/), [USA OPM Information Management](https://www.opm.gov/information-management/plain-language/), [Canada: Writing principles for web content](https://www.canada.ca/en/treasury-board-secretariat/services/government-communications/canada-content-style-guide.html#toc5) and [plainlanguage.gov](https://www.plainlanguage.gov).
 
 ## Content Designer / Information Architecture
 * See: [UK DWP: Content Designer](https://accessibility-manual.dwp.gov.uk/guidance-for-your-job-role/content-designer), [UK Service Manual](https://www.gov.uk/service-manual/the-team/what-each-role-does-in-service-team#content-designer) and [NZ Government](https://govtnz.github.io/web-a11y-guidance/roles/content-design/)

diff --git a/...omated-accessibility-testing-leveraging-github-actions-and-pa11y-ci-with-axe.md b/...omated-accessibility-testing-leveraging-github-actions-and-pa11y-ci-with-axe.md
@@ -202,7 +202,7 @@ As noted in our [playbook for automated testing](/playbook/automated-testing):
   * [The Pa11y website](https://github.com/pa11y/pa11y.github.io) uses Travis CI and pa11y-ci.
   * The [18F Accessibility Guide](https://github.com/18F/accessibility) uses CircleCI and axe.
 
-Thank you to [Melinda Burgess](https://civicactions.com/team/melinda-burgess), [Luke Fretwell](/about/people/luke-fretwell), and [Mike Gifford](/about/people/mike-gifford) for your support, thoughts, and feedback.
+Thank you to Melinda Burgess, Luke Fretwell, and Mike Gifford for your support, thoughts, and feedback.
 
 ## What about GitLab?
 

diff --git a/_posts/2021-05-20-pre-GAAD-Authoring-Tools-Built-in-Accessibility.md b/_posts/2021-05-20-pre-GAAD-Authoring-Tools-Built-in-Accessibility.md
@@ -15,8 +15,6 @@ and people around the world organize events to raise awareness about digital acc
 2020 was the 10th anniversary, and also the launch of the [GAAD Foundation](https://gaad.foundation/). 
 
 I represented Drupal in [Funka's We4Authors Accessibility Cluster](https://accessibilitycluster.com/). Yesterday, [Funka](https://www.funka.com/) organized a pre-GAAD event to highlight the importance of authoring tools.
-[Authoring tools with built-in accessibility!](https://accessibilitycluster.com/main-results/pre-gaad-event-19-may-2021-at-13:00-16:00-cet---authoring-tools-with-built-in-accessibility! 
-) was a wonderful success with over hundred participants from over 35 countries around the world. 
 
 The We4Authors Cluster is a multi-CMS (Content Management System) group that is working to better support authors. Authors need to be subject matter experts, not accessibility experts, and CMS tools can help make their job easier. It should be simple for everyone to produce accessible content. For folks familiar with the W3C's Web Accessibility Initiative, it is essentially
 looking at implementing [Authoring Tool Accessibility Guidelines (ATAG) 2.0 - Part B](https://www.w3.org/TR/ATAG20/#part_b). By bringing together leaders in CMS solutions that are popular with governments in the 

diff --git a/...0-launching-a-community-of-practice-for-accessibility-in-government-services.md b/...0-launching-a-community-of-practice-for-accessibility-in-government-services.md
@@ -73,7 +73,7 @@ scanning/) on their website.
 
 We're also talking about:
 
-  * Why we need [accessibility compliance as code](https://gcn.com/articles/2021/02/04/accessibility-compliance-as-code.aspx)
+  * Why we need [accessibility compliance as code](https://web.archive.org/web/20210204213719/https://gcn.com/articles/2021/02/04/accessibility-compliance-as-code.aspx)
   * How to [integrate accessibility early](https://www.smashingmagazine.com/2021/04/bake-layers-accessibility-testing-process/) and throughout your process
   * Why [anchor links are a must for government agencies](https://github.com/CivicActions/accessibility/issues/261)
   * How to run [automated testing on your GitHub-hosted Jekyll site](https://accessibility.civicactions.com/posts/automated-accessibility-testing-leveraging-github-actions-and-pa11y-ci-with-axe)