WCAG2ICT - editorial - check for use of non-web ICT throughout document

[pday1]

In TF discussions of 19th February, there was some discussion regarding the use of non-web ICT, and whether that has been used frequently and consistently.
https://www.w3.org/2026/02/19-wcag2ict-minutes.html

Check latest editor's draft for use of non-web ICT (or just ICT), and ensure that it is used consistently and is also defined.

[pday1]

Searched on latest editor's draft for "non-web ICT".
This is used 16 times throughout the document.

It is defined the first time it is used in the 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)

It also appears to have been used consistently throughout. No further action is required.

[GreggVan]

suggest that the intro abstract change to non-web documents and non-web software for clarity -- adding non-web to software

[maryjom]

The whole document uses "non-web documents and software". If clarification is needed, suggest it's added to the content describing the document conventions.

[GreggVan]

I was only suggesting that we worry about it here because this is essentially a definition. But ok to leave as is - since we use it that way throughout
but if we sometimes say non-web documents and non-web software (even once) then we need to change them ALL to be non-web documents and non-web software or non-web documents and non-web software but it should always be one or the other

[pday1]

In the TF meeting of 26th Feb, it was recommended that the Introduction be edited to ensure that we define web ICT as including, but not being limited to, non-web documents and non-web software.
Define non-web ICT as includes but not limited to non web docs and software

[pday1]

Current editor's draft has the following:

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).

Guidance in This Document
This document provides informative guidance (guidance that is not normative and does not set requirements) with regard to the interpretation and application of Web Content Accessibility Guidelines (WCAG) to non-web information and communications technologies (ICT). This document is a Working Group Note (in contrast to WCAG 2.0, WCAG 2.1, and WCAG 2.2, which are W3C Recommendations). Specifically, this document provides informative guidance on applying WCAG 2.0, 2.1, and 2.2 Level A and AA success criteria to non-web ICT, specifically to non-web documents and software.

[pday1]

Proposed change (shown in bold text)

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),

including, but not being limited to, non-web documents and non-web software.

It provides informative guidance (guidance that is not normative and does not set requirements).

Guidance in This Document
This document provides informative guidance (guidance that is not normative and does not set requirements) with regard to the interpretation and application of Web Content Accessibility Guidelines (WCAG) to non-web information and communications technologies (ICT). This document is a Working Group Note (in contrast to WCAG 2.0, WCAG 2.1, and WCAG 2.2, which are W3C Recommendations). Specifically, this document provides informative guidance on applying WCAG 2.0, 2.1, and 2.2 Level A and AA success criteria to non-web ICT,

including, but not being limited to, non-web documents and non-web software.