Merge branch 'main' into mjm-changes-from-pr830

Author: bruce-usab

abstract.md

@@ -3,4 +3,4 @@ Abstract
 
 This document describes how the Web Content Accessibility Guidelines (WCAG) versions 2.0 \[\[WCAG20\]\], 2.1 \[\[WCAG21\]\], and 2.2 \[\[WCAG22\]\] principles, guidelines, and success criteria can be applied to non-web Information and Communications Technologies (ICT), specifically to non-web documents and software. It provides informative guidance (guidance that is not normative and does not set requirements).
 
-This document is part of a series of technical and educational documents published by the [W3C Web Accessibility Initiative (WAI)](http://www.w3.org/WAI/) and available from the [WCAG2ICT Overview](http://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/).
+This document is part of a series of technical and educational documents published by the [W3C Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/) and available from the [WCAG2ICT Overview](https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/).

background-on-text-command-line-terminal-applications-and-interfaces.md

@@ -24,9 +24,9 @@ Applying WCAG 2 to Text Applications
 
 To apply WCAG to text applications, it is necessary to apply the glossary terms [accessibility supported](#dfn-accessibility-supported) and [programmatically determined](#dfn-programmatically-determinable) in the context of how text applications are rendered and the history of assistive technologies that made them accessible.
 
-As noted above, in a text interface the terminal application renders the characters on the screen, just as a web browser typically renders content for a web application. As an example, for success criterion [1.4.4 Resize Text](http://www.w3.org/TR/WCAG22/#resize-text), a text application could achieve 200 percent resizing when the terminal application client that is rendering it has this capability (cf. WCAG 2 Technique [G142 Using a technology that has commonly-available user agents that support zoom](http://www.w3.org/WAI/WCAG22/Techniques/general/G142)). Many web pages and web applications use this approach to meet success criterion [1.4.4 Resize Text](http://www.w3.org/TR/WCAG22/#resize-text) through no explicit action of their own.
+As noted above, in a text interface the terminal application renders the characters on the screen, just as a web browser typically renders content for a web application. As an example, for success criterion [1.4.4 Resize Text](https://www.w3.org/TR/WCAG22/#resize-text), a text application could achieve 200 percent resizing when the terminal application client that is rendering it has this capability (cf. WCAG 2 Technique [G142 Using a technology that has commonly-available user agents that support zoom](https://www.w3.org/WAI/WCAG22/Techniques/general/G142)). Many web pages and web applications use this approach to meet success criterion [1.4.4 Resize Text](https://www.w3.org/TR/WCAG22/#resize-text) through no explicit action of their own.
 
-A similar approach could also be used for success criterion [1.4.3 Contrast (minimum)](http://www.w3.org/TR/WCAG22/#contrast-minimum) (cf. WCAG 2 Technique [G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults](http://www.w3.org/WAI/WCAG22/Techniques/general/G148)): relying on the terminal application client to render the text with sufficient contrast against the background. In fact, many terminal applications allow the user to force all text to share a single user-chosen foreground color (and a single user-chosen background color), overriding the text application's specified colors to meet the user's desires or needs.
+A similar approach could also be used for success criterion [1.4.3 Contrast (minimum)](https://www.w3.org/TR/WCAG22/#contrast-minimum) (cf. WCAG 2 Technique [G148: Not specifying background color, not specifying text color, and not using technology features that change those defaults](https://www.w3.org/WAI/WCAG22/Techniques/general/G148)): relying on the terminal application client to render the text with sufficient contrast against the background. In fact, many terminal applications allow the user to force all text to share a single user-chosen foreground color (and a single user-chosen background color), overriding the text application's specified colors to meet the user's desires or needs.
 
 Since many assistive technology analysis techniques depend upon discerning the location of the text input cursor, terminal application use of “soft cursors” and “highlight bars” may bypass those analysis techniques and cause failures of success criteria.
 

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/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 — 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](https://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 — and therefore which success criteria would be problematic in the context of ICT with closed functionality.
 
 <div class="example">