From d4e49306f367bb90b30b403c6688d8dd450cdd4e Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Mon, 7 Apr 2025 12:16:00 -0400 Subject: [PATCH 01/23] Update non-web-ict.md Request to update https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/ WCAG2ICT overview page with edits from WCAG2ICT's Explainer work --- .../standards-guidelines/wcag/non-web-ict.md | 68 +++++++++++++++++-- 1 file changed, 64 insertions(+), 4 deletions(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 572042c905d..b135534a1a8 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -44,13 +44,35 @@ Quick link: ## Introduction {#intro} -Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) describes how the Web Content Accessibility Guidelines (WCAG) can be applied to non-web information and communications technologies (ICT), including documents and software. WCAG2ICT is a W3C Group Note that provides informative guidance (not normative requirements). +Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) describes how the Web Content Accessibility Guidelines (WCAG) can be applied to non-web information and communications technologies (ICT), including documents and software. WCAG2ICT is the acronym used for the W3C Guidance on Applying WCAG 2 to Non-web Information and Communication Technology Group Note. + +The WCAG2ICT Group Note provides: +* [Informative](https://www.w3.org/TR/WCAG22/#dfn-informative) **guidance** that is not [normative](https://www.w3.org/TR/WCAG22/#dfn-normative) and that does not set requirements. +* **Comments on applicability** of the Web Content Accessibility Guidelines (WCAG) when applied to non-web information and communications technologies (ICT) - this includes non-web documents and software, including mobile apps, native applications, platform software, and [software on ICT with closed functionality[(https://www.w3.org/TR/wcag2ict/#comments-on-closed-functionality). +* **Technology-specific explanations or difficulties** for some success criteria. This is especially the case where WCAG makes assumptions on the presence of a browser that would not be true for non-web documents and software. Not all ICT have these concepts. + +The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make non-web documents and non-web software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with accessibility requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. WCAG2ICT supports harmonized accessibility solutions across a range of technologies. WCAG2ICT has been a key resource for including WCAG in ICT accessibility regulation, legislation, and standards around the world. +### Background and Development History for WCAG2ICT + +[WCAG 2 was developed for the Web]( https://www.w3.org/WAI/standards-guidelines/wcag/glance/). Addressing accessibility for non-web documents and non-web software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-web documents and non-web software are accessible, as far as possible, to people with disabilities. + +The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 508, EN 301549) adopt WCAG criteria for non-web documents and non-web software. The 2013 Group Note covered WCAG 2.0 (level A and AA) and the latest version of WCAG2ICT Group Note covers all WCAG 2 versions (level A and AA). + *Background:* **WCAG 2.0** is a normative web standard — it is a W3C Recommendation and an ISO International Standard ([ISO/IEC 40500:2012](https://www.w3.org/QA/2012/10/wcag_20_is_now_also_isoiec_405.html)) — that explains how to make web content (including static web pages, dynamic web applications, etc.) more accessible to people with disabilities. WCAG 2.1 was published in 2018 and **WCAG 2.2** was published in 2023. The [WCAG Overview](/standards-guidelines/wcag/) introduces the WCAG documents and links to supporting resources such as [[WCAG 2.0 at a Glance]](/standards-guidelines/wcag/20/glance/) and [How to Meet WCAG 2 (Quick Reference)](https://www.w3.org/WAI/WCAG20/quickref/). -*This document:* **WCAG2ICT** is a W3C Group Note that is informative — it is not normative and does not set requirements. It provides guidance on the application of WCAG 2 principles, guidelines, and success criteria to non-web documents and software. WCAG2ICT was developed to provide an authoritative interpretation of how WCAG 2 can apply in different contexts. For information on the scope of WCAG2ICT, see the [Introduction section of WCAG2ICT](https://www.w3.org/TR/wcag2ict/#intro). +### Goals +The objective of the WCAG2ICT Task Force is to develop documentation describing how WCAG 2.x and its principles, guidelines, and success criteria could apply to non-Web Information and Communications Technologies (ICT). + +### Intent and Usage of the WCAG2ICT + +WCAG2ICT, like any other [W3C Group Note](https://www.w3.org/policies/process/#Note), is informative — it is not normative and does not set requirements. It provides guidance on the application of WCAG 2 principles, guidelines, and success criteria to non-web documents and software. The WCAG2ICT Group Note was developed to provide an authoritative interpretation of how WCAG 2 can apply in different contexts. + +The main focus of the WCAG2ICT Group Note is to provide verbiage replacements for web-based language in the WCAG success criteria and definitions as well as provide additional insights into where WCAG criteria may make assumptions of the presence and functionality of a user agent and assistive technology. This is because not all software has a user agent or platform software with accessibility APIs and services, nor do all technologies have or support assistive technology that acts on programmatic information. + +While WCAG2ICT Group Note provides guidance on applying WCAG in non-web contexts, at this time it may not provide sufficient clarity for some success criteria on how they can be applied to electronic documents whose source is driven by non-web markup technologies when they are delivered via a website. Likewise, there may not be sufficient clarity for mobile applications. *Scope*: WCAG2ICT does not include techniques for how to meet WCAG success criteria in specific technologies. More information is in the [Excluded from Scope section](https://www.w3.org/TR/wcag2ict-22/#excluded-from-scope). @@ -61,7 +83,26 @@ WCAG2ICT supports harmonized accessibility solutions across a range of technolog ## Who WCAG2ICT is for {#for} -WCAG2ICT is for ICT managers, ICT developers, policy makers, and others wanting to understand how WCAG 2 can be applied to non-web documents and software. +The WCAG2ICT Group Note is for standards developers, ICT managers, ICT developers, policy makers, and any others wanting to understand how WCAG 2 can be applied to non-web documents and software. +* Accessibility [standards organizations](https://en.wikipedia.org/wiki/Standards_organization) - to provide non-web language in the success criteria and definitions and to provide interpretation notes to help the organization make any potential adjustments or notes needed for specific technologies, if needed. +* ICT managers - who are familiar with WCAG to quickly get an overview of using WCAG as an accessibility benchmark for non-web ICT. +* Technology developers - to provide the language substitutions for non-web language in WCAG success criteria where existing accessibility standards don’t contain an interpretation. +* Policy makers (which includes legislators, regulators) - to inform policy makers how the WCAG2ICT note is being used to influence standards requirements where WCAG is being applied to non-web ICT. +* Others include auditors, educators, litigators, vendors, and any individuals looking to learn more about digital accessibility. + + +## What WCAG2ICT Does Not Do + +The WCAG2ICT Group Note: +* Does not make or help developers make a determination on which WCAG 2 provisions (principles, guidelines, or success criteria) should not be applied to non-web documents and software or to any particular technology or product. +* Does not propose changes to WCAG 2 or its supporting documents. +* Does not address any gaps between WCAG criteria and the accessibility requirements needed to address non-user interface aspects of platforms, user-interface components as individual items, and closed product software (where there is no assistive technology to communicate programmatic information). +* Does not apply WCAG to hardware aspects of products, because WCAG does not apply to hardware. +Does not provide techniques for implementing WCAG in any type of technology, web or non-web. +* Is not a standard and does not describe how non-web ICT should conform to WCAG. +* Does not incorporate or interpret any of the WCAG supplemental guidance. + +See the [Guidance in this Document[(https://w3c.github.io/wcag2ict/#guidance-in-this-document) section of the WCAG2ICT Group Note for more details. ## What is in WCAG2ICT {#whatis} @@ -85,7 +126,26 @@ WCAG2ICT follows the [W3C](https://www.w3.org) format for technical reports, whi ## Who develops WCAG2ICT {#wg} -WCAG2ICT is developed by the [WCAG2ICT Task Force](https://www.w3.org/WAI/GL/WCAG2ICT-TF/), provided for public review, and approved by the Accessibility Guidelines Working Group ([AG WG](https://www.w3.org/WAI/GL/)), which is part of the World Wide Web Consortium ([W3C](https://www.w3.org/)) Web Accessibility Initiative ([WAI](https://www.w3.org/WAI/)). +The WCAG2ICT Group Note is developed by a [Task Force (TF)](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/) of the [Accessibility Guidelines Working Group (AG WG)](https://www.w3.org/WAI/about/groups/agwg/). The [work statement](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/work-statement/) defines the objectives, scope, approach, and so on for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from [W3C member organizations](https://www.w3.org/membership/list/) and [invited experts](https://www.w3.org/invited-experts/) and are supported by [Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/about/#wai-staff). + +### Related Documents + +We realize that there are many more standards that cover non-web software aspects of ICT. The following is not an extensive or complete list of references that may use WCAG2ICT: +* W3C WAI [Web Accessibility Laws and Policies](https://www.w3.org/WAI/policies/) page +* [Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments | ADA.gov](https://www.ada.gov/resources/2024-03-08-web-rule/) +* U.S. Dept. of Justice Rule [Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities](https://www.federalregister.gov/documents/2024/04/24/2024-07758/nondiscrimination-on-the-basis-of-disability-accessibility-of-web-information-and-services-of-state) +* [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/TR/WCAG22/) +* [WCAG2ICT Task Force](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/)) +* [WCAG2ICT Work Statement](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/work-statement/) +* [EN 301 549](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf) and country-specific standards based on the EN 301 549 + * [CAN/ASC - EN 301 549 Accessibility requirements for ICT products and services (EN 301 549, IDT](https://accessible.canada.ca/en-301-549-accessibility-requirements-ict-products-and-services-1)) (Canada standards adoption of the EN 301 549 verbatim) + * [AS EN 301 549](https://www.standards.org.au/standards-catalogue/standard-details?designation=as-en-301-549-2020) (Australia standards adoption of the EN 301 549 verbatim) + * [IS 17802 Part 1](https://broadbandindiaforum.in/wp-content/uploads/2022/08/IS-17802_1_2021.pdf) and [IS 17802 Part 2](https://broadbandindiaforum.in/wp-content/uploads/2022/08/IS-17802_2_2022.pdf) (India standard based on the EN 301 549) + * [KS 2952-1](KS 2952-1) and [KS 2952-2](https://webstore.kebs.org/index.php?route=product/product&product_id=17112) (Kenya standard based on the EN 301 549) + * CPR-6201, JEN 301 549 (Japan standard based on the EN 301 549) +* [CSA/ASC B651.2:22](https://www.csagroup.org/wp-content/uploads/2430258.pdf?srsltid=AfmBOoqlJl3r-eDhOggnJXIs7mLdzYJMBawVua_mDI1ss6iGX9czQ93f) (National Standard of Canada) CSA Group Accessible design for service-interactive devices including automated banking machines. +* [U.S. Section 508 of the Rehabilitation Act](https://www.access-board.gov/about/law/ra.html#section-508-federal-electronic-and-information-technology) requires ICT developed, procured, maintained, or used by U.S. federal agencies be accessible to people with disabilities. +* [Section 508 Standards](https://www.access-board.gov/ict/) is a U.S. regulation that defines what is necessary for ICT to be considered accessible ### Comments From f614ca939b917e83b421136d8c35895072c80804 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:45:17 -0400 Subject: [PATCH 02/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index b135534a1a8..8d6eba31b67 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -66,7 +66,7 @@ The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 5 ### Goals The objective of the WCAG2ICT Task Force is to develop documentation describing how WCAG 2.x and its principles, guidelines, and success criteria could apply to non-Web Information and Communications Technologies (ICT). -### Intent and Usage of the WCAG2ICT +### Intent and Usage of WCAG2ICT WCAG2ICT, like any other [W3C Group Note](https://www.w3.org/policies/process/#Note), is informative — it is not normative and does not set requirements. It provides guidance on the application of WCAG 2 principles, guidelines, and success criteria to non-web documents and software. The WCAG2ICT Group Note was developed to provide an authoritative interpretation of how WCAG 2 can apply in different contexts. From 676e18b29491dc8e964ea221671b544ca651fbcd Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:45:31 -0400 Subject: [PATCH 03/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 1 - 1 file changed, 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 8d6eba31b67..b37946bec01 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -74,7 +74,6 @@ The main focus of the WCAG2ICT Group Note is to provide verbiage replacements fo While WCAG2ICT Group Note provides guidance on applying WCAG in non-web contexts, at this time it may not provide sufficient clarity for some success criteria on how they can be applied to electronic documents whose source is driven by non-web markup technologies when they are delivered via a website. Likewise, there may not be sufficient clarity for mobile applications. -*Scope*: WCAG2ICT does not include techniques for how to meet WCAG success criteria in specific technologies. More information is in the [Excluded from Scope section](https://www.w3.org/TR/wcag2ict-22/#excluded-from-scope). ### Versions * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published 8 October 2024 and covers WCAG 2.0, 2.1, and 2.2 From e01e7e805912f1602731e2753e69377b227cca53 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:45:44 -0400 Subject: [PATCH 04/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index b37946bec01..319fea761dc 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -97,7 +97,7 @@ The WCAG2ICT Group Note: * Does not propose changes to WCAG 2 or its supporting documents. * Does not address any gaps between WCAG criteria and the accessibility requirements needed to address non-user interface aspects of platforms, user-interface components as individual items, and closed product software (where there is no assistive technology to communicate programmatic information). * Does not apply WCAG to hardware aspects of products, because WCAG does not apply to hardware. -Does not provide techniques for implementing WCAG in any type of technology, web or non-web. +* Does not provide techniques for implementing WCAG in any type of technology, web or non-web. * Is not a standard and does not describe how non-web ICT should conform to WCAG. * Does not incorporate or interpret any of the WCAG supplemental guidance. From cf7bb915b58e1440f498d434487b348c4417a740 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:45:57 -0400 Subject: [PATCH 05/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 319fea761dc..1998a3b97c7 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -101,7 +101,7 @@ The WCAG2ICT Group Note: * Is not a standard and does not describe how non-web ICT should conform to WCAG. * Does not incorporate or interpret any of the WCAG supplemental guidance. -See the [Guidance in this Document[(https://w3c.github.io/wcag2ict/#guidance-in-this-document) section of the WCAG2ICT Group Note for more details. +See the [Guidance in this Document](https://w3c.github.io/wcag2ict/#guidance-in-this-document) section of the WCAG2ICT Group Note for more details. ## What is in WCAG2ICT {#whatis} From 1e4465a3ebf5138d29a8df15c777f94c1de03261 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:46:08 -0400 Subject: [PATCH 06/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 1998a3b97c7..b2afee8f1ae 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -131,7 +131,7 @@ The WCAG2ICT Group Note is developed by a [Task Force (TF)](https://www.w3.org/W We realize that there are many more standards that cover non-web software aspects of ICT. The following is not an extensive or complete list of references that may use WCAG2ICT: * W3C WAI [Web Accessibility Laws and Policies](https://www.w3.org/WAI/policies/) page -* [Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments | ADA.gov](https://www.ada.gov/resources/2024-03-08-web-rule/) +* [Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments](https://www.ada.gov/resources/2024-03-08-web-rule/) (ADA.gov) * U.S. Dept. of Justice Rule [Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities](https://www.federalregister.gov/documents/2024/04/24/2024-07758/nondiscrimination-on-the-basis-of-disability-accessibility-of-web-information-and-services-of-state) * [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/TR/WCAG22/) * [WCAG2ICT Task Force](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/)) From a5390bbb0995f6b97276b5919a40f1a8e3bfc6f0 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:46:23 -0400 Subject: [PATCH 07/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Phil Day <113425927+pday1@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index b2afee8f1ae..69e6e76f753 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -72,7 +72,7 @@ WCAG2ICT, like any other [W3C Group Note](https://www.w3.org/policies/process/# The main focus of the WCAG2ICT Group Note is to provide verbiage replacements for web-based language in the WCAG success criteria and definitions as well as provide additional insights into where WCAG criteria may make assumptions of the presence and functionality of a user agent and assistive technology. This is because not all software has a user agent or platform software with accessibility APIs and services, nor do all technologies have or support assistive technology that acts on programmatic information. -While WCAG2ICT Group Note provides guidance on applying WCAG in non-web contexts, at this time it may not provide sufficient clarity for some success criteria on how they can be applied to electronic documents whose source is driven by non-web markup technologies when they are delivered via a website. Likewise, there may not be sufficient clarity for mobile applications. +While the WCAG2ICT Group Note provides guidance on applying WCAG in non-web contexts, at this time it may not provide sufficient clarity for some success criteria on how they can be applied to electronic documents whose source is driven by non-web markup technologies when they are delivered via a website. Likewise, there may not be sufficient clarity for mobile applications. ### Versions From 96e7266f54e3be1059412f81edf67aba9b958d73 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:46:33 -0400 Subject: [PATCH 08/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Phil Day <113425927+pday1@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 69e6e76f753..630fb89d701 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -125,7 +125,7 @@ WCAG2ICT follows the [W3C](https://www.w3.org) format for technical reports, whi ## Who develops WCAG2ICT {#wg} -The WCAG2ICT Group Note is developed by a [Task Force (TF)](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/) of the [Accessibility Guidelines Working Group (AG WG)](https://www.w3.org/WAI/about/groups/agwg/). The [work statement](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/work-statement/) defines the objectives, scope, approach, and so on for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from [W3C member organizations](https://www.w3.org/membership/list/) and [invited experts](https://www.w3.org/invited-experts/) and are supported by [Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/about/#wai-staff). +The WCAG2ICT Group Note is developed by a [Task Force (TF)](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/) of the [Accessibility Guidelines Working Group (AG WG)](https://www.w3.org/WAI/about/groups/agwg/). The [work statement](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/work-statement/) defines the objectives, scope, and approach for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from [W3C member organizations](https://www.w3.org/membership/list/) and [invited experts](https://www.w3.org/invited-experts/) and are supported by [Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/about/#wai-staff). ### Related Documents From 875658f2c87aa07cb76b0cc4515efacb8e9712b9 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:46:44 -0400 Subject: [PATCH 09/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Phil Day <113425927+pday1@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 630fb89d701..8cbbd4f67b8 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -140,7 +140,7 @@ We realize that there are many more standards that cover non-web software aspect * [CAN/ASC - EN 301 549 Accessibility requirements for ICT products and services (EN 301 549, IDT](https://accessible.canada.ca/en-301-549-accessibility-requirements-ict-products-and-services-1)) (Canada standards adoption of the EN 301 549 verbatim) * [AS EN 301 549](https://www.standards.org.au/standards-catalogue/standard-details?designation=as-en-301-549-2020) (Australia standards adoption of the EN 301 549 verbatim) * [IS 17802 Part 1](https://broadbandindiaforum.in/wp-content/uploads/2022/08/IS-17802_1_2021.pdf) and [IS 17802 Part 2](https://broadbandindiaforum.in/wp-content/uploads/2022/08/IS-17802_2_2022.pdf) (India standard based on the EN 301 549) - * [KS 2952-1](KS 2952-1) and [KS 2952-2](https://webstore.kebs.org/index.php?route=product/product&product_id=17112) (Kenya standard based on the EN 301 549) + * [KS 2952-1](https://webstore.kebs.org/index.php?route=product/product&product_id=17111) and [KS 2952-2](https://webstore.kebs.org/index.php?route=product/product&product_id=17112) (Kenya standard based on the EN 301 549) * CPR-6201, JEN 301 549 (Japan standard based on the EN 301 549) * [CSA/ASC B651.2:22](https://www.csagroup.org/wp-content/uploads/2430258.pdf?srsltid=AfmBOoqlJl3r-eDhOggnJXIs7mLdzYJMBawVua_mDI1ss6iGX9czQ93f) (National Standard of Canada) CSA Group Accessible design for service-interactive devices including automated banking machines. * [U.S. Section 508 of the Rehabilitation Act](https://www.access-board.gov/about/law/ra.html#section-508-federal-electronic-and-information-technology) requires ICT developed, procured, maintained, or used by U.S. federal agencies be accessible to people with disabilities. From fb11180af07ef80e1c629fe15119e0266c9510f4 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 10 Apr 2025 10:54:53 -0400 Subject: [PATCH 10/23] Update non-web-ict.md per what was covered in WCAG2ICT meeting on 4/10/25 --- pages/standards-guidelines/wcag/non-web-ict.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 8cbbd4f67b8..e7bd3d31b90 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -1,7 +1,7 @@ --- title: "WCAG2ICT Overview" lang: en -last_updated: 2024-10-08 +last_updated: 2025-04-10 description: "Introduces the document: Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)." permalink: /standards-guidelines/wcag/non-web-ict/ @@ -12,7 +12,7 @@ github: image: /content-images/wcag/general-social.jpg footer: > -

