Update links (#523)

w3c · Oct 2, 2024 · eb895ff · eb895ff
1 parent 8cb82cc
commit eb895ff
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/closed-functionality.md b/closed-functionality.md
@@ -3,7 +3,7 @@ Comments on Closed Functionality
 
 As noted in the Introduction, WCAG 2 assumes the presence of a “user agent” such as a browser, media player, or assistive technology as a means to access web content. Many of the success criteria in WCAG 2 assume web content will be accessed by ICT where assistive technologies can be connected to it or installed on it. The assistive technologies then present the web content to people with disabilities in an accessible form. 
 
-ICT with [closed functionality](#closed-functionality) does not allow the use of some assistive technologies for some or all of the ICT's functions. In many cases, such ICT also lacks a “user agent” or its equivalent. To the extent the ICT is closed, following the WCAG success criteria by themselves will not ensure that non-web software is accessible. Where the wide range of assistive technologies or user agents are not available, as they are for Web content, to address the intent of these success criteria, something else needs to be provided or be required to facilitate accessibility as intended by WCAG 2. It is outside the [WCAG2ICT Task Force Work Statement](http://www.w3.org/WAI/GL/task-forces/wcag2ict/work-statement) to say what additional measures are needed, but WCAG2ICT points out which success criteria depend on assistive technologies &mdash; and therefore which success criteria would be problematic in the context of ICT with closed functionality.
+ICT with [closed functionality](#closed-functionality) does not allow the use of some assistive technologies for some or all of the ICT's functions. In many cases, such ICT also lacks a “user agent” or its equivalent. To the extent the ICT is closed, following the WCAG success criteria by themselves will not ensure that non-web software is accessible. Where the wide range of assistive technologies or user agents are not available, as they are for Web content, to address the intent of these success criteria, something else needs to be provided or be required to facilitate accessibility as intended by WCAG 2. It is outside the [WCAG2ICT Task Force Work Statement](http://www.w3.org/WAI/about/groups/task-forces/wcag2ict/work-statement/) to say what additional measures are needed, but WCAG2ICT points out which success criteria depend on assistive technologies &mdash; and therefore which success criteria would be problematic in the context of ICT with closed functionality.
 
 <div class="example">
 

diff --git a/introduction.md b/introduction.md
@@ -18,7 +18,7 @@ This document is intended to help clarify how to use WCAG 2 to make non-web docu
 
 Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. Since WCAG 2 was developed for the Web, addressing accessibility for non-web documents and software may involve requirements and considerations beyond those included in this document. Authors and developers are encouraged to seek relevant advice about current best practices to ensure that non-web documents and software are accessible, as much as possible, to people with disabilities. The following supporting documents contain helpful information to learn about the user needs, intent, and generalized implementation techniques to support a wider range of people with disabilities:
 
-* [WCAG 2 Overview](https://www.w3.org/WAI/intro/wcag.php)
+* [WCAG 2 Overview](https://www.w3.org/WAI/standards-guidelines/wcag/)
 * [Techniques for WCAG 2.2](https://www.w3.org/WAI/WCAG22/Techniques/) \[\[WCAG22-TECHS\]\]
 * [How to Meet WCAG (Quick Reference)](https://www.w3.org/WAI/WCAG22/quickref/)
 * [Additional Accessibility Guidelines Working Group - Publications](https://www.w3.org/groups/wg/ag/publications/)