Skip to content

WCAG2ICT Task Force request to Update non-web-ict.md #1197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 23 commits into
base: main
Choose a base branch
from
Draft

WCAG2ICT Task Force request to Update non-web-ict.md #1197

Changes from all commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
d4e4930
Update non-web-ict.md
ChrisLoiselle Apr 7, 2025
f614ca9
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
676e18b
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
e01e7e8
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
cf7bb91
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
1e4465a
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
a5390bb
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
96e7266
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
875658f
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 10, 2025
fb11180
Update non-web-ict.md
ChrisLoiselle Apr 10, 2025
1561c19
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 15, 2025
00ba8e1
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 15, 2025
000685a
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 15, 2025
7f7fcdb
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 15, 2025
61e72bb
Update pages/standards-guidelines/wcag/non-web-ict.md
daniel-montalvo Apr 15, 2025
5ecd2b6
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 16, 2025
adc5086
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 16, 2025
5a2b344
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 16, 2025
1b98cfa
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 17, 2025
ea705b8
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 17, 2025
51504a8
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 17, 2025
bd94a86
Update pages/standards-guidelines/wcag/non-web-ict.md
ChrisLoiselle Apr 17, 2025
66e61b8
Update pages/standards-guidelines/wcag/non-web-ict.md
daniel-montalvo Apr 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 66 additions & 8 deletions pages/standards-guidelines/wcag/non-web-ict.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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/
Expand All @@ -12,7 +12,7 @@ github:

image: /content-images/wcag/general-social.jpg
footer: >
<p><strong>Editor:</strong> <a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>. Contributors: Mary Jo Mueller, Judy Brewer, and Daniel Montalvo.</p>
<p><strong>Editor:</strong> <a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>. Contributors: Mary Jo Mueller, Chris Loiselle, and Daniel Montalvo.</p>
<p>Developed with input from the <a href="https://www.w3.org/groups/tf/wcag2ict/">WCAG2ICT Task Force</a> and the Education and Outreach Working Group (<a href="https://www.w3.org/groups/wg/eowg/">EOWG</a>).</p>
---

Expand Down Expand Up @@ -44,24 +44,63 @@ Quick link:

## Introduction {#intro}

<cite>Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)</cite> 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).
<cite>Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)</cite> 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if linking to WCAG's definition of normative and informative is a good idea. We should think about how much we want to link to other places. This is a potential distraction for readers. Aren't normative and informative self-explanatory in this context?

Suggested change
* [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.
* **Informative guidance** that is not normative and that does not set requirements.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was something that the link was in the WCAG2ICT Note and when I copied in the text, and the link remained. However, there are those of us that work in the standards world and we know what normative vs. informative is. Not sure policy makers and others who are new to reading standards know the distinction. I don't think having a link is harmful here, and would prefer it be kept..

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Task Force discussed, we want to keep these links. Closed without action.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ChrisLoiselle

Thanks. I understand TF rationale. I'd like to leave this open in case this serves as guidance for other WAI Staff that will review this.

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

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

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

*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 WCAG2ICT

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.

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.

*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
* [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

## 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

W3C has traditionally avoided "policy makers" as an audience. Could we do with "regulators" as a broader term? Applies to subsequent appearances of the word.

Suggested change
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.
The WCAG2ICT Group Note is for standards developers, ICT managers, ICT developers, regulators, and any others wanting to understand how WCAG 2 can be applied to non-web documents and software.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Task Force Reviewed. We do not want to accept change. Policy makers is more accurate. Policy makers include people inside a company or organization.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ChrisLoiselle

Thanks. I understand TF rationale. I'd like to leave this open in case this serves as guidance for other WAI Staff that will review this.

* 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.
* 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}

Expand All @@ -85,7 +124,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 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Traditionally, we have avoided having all these pointers to external resources on the overview pages. I think these belong more on the Note itself. I presume this is one thing that other WAI Staff may have comments on. Would we be OK moving these to the document itself (some of them are already there) and pointing to that section if we want to explicitly call them out in here.


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](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/))
* [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](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.
* [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

Expand Down