Editor: Shawn Lawton Henry. Contributors: Mary Jo Mueller, Judy Brewer, and Daniel Montalvo.

+

Editor: Shawn Lawton Henry. Contributors: Mary Jo Mueller, Chris Loiselle, and Daniel Montalvo.

Developed with input from the WCAG2ICT Task Force and the Education and Outreach Working Group (EOWG).

--- @@ -76,7 +76,7 @@ While the WCAG2ICT Group Note provides guidance on applying WCAG in non-web cont ### Versions -* [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published 8 October 2024 and covers WCAG 2.0, 2.1, and 2.2 +* [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published 15 November 2024 and covers WCAG 2.0, 2.1, and 2.2 * older version: [Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-20/) was published 5 September 2013 and covers WCAG 2.0 * The URI [https://www.w3.org/TR/wcag2ict/](https://www.w3.org/TR/wcag2ict/) points to the latest completed version From 1561c194cd54d814d7a4954c82580fa45fa06443 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Tue, 15 Apr 2025 07:41:25 -0400 Subject: [PATCH 11/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index e7bd3d31b90..caeed41e72a 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -59,7 +59,7 @@ WCAG2ICT supports harmonized accessibility solutions across a range of technolog [WCAG 2 was developed for the Web]( https://www.w3.org/WAI/standards-guidelines/wcag/glance/). Addressing accessibility for non-web documents and non-web software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-web documents and non-web software are accessible, as far as possible, to people with disabilities. -The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 508, EN 301549) adopt WCAG criteria for non-web documents and non-web software. The 2013 Group Note covered WCAG 2.0 (level A and AA) and the latest version of WCAG2ICT Group Note covers all WCAG 2 versions (level A and AA). +The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 508, EN 301549) to adopt WCAG criteria for non-web documents and non-web software. The 2013 Group Note covered WCAG 2.0 (level A and AA) and the latest version of WCAG2ICT Group Note covers all WCAG 2 versions (level A and AA). *Background:* **WCAG 2.0** is a normative web standard — it is a W3C Recommendation and an ISO International Standard ([ISO/IEC 40500:2012](https://www.w3.org/QA/2012/10/wcag_20_is_now_also_isoiec_405.html)) — that explains how to make web content (including static web pages, dynamic web applications, etc.) more accessible to people with disabilities. WCAG 2.1 was published in 2018 and **WCAG 2.2** was published in 2023. The [WCAG Overview](/standards-guidelines/wcag/) introduces the WCAG documents and links to supporting resources such as [[WCAG 2.0 at a Glance]](/standards-guidelines/wcag/20/glance/) and [How to Meet WCAG 2 (Quick Reference)](https://www.w3.org/WAI/WCAG20/quickref/). From 00ba8e1014d01f689d5363d61eec701cdb4e5ac1 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Tue, 15 Apr 2025 07:41:43 -0400 Subject: [PATCH 12/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 1 - 1 file changed, 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index caeed41e72a..602668df0bb 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -89,7 +89,6 @@ The WCAG2ICT Group Note is for standards developers, ICT managers, ICT developer * Policy makers (which includes legislators, regulators) - to inform policy makers how the WCAG2ICT note is being used to influence standards requirements where WCAG is being applied to non-web ICT. * Others include auditors, educators, litigators, vendors, and any individuals looking to learn more about digital accessibility. - ## What WCAG2ICT Does Not Do The WCAG2ICT Group Note: From 000685a9e5daf899da32e66ebedfebf28c69b1d7 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Tue, 15 Apr 2025 07:42:47 -0400 Subject: [PATCH 13/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 602668df0bb..75522a8f553 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -57,7 +57,7 @@ WCAG2ICT supports harmonized accessibility solutions across a range of technolog ### Background and Development History for WCAG2ICT -[WCAG 2 was developed for the Web]( https://www.w3.org/WAI/standards-guidelines/wcag/glance/). Addressing accessibility for non-web documents and non-web software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-web documents and non-web software are accessible, as far as possible, to people with disabilities. +[WCAG 2 was developed for the Web](https://www.w3.org/WAI/standards-guidelines/wcag/glance/). Addressing accessibility for non-Web documents and software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-Web documents and software are accessible, as far as possible, to people with disabilities. The 2013 WCAG2ICT Group Note helped regulatory bodies develop standards (i.e., 508, EN 301549) to adopt WCAG criteria for non-web documents and non-web software. The 2013 Group Note covered WCAG 2.0 (level A and AA) and the latest version of WCAG2ICT Group Note covers all WCAG 2 versions (level A and AA). From 7f7fcdb72b7faa7b54842c825f11f03a4ab587d7 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Tue, 15 Apr 2025 07:43:11 -0400 Subject: [PATCH 14/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 75522a8f553..8bb7ada8719 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -51,7 +51,7 @@ The WCAG2ICT Group Note provides: * **Comments on applicability** of the Web Content Accessibility Guidelines (WCAG) when applied to non-web information and communications technologies (ICT) - this includes non-web documents and software, including mobile apps, native applications, platform software, and [software on ICT with closed functionality[(https://www.w3.org/TR/wcag2ict/#comments-on-closed-functionality). * **Technology-specific explanations or difficulties** for some success criteria. This is especially the case where WCAG makes assumptions on the presence of a browser that would not be true for non-web documents and software. Not all ICT have these concepts. -The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make non-web documents and non-web software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with accessibility requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. +The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make non-Web documents and software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with accessibility requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. WCAG2ICT supports harmonized accessibility solutions across a range of technologies. WCAG2ICT has been a key resource for including WCAG in ICT accessibility regulation, legislation, and standards around the world. From 61e72bb3fcdf27bc7399dbf39799cfcb18a721f2 Mon Sep 17 00:00:00 2001 From: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> Date: Tue, 15 Apr 2025 18:01:08 +0200 Subject: [PATCH 15/23] Update pages/standards-guidelines/wcag/non-web-ict.md --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 8bb7ada8719..cbe28274984 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -44,7 +44,7 @@ Quick link: ## Introduction {#intro} -Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) describes how the Web Content Accessibility Guidelines (WCAG) can be applied to non-web information and communications technologies (ICT), including documents and software. WCAG2ICT is the acronym used for the W3C Guidance on Applying WCAG 2 to Non-web Information and Communication Technology Group Note. +Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) describes how the Web Content Accessibility Guidelines (WCAG) can be applied to non-web information and communications technologies (ICT), including documents and software. The WCAG2ICT Group Note provides: * [Informative](https://www.w3.org/TR/WCAG22/#dfn-informative) **guidance** that is not [normative](https://www.w3.org/TR/WCAG22/#dfn-normative) and that does not set requirements. From 5ecd2b6baccdee9f3f15ad38965f4927fc509b1c Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Wed, 16 Apr 2025 09:37:35 -0400 Subject: [PATCH 16/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index cbe28274984..9a21bbf1e3a 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -68,7 +68,7 @@ The objective of the WCAG2ICT Task Force is to develop documentation describing ### Intent and Usage of WCAG2ICT -WCAG2ICT, like any other [W3C Group Note](https://www.w3.org/policies/process/#Note), is informative — it is not normative and does not set requirements. It provides guidance on the application of WCAG 2 principles, guidelines, and success criteria to non-web documents and software. The WCAG2ICT Group Note was developed to provide an authoritative interpretation of how WCAG 2 can apply in different contexts. +WCAG2ICT, like any other W3C Group Note, is informative — it is not normative and does not set requirements. It provides guidance on the application of WCAG 2 principles, guidelines, and success criteria to non-web documents and software. The WCAG2ICT Group Note was developed to provide an authoritative interpretation of how WCAG 2 can apply in different contexts. The main focus of the WCAG2ICT Group Note is to provide verbiage replacements for web-based language in the WCAG success criteria and definitions as well as provide additional insights into where WCAG criteria may make assumptions of the presence and functionality of a user agent and assistive technology. This is because not all software has a user agent or platform software with accessibility APIs and services, nor do all technologies have or support assistive technology that acts on programmatic information. From adc5086c7fe6644bbe88e7ddff0ea12814011f8d Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Wed, 16 Apr 2025 09:40:32 -0400 Subject: [PATCH 17/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 9a21bbf1e3a..a01121d5c92 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -48,7 +48,7 @@ Quick link: The WCAG2ICT Group Note provides: * [Informative](https://www.w3.org/TR/WCAG22/#dfn-informative) **guidance** that is not [normative](https://www.w3.org/TR/WCAG22/#dfn-normative) and that does not set requirements. -* **Comments on applicability** of the Web Content Accessibility Guidelines (WCAG) when applied to non-web information and communications technologies (ICT) - this includes non-web documents and software, including mobile apps, native applications, platform software, and [software on ICT with closed functionality[(https://www.w3.org/TR/wcag2ict/#comments-on-closed-functionality). +* **Guidance** on how the Web Content Accessibility Guidelines (WCAG) could apply to non-Web information and communications technologies (ICT) - this includes non-Web documents and software, including mobile apps, native applications, platform software, and software on ICT with closed functionality. * **Technology-specific explanations or difficulties** for some success criteria. This is especially the case where WCAG makes assumptions on the presence of a browser that would not be true for non-web documents and software. Not all ICT have these concepts. The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make non-Web documents and software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with accessibility requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. From 5a2b344273cef7e8802bb1771bf90116981a9a51 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Wed, 16 Apr 2025 09:41:04 -0400 Subject: [PATCH 18/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index a01121d5c92..bfe5ea0d034 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -55,7 +55,7 @@ The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make no WCAG2ICT supports harmonized accessibility solutions across a range of technologies. WCAG2ICT has been a key resource for including WCAG in ICT accessibility regulation, legislation, and standards around the world. -### Background and Development History for WCAG2ICT +### Background [WCAG 2 was developed for the Web](https://www.w3.org/WAI/standards-guidelines/wcag/glance/). Addressing accessibility for non-Web documents and software involves requirements beyond those included in WCAG 2 and the WCAG2ICT Group Note. Authors and developers are encouraged to seek other relevant advice about current best practices to ensure that non-Web documents and software are accessible, as far as possible, to people with disabilities. From 1b98cfac560225437a52c699f06ccf397ba48154 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 17 Apr 2025 10:28:37 -0400 Subject: [PATCH 19/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index bfe5ea0d034..e1623720cfb 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -49,7 +49,7 @@ Quick link: The WCAG2ICT Group Note provides: * [Informative](https://www.w3.org/TR/WCAG22/#dfn-informative) **guidance** that is not [normative](https://www.w3.org/TR/WCAG22/#dfn-normative) and that does not set requirements. * **Guidance** on how the Web Content Accessibility Guidelines (WCAG) could apply to non-Web information and communications technologies (ICT) - this includes non-Web documents and software, including mobile apps, native applications, platform software, and software on ICT with closed functionality. -* **Technology-specific explanations or difficulties** for some success criteria. This is especially the case where WCAG makes assumptions on the presence of a browser that would not be true for non-web documents and software. Not all ICT have these concepts. +* **Technology-specific explanations or difficulties** for some success criteria. This is especially the case where WCAG makes assumptions on the presence of a browser that would not be true for non-web documents and software. Not all ICT have a user agent or other underlying platform. The WCAG2ICT Group Note is intended to help clarify how to use WCAG 2 to make non-Web documents and software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with accessibility requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. From ea705b889a347b6fa539226667294243e816c316 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 17 Apr 2025 10:30:08 -0400 Subject: [PATCH 20/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index e1623720cfb..718697b64e7 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -72,7 +72,7 @@ WCAG2ICT, like any other W3C Group Note, is informative — it is not normative The main focus of the WCAG2ICT Group Note is to provide verbiage replacements for web-based language in the WCAG success criteria and definitions as well as provide additional insights into where WCAG criteria may make assumptions of the presence and functionality of a user agent and assistive technology. This is because not all software has a user agent or platform software with accessibility APIs and services, nor do all technologies have or support assistive technology that acts on programmatic information. -While the WCAG2ICT Group Note provides guidance on applying WCAG in non-web contexts, at this time it may not provide sufficient clarity for some success criteria on how they can be applied to electronic documents whose source is driven by non-web markup technologies when they are delivered via a website. Likewise, there may not be sufficient clarity for mobile applications. +While the WCAG2ICT Group Note provides guidance on applying WCAG in non-web contexts, application of some success criteria to electronic documents whose source is driven by non-web markup technologies when they are delivered via a website may benefit from more specific guidance. Likewise, guidance for mobile applications may also benefit from a greater level of detail. ### Versions From 51504a89f58df72237446347b4b876df7c6aacff Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 17 Apr 2025 10:44:26 -0400 Subject: [PATCH 21/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 718697b64e7..0e73d0a431d 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -86,7 +86,7 @@ The WCAG2ICT Group Note is for standards developers, ICT managers, ICT developer * Accessibility [standards organizations](https://en.wikipedia.org/wiki/Standards_organization) - to provide non-web language in the success criteria and definitions and to provide interpretation notes to help the organization make any potential adjustments or notes needed for specific technologies, if needed. * ICT managers - who are familiar with WCAG to quickly get an overview of using WCAG as an accessibility benchmark for non-web ICT. * Technology developers - to provide the language substitutions for non-web language in WCAG success criteria where existing accessibility standards don’t contain an interpretation. -* Policy makers (which includes legislators, regulators) - to inform policy makers how the WCAG2ICT note is being used to influence standards requirements where WCAG is being applied to non-web ICT. +* Policy makers (including regulators when making regulations) - to inform them how the WCAG2ICT note is being used to influence standards requirements where WCAG is being applied to non-web ICT. * Others include auditors, educators, litigators, vendors, and any individuals looking to learn more about digital accessibility. ## What WCAG2ICT Does Not Do From bd94a86654b8383d02e4abc6ee9479ed2af73b45 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 17 Apr 2025 10:47:07 -0400 Subject: [PATCH 22/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index 0e73d0a431d..bb7191f3e24 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -124,7 +124,7 @@ WCAG2ICT follows the [W3C](https://www.w3.org) format for technical reports, whi ## Who develops WCAG2ICT {#wg} -The WCAG2ICT Group Note is developed by a [Task Force (TF)](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/) of the [Accessibility Guidelines Working Group (AG WG)](https://www.w3.org/WAI/about/groups/agwg/). The [work statement](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/work-statement/) defines the objectives, scope, and approach for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from [W3C member organizations](https://www.w3.org/membership/list/) and [invited experts](https://www.w3.org/invited-experts/) and are supported by [Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/about/#wai-staff). +The WCAG2ICT Group Note is developed by the [WCAG2ICT Task Force](https://www.w3.org/WAI/about/groups/task-forces/wcag2ict/). The work statement defines the objectives, scope, and approach for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from W3C member organizations and invited experts and are supported by Web Accessibility Initiative (WAI) staff. ### Related Documents From 66e61b849a806c75187f628373385eb4a80bb20c Mon Sep 17 00:00:00 2001 From: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> Date: Tue, 22 Apr 2025 14:27:17 +0200 Subject: [PATCH 23/23] Update pages/standards-guidelines/wcag/non-web-ict.md Co-authored-by: Mary Jo Mueller --- pages/standards-guidelines/wcag/non-web-ict.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/standards-guidelines/wcag/non-web-ict.md b/pages/standards-guidelines/wcag/non-web-ict.md index bb7191f3e24..842f22abfab 100644 --- a/pages/standards-guidelines/wcag/non-web-ict.md +++ b/pages/standards-guidelines/wcag/non-web-ict.md @@ -83,7 +83,7 @@ While the WCAG2ICT Group Note provides guidance on applying WCAG in non-web cont ## Who WCAG2ICT is for {#for} The WCAG2ICT Group Note is for standards developers, ICT managers, ICT developers, policy makers, and any others wanting to understand how WCAG 2 can be applied to non-web documents and software. -* Accessibility [standards organizations](https://en.wikipedia.org/wiki/Standards_organization) - to provide non-web language in the success criteria and definitions and to provide interpretation notes to help the organization make any potential adjustments or notes needed for specific technologies, if needed. +* Accessibility standards organizations - to provide non-web language in the success criteria and definitions and to provide interpretation notes to help the organization make any potential adjustments or notes needed for specific technologies, if needed. * ICT managers - who are familiar with WCAG to quickly get an overview of using WCAG as an accessibility benchmark for non-web ICT. * Technology developers - to provide the language substitutions for non-web language in WCAG success criteria where existing accessibility standards don’t contain an interpretation. * Policy makers (including regulators when making regulations) - to inform them how the WCAG2ICT note is being used to influence standards requirements where WCAG is being applied to non-web ICT.