From 05db0312af2262d3997ff2a3692e116189a9de2c Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 31 Oct 2024 14:26:28 -0500 Subject: [PATCH 01/12] Proposed updates to the WCAG2ICT work statement This is to update the work statement for phase 2 work remaining. --- .../task-forces/wcag2ict/work-statement.md | 45 ++++++++++--------- 1 file changed, 24 insertions(+), 21 deletions(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index a90b0bd9d41..7d49aa9c459 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -42,15 +42,17 @@ The work of the task force includes: * Producing an updated Working Group Note (a form of W3C Technical Report)—following the W3C process under the coordination, review, and approval of the AG WG—that describes: * how each of the new WCAG 2.x A, AA, and AAA success criteria could apply to non-Web ICT; * how each of the new WCAG 2.x guidelines could apply to non-Web ICT; - * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software; and - * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict). + * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software; + * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict); + * provide an explainer that clarifies the usage of WCAG2ICT Explicitly out of scope for the WCAG2ICT Task Force work are: * proposing changes to WCAG 2.x; * developing techniques or interpretations of WCAG 2.x for implementing WCAG 2.x in Web technologies; * developing any specific, sufficient techniques, including platform-specific techniques, for implementing WCAG 2.x in non-Web ICT, though examples may be in scope; -* determining whether WCAG, as a whole, _should be_ applied to non-web content; and +* determining whether WCAG, as a whole, _should be_ applied to non-web content; +* providing a determination of which success criteria are applicable to a particular non-web technology; and * developing a normative standard or any normative requirements. ## Approach @@ -61,7 +63,7 @@ The primary effort of this Task Force is to describe how to interpret WCAG 2.x a To efficiently develop the Working Group Note, work may be broken down into sub-groups, under the coordination of the Task Force facilitator(s) following established AG WG procedures for sub-groups. -The work will be focused in stages to ensure WCAG2ICT content is available in time for use in upcoming updates to regulations and standards (like the EN 301 549) that apply WCAG to non-web technology. This means prioritizing Level A and AA criteria and known issues in the existing Note. WCAG2ICT could potentially need to be published before addressing Level AAA due to regulatory schedule needs. If publication is needed prior to addressing Level AAA criteria, another update to the WCAG2ICT Note may be necessary. +The work will be focused in stages to ensure WCAG2ICT content is available in time for use in upcoming updates to regulations and standards (like the EN 301 549) that apply WCAG to non-web technology. This means prioritizing Level A and AA criteria and known issues in the existing Note. WCAG2ICT was published on 4 November 2024 before addressing Level AAA, due to regulatory schedule needs. The next update to WCAG2ICT will address Level AAA success criteria, with republication of the WCAG2ICT Note once they have been incorporated and gone through the W3C review and publication process. The work will be carried out through a series of document drafts, all publicly visible, with opportunities for public comment through publicly available comment lists. In particular, key stakeholders such as developers, evaluators, accessibility experts, researchers, procurement experts, and end users will be regularly involved in the development process. Key participants will be drawn from people with expertise not only in Web technologies, but also those with specific accessibility expertise, including the development of accessible frameworks, platforms, user interface components, and software covering a broad variety of computing environments. @@ -71,45 +73,46 @@ The following sections contain rough timelines for the WCAG2ICT work. Actual tim As previously mentioned, a phased delivery of the WCAG2ICT Working Group Note will likely be necessary to provide timely guidance for upcoming regulatory and standards updates. -### Phase 1 +### Phase 1 (completed) -Goals are to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria, and make other necessary updates to the other content in the WCAG2ICT document to align with WCAG 2.2. In addition, this phase will address known documented issues. +Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria and making other necessary updates to the other content in the WCAG2ICT document to align with WCAG 2.2 have been completed. This phase also addressed known documented issues. -Note: To include WCAG 2.2, the Recommendation version standard must be published with sufficient time to update the draft WCAG2ICT Note with finalized requirements verbiage. - -* April - August 2022: +* Plan: April - August 2022, Actual: April - August 2022 * obtain approval from AG WG and launch the WCAG2ICT Task Force; * recruit TF participants with necessary expertise. -* September 2022: - * develop a brief requirements document and obtain agreement from AG WG; -* October 2022 - April 2023: +* Plan: September 2022, Actual: October 2022 + * develop a brief requirements document (as inclurporated into the work statement) and obtain agreement from AG WG ; +* Plan: October 2022 - April 2023, Actual: October 2022 - August 2023 * develop an initial draft with updates to the Working Group Note; * develop initial discussion drafts of remaining sections of the Note; * develop initial discussion drafts of Note sections; - * start reporting to the AG WG (schedule and frequency TBD) -* July - June 2023: + * start reporting to the AG WG (schedule and frequency aligned to when groups of SCs are added) +* Plan: July - June 2023, Actual: August 2023 - July 2024: * incorporate first feedback from TF and AG WG into a (publicly visible) Editors’ Draft; * publish Draft of the updated Working Group Note through the AG WG; * start processing feedback on draft. -* July - October 2023: +* Plan: July - October 2023, Actual: July - October 2024 * process feedback on document, further develop and edit WG Note; * publish updated formal draft, process comments. -* November 2023: +* Plan: November 2023, Actual: November 2024: * Publish updated WCAG2ICT Note. ### Phase 2 -The next phase of updates would include any other in-scope work, including Level AAA, that was not addressed in Phase 1. Details of the Phase 2 timeline will be developed outside of this document when more is known about the scope of work left to do. +The next phase of updates will include any other in-scope work, including: +* addition of guidance for Level AAA success criteria + NOTE: Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki. +* development of a WCAG2ICT Explainer. An initial outline is available in the Google doc [WCAG2ICT Explainer](https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?usp=sharing). ## Liaisons -While there are no direct dependencies at the Task Force level (please see [deliverables section of the AG WG Charter](https://www.w3.org/2019/12/ag-charter#deliverables) for more information). The following proposed participating liaisons may change pending confirmation, and/or be expanded: +While there are no direct dependencies at the Task Force level (please see [deliverables section of the AG WG Charter](https://www.w3.org/2019/12/ag-charter#deliverables) for more information), the following are participating liaisons, which may change and/or be expanded over time: * Liaisons from worldwide accessibility consulting and advocacy groups * Liaisons from worldwide standards organizations (ISO, ETSI, CEN and CENELEC, etc.) * Liaisons from worldwide government and/or regulatory agencies considering referencing the updated WCAG2ICT (U.S. Access Board, EU, Canada, potentially others) -The list of liaisons will be updated to show official organization representation of the participants in the task force, once known. +The list of liaisons will be updated to show official organization representation of the participants in the task force, as found in the [WCAG2ICT participants](https://www.w3.org/groups/tf/wcag2ict/participants/) list. ## Communication @@ -140,7 +143,7 @@ Contact [Daniel Montalvo](mailto:dmontalvo@w3.org) to become a participant of th Staff contacts from the Accessibility Guidelines Working Group oversee attention to W3C Process with respect to the chartered requirements of the Working Group. The facilitators set agenda, lead meetings, determine consensus, and are the primary liaison to the Working Group. -* **Facilitator:** [Mary Jo Mueller](mailto:maryjom@us.ibm.com) +* **Co-facilitators:** [Mary Jo Mueller](mailto:maryjom@us.ibm.com) and [Chris Loiselle](mailto:chris.loiselle@oracle.com) * **Staff Contact:** [Daniel Montalvo](http://www.w3.org/People#dmontalvo) * **Liaison to AG WG:** one of the AG WG co-chairs * **Editorial Team:** @@ -150,4 +153,4 @@ Staff contacts from the Accessibility Guidelines Working Group oversee attention ## Patent Policy -This Task Force is part of the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG Working Group](https://www.w3.org/groups/wg/ag/ipr). \ No newline at end of file +This Task Force is part of the [AG Working Group Charter](https://www.w3.org/WAI/GL/charter), which operates under the [W3C Patent Policy](https://www.w3.org/Consortium/Patent-Policy-20200915/) (15 September 2020 Version). W3C maintains a public list of any patent disclosures made in connection with the deliverables of the [AG Working Group](https://www.w3.org/groups/wg/ag/ipr). From 52dd78cb993d31f2c2ab1fb531c7f6ebe73011ce Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 31 Oct 2024 14:27:33 -0500 Subject: [PATCH 02/12] add "and" --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 7d49aa9c459..83679c4b434 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -43,7 +43,7 @@ The work of the task force includes: * how each of the new WCAG 2.x A, AA, and AAA success criteria could apply to non-Web ICT; * how each of the new WCAG 2.x guidelines could apply to non-Web ICT; * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software; - * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict); + * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict); and * provide an explainer that clarifies the usage of WCAG2ICT Explicitly out of scope for the WCAG2ICT Task Force work are: From fa5789c43d58c475a9f9b9afe161830e9ad16838 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 31 Oct 2024 14:34:40 -0500 Subject: [PATCH 03/12] Add paragraph markup on note --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 83679c4b434..740268e9895 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -101,7 +101,7 @@ Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria a The next phase of updates will include any other in-scope work, including: * addition of guidance for Level AAA success criteria - NOTE: Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki. +

NOTE: Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki.

* development of a WCAG2ICT Explainer. An initial outline is available in the Google doc [WCAG2ICT Explainer](https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?usp=sharing). ## Liaisons From afed7bb074b4dc8227088f532d7d0444de68bca6 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 31 Oct 2024 14:39:03 -0500 Subject: [PATCH 04/12] Fix up markdown --- .../groups/task-forces/wcag2ict/work-statement.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 740268e9895..1ed50d17091 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -100,17 +100,16 @@ Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria a ### Phase 2 The next phase of updates will include any other in-scope work, including: -* addition of guidance for Level AAA success criteria -

NOTE: Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki.

-* development of a WCAG2ICT Explainer. An initial outline is available in the Google doc [WCAG2ICT Explainer](https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?usp=sharing). +* Addition of guidance for Level AAA success criteria. Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki. +* Development of a WCAG2ICT Explainer. An initial outline is available in the Google doc [WCAG2ICT Explainer](https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?usp=sharing). ## Liaisons While there are no direct dependencies at the Task Force level (please see [deliverables section of the AG WG Charter](https://www.w3.org/2019/12/ag-charter#deliverables) for more information), the following are participating liaisons, which may change and/or be expanded over time: -* Liaisons from worldwide accessibility consulting and advocacy groups -* Liaisons from worldwide standards organizations (ISO, ETSI, CEN and CENELEC, etc.) -* Liaisons from worldwide government and/or regulatory agencies considering referencing the updated WCAG2ICT (U.S. Access Board, EU, Canada, potentially others) +* Liaisons from worldwide accessibility consulting and advocacy groups +* Liaisons from worldwide standards organizations (ISO, ETSI, CEN and CENELEC, etc.) +* Liaisons from worldwide government and/or regulatory agencies considering referencing the updated WCAG2ICT (U.S. Access Board, EU, Canada, potentially others) The list of liaisons will be updated to show official organization representation of the participants in the task force, as found in the [WCAG2ICT participants](https://www.w3.org/groups/tf/wcag2ict/participants/) list. From 1875227447d4775088835b37d9daf4a67a7fe3a6 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 31 Oct 2024 14:44:13 -0500 Subject: [PATCH 05/12] In Phase 1, added link to published Note --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 1ed50d17091..fb692a9b1ca 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -75,6 +75,8 @@ As previously mentioned, a phased delivery of the WCAG2ICT Working Group Note wi ### Phase 1 (completed) +Phase 1 - Published update to [Guidance on Applying WCAG 2 to Non-web Information and Communications Technologies (WCAG2ICT) Group Note](https://www.w3.org/TR/wcag2ict-22/) (8 October 2024). + Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria and making other necessary updates to the other content in the WCAG2ICT document to align with WCAG 2.2 have been completed. This phase also addressed known documented issues. * Plan: April - August 2022, Actual: April - August 2022 From c1d6c41418008ff553ca86d50231e017cb1b4446 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Thu, 21 Nov 2024 10:28:07 -0600 Subject: [PATCH 06/12] Incorporate changes discussed in the 21 November meeting See the [21 Nov. meeting minutes](https://www.w3.org/2024/11/21-wcag2ict-minutes.html) for details of what was discussed. --- .../groups/task-forces/wcag2ict/work-statement.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index fb692a9b1ca..29d5665e2b6 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -40,11 +40,15 @@ The work of the task force includes: * Determining how to apply each of the new WCAG 2.1 and WCAG 2.2 (hereafter called “WCAG 2.x") guidelines and Levels A, AA, and AAA success criteria to non-Web ICT; this includes provision of additional details for application to closed product software and where applying individual criteria might be difficult and why; and * Producing an updated Working Group Note (a form of W3C Technical Report)—following the W3C process under the coordination, review, and approval of the AG WG—that describes: - * how each of the new WCAG 2.x A, AA, and AAA success criteria could apply to non-Web ICT; - * how each of the new WCAG 2.x guidelines could apply to non-Web ICT; - * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software; - * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict); and + * how each of the new WCAG 2.x A and AA success criteria could apply to non-Web ICT (done); + * how each of the new WCAG 2.x guidelines could apply to non-Web ICT (done); + * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software (done); + * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict) (done); and * provide an explainer that clarifies the usage of WCAG2ICT + * where known, give examples of some Success Criteria which may not be applicable to a particular non-web technology; and + * as needed, suggested changes to success criteria normative language to more clearly align with non-web software and document technologies; and + NOTE: This would not be suggested changes to change WCAG itself, but instead provide language more meaninful in non-web contexts. For example, provide alternative language in criteria that the WCAG normative language uses CSS pixels, to use language more appropriate for non-web technologies. + * how each of the WCAG 2.x Level AAA success criteria could apply to non-web technologies. Explicitly out of scope for the WCAG2ICT Task Force work are: @@ -52,7 +56,6 @@ Explicitly out of scope for the WCAG2ICT Task Force work are: * developing techniques or interpretations of WCAG 2.x for implementing WCAG 2.x in Web technologies; * developing any specific, sufficient techniques, including platform-specific techniques, for implementing WCAG 2.x in non-Web ICT, though examples may be in scope; * determining whether WCAG, as a whole, _should be_ applied to non-web content; -* providing a determination of which success criteria are applicable to a particular non-web technology; and * developing a normative standard or any normative requirements. ## Approach From 6d712c79bd5eb5eb9ffce5862111c758c4a82901 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Mon, 9 Dec 2024 16:11:03 -0600 Subject: [PATCH 07/12] Update work-statement.md --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 29d5665e2b6..3f5d43e4bd0 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -105,8 +105,8 @@ Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria a ### Phase 2 The next phase of updates will include any other in-scope work, including: -* Addition of guidance for Level AAA success criteria. Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki. * Development of a WCAG2ICT Explainer. An initial outline is available in the Google doc [WCAG2ICT Explainer](https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?usp=sharing). +* Addition of guidance for Level AAA success criteria. Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki. ## Liaisons From 8ee5128cde42b2f36e9f7371efa872ea0e4cfd36 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 10 Dec 2024 09:59:28 -0600 Subject: [PATCH 08/12] Fix misspelling --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 3f5d43e4bd0..2570c2f3852 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -47,7 +47,7 @@ The work of the task force includes: * provide an explainer that clarifies the usage of WCAG2ICT * where known, give examples of some Success Criteria which may not be applicable to a particular non-web technology; and * as needed, suggested changes to success criteria normative language to more clearly align with non-web software and document technologies; and - NOTE: This would not be suggested changes to change WCAG itself, but instead provide language more meaninful in non-web contexts. For example, provide alternative language in criteria that the WCAG normative language uses CSS pixels, to use language more appropriate for non-web technologies. + NOTE: This would not be suggested changes to change WCAG itself, but instead provide language more meaningful in non-web contexts. For example, provide alternative language in criteria that the WCAG normative language uses CSS pixels, to use language more appropriate for non-web technologies. * how each of the WCAG 2.x Level AAA success criteria could apply to non-web technologies. Explicitly out of scope for the WCAG2ICT Task Force work are: From 894e4b19370e7e4332eef848e3f7a8bece32e51f Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 7 Jan 2025 12:27:30 -0600 Subject: [PATCH 09/12] Update several sections to consistently reflect the Phase 2 work Also incorporated Mitch's two comments from the PR --- .../task-forces/wcag2ict/work-statement.md | 43 +++++++++++-------- 1 file changed, 24 insertions(+), 19 deletions(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 2570c2f3852..d08a01e43fa 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -24,7 +24,9 @@ The WCAG2ICT Task Force is a task force of the [Accessibility Guidelines Working ## Status -This work statement was [approved by the AG WG on 26 October 2022](https://lists.w3.org/Archives/Public/w3c-wai-gl/2022AprJun/0280.html). The task force is active. +This work statement was [approved by the AG WG on @@insert date approved here@@](https://lists.w3.org/Archives/Public/w3c-wai-gl/2022AprJun/0280.html). The task force is active. + +The work statement describes which of the WCAG2ICT Phase 1 objectives have been completed and what are the Phase 2 objectives for the WCAG2ICT Note. NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). @@ -32,7 +34,9 @@ NOTE: This work is mentioned in the [Other Deliverables section of the current A 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). -This Task Force was formed to update the 2013 “[Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict/)" Working Group Note published on 5 September 2013. Updates are needed to include new guidelines and success criteria added in the WCAG 2.1 Recommendation as well as new requirements added in WCAG 2.2. WCAG2ICT was developed to describe how to apply WCAG 2.0 and its principles, guidelines, and success criteria to non-web ICT (Information and Communications Technologies). WCAG2ICT also plans to add new content that identifies problematic WCAG provisions when applied to non-Web ICT. +The WCAG2ICT Phase 1 objectives have been completed by incorporating guidance for WCAG 2.1 and 2.2 guidelines, Level A and AA success criteria, and their associated glossary definitions. WCAG2ICT also added new content that identifies problematic WCAG success criteria when applied to non-Web ICT. The 2024 [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published as a result. + +This work statement sets further objectives for Phase 2 of the WCAG2ICT Note updates as there have been concerns with determining which success criteria can (or should) apply for a particular technology as well as the possibility of suggesting normative language changes to some success criteria to make them more directly applicable in non-web contexts. In addition, the task force would like to address misunderstandings of what the WCAG2ICT Note does and does not provide in a brief which we hope will address incorrect assumptions and provide an explanation of problems that the WCAG2ICT Note does not solve. ## Scope of Work @@ -40,16 +44,17 @@ The work of the task force includes: * Determining how to apply each of the new WCAG 2.1 and WCAG 2.2 (hereafter called “WCAG 2.x") guidelines and Levels A, AA, and AAA success criteria to non-Web ICT; this includes provision of additional details for application to closed product software and where applying individual criteria might be difficult and why; and * Producing an updated Working Group Note (a form of W3C Technical Report)—following the W3C process under the coordination, review, and approval of the AG WG—that describes: - * how each of the new WCAG 2.x A and AA success criteria could apply to non-Web ICT (done); - * how each of the new WCAG 2.x guidelines could apply to non-Web ICT (done); - * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software (done); - * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict) (done); and - * provide an explainer that clarifies the usage of WCAG2ICT + * how each of the new WCAG 2.x A and AA success criteria could apply to non-Web ICT (completed in Phase 1); + * how each of the new WCAG 2.x guidelines could apply to non-Web ICT (completed in Phase 1); + * clarification of challenges of applying particular WCAG 2.x success criteria to non-web ICT, including closed product software (completed) in Phase 1; + * address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict) (completed in Phase 1); and + * provide a concise, high-level overview or introduction to WCAG2ICT, explaining its purpose and how to use it * where known, give examples of some Success Criteria which may not be applicable to a particular non-web technology; and * as needed, suggested changes to success criteria normative language to more clearly align with non-web software and document technologies; and - NOTE: This would not be suggested changes to change WCAG itself, but instead provide language more meaningful in non-web contexts. For example, provide alternative language in criteria that the WCAG normative language uses CSS pixels, to use language more appropriate for non-web technologies. * how each of the WCAG 2.x Level AAA success criteria could apply to non-web technologies. +NOTE: "suggested changes to success criteria" would not be suggestions to change WCAG itself, but instead to provide language more meaningful in non-web contexts. For example, in criteria where the WCAG normative language uses CSS pixels, the Task Force could provide alternative language more appropriate for non-web technologies. + Explicitly out of scope for the WCAG2ICT Task Force work are: * proposing changes to WCAG 2.x; @@ -60,27 +65,27 @@ Explicitly out of scope for the WCAG2ICT Task Force work are: ## Approach -WCAG2ICT is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. We have an AG WG co-chair liaison to ensure draft content is taken to the AG WG for review as it progresses. +WCAG2ICT is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. Draft content is periodically taken to the AG WG for review as it progresses. The primary effort of this Task Force is to describe how to interpret WCAG 2.x and its principles, guidelines, success criteria and conformance requirements when applying them to non-web ICT; and evaluating what WCAG Conformance means in the context of non-Web ICT. The resulting Working Group Note will include a discussion of the application of each of the criteria in WCAG 2.x to non-Web ICT, including their interface components and platforms, and the extent to which [WCAG Conformance](http://www.w3.org/TR/WCAG20/#conformance) is meaningful to non-Web ICT. -To efficiently develop the Working Group Note, work may be broken down into sub-groups, under the coordination of the Task Force facilitator(s) following established AG WG procedures for sub-groups. +To efficiently develop the Working Group Note, work is sometimes broken down into sub-groups, under the coordination of the Task Force facilitators following established AG WG procedures for sub-groups. -The work will be focused in stages to ensure WCAG2ICT content is available in time for use in upcoming updates to regulations and standards (like the EN 301 549) that apply WCAG to non-web technology. This means prioritizing Level A and AA criteria and known issues in the existing Note. WCAG2ICT was published on 4 November 2024 before addressing Level AAA, due to regulatory schedule needs. The next update to WCAG2ICT will address Level AAA success criteria, with republication of the WCAG2ICT Note once they have been incorporated and gone through the W3C review and publication process. +The work has been focused in stages to ensure WCAG2ICT content was made available in time for use in upcoming updates to regulations and standards (like the EN 301 549) that apply WCAG to non-web technology. Phase 1 prioritized Level A and AA criteria and known issues in the existing Note and was published on 4 November 2024. The next update to WCAG2ICT plans to address the remaining in-scope items detailed in the [Scope of Work](#scope-of-work) section. -The work will be carried out through a series of document drafts, all publicly visible, with opportunities for public comment through publicly available comment lists. In particular, key stakeholders such as developers, evaluators, accessibility experts, researchers, procurement experts, and end users will be regularly involved in the development process. Key participants will be drawn from people with expertise not only in Web technologies, but also those with specific accessibility expertise, including the development of accessible frameworks, platforms, user interface components, and software covering a broad variety of computing environments. +The work is carried out through a series of document drafts, all publicly visible, with opportunities for public comment through publicly available comment lists. In particular, key stakeholders such as developers, evaluators, accessibility experts, researchers, procurement experts, and end users will be regularly involved in the development process. Key participants will be drawn from people with expertise not only in Web technologies, but also those with specific accessibility expertise, including the development of accessible frameworks, platforms, user interface components, and software covering a broad variety of computing environments. ## Timeline The following sections contain rough timelines for the WCAG2ICT work. Actual timelines and project management will be handled outside of this work statement, and will not be maintained herein. -As previously mentioned, a phased delivery of the WCAG2ICT Working Group Note will likely be necessary to provide timely guidance for upcoming regulatory and standards updates. +A phased delivery of the WCAG2ICT Working Group Note was necessary to provide timely guidance for upcoming regulatory and standards updates, and Phase 1 has concluded. ### Phase 1 (completed) -Phase 1 - Published update to [Guidance on Applying WCAG 2 to Non-web Information and Communications Technologies (WCAG2ICT) Group Note](https://www.w3.org/TR/wcag2ict-22/) (8 October 2024). +Published update to [Guidance on Applying WCAG 2 to Non-web Information and Communications Technologies (WCAG2ICT) Group Note](https://www.w3.org/TR/wcag2ict-22/) (8 October 2024). -Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria and making other necessary updates to the other content in the WCAG2ICT document to align with WCAG 2.2 have been completed. This phase also addressed known documented issues. +Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria and making other necessary updates to the other content in the WCAG2ICT document to align with WCAG 2.2. This phase also addressed known documented issues prior to publication. * Plan: April - August 2022, Actual: April - August 2022 * obtain approval from AG WG and launch the WCAG2ICT Task Force; @@ -104,9 +109,9 @@ Goals were to incorporate new WCAG 2.1 and 2.2 Level A and AA success criteria a ### Phase 2 -The next phase of updates will include any other in-scope work, including: -* Development of a WCAG2ICT Explainer. An initial outline is available in the Google doc [WCAG2ICT Explainer](https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?usp=sharing). -* Addition of guidance for Level AAA success criteria. Details of the Phase 2 timeline are found outside of this document. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page in the GitHub WCAG2ICT Wiki. +The next phase of updates will include the remaining in-scope work listed in the [Scope of Work[(#scope-of-work) section. + +Details of the Phase 2 timeline are found outside of this document in the GitHub WCAG2ICT Wiki. See the [schedule and milestones](https://github.com/w3c/wcag2ict/wiki/Schedule-and-milestones) page. ## Liaisons @@ -116,7 +121,7 @@ While there are no direct dependencies at the Task Force level (please see [deli * Liaisons from worldwide standards organizations (ISO, ETSI, CEN and CENELEC, etc.) * Liaisons from worldwide government and/or regulatory agencies considering referencing the updated WCAG2ICT (U.S. Access Board, EU, Canada, potentially others) -The list of liaisons will be updated to show official organization representation of the participants in the task force, as found in the [WCAG2ICT participants](https://www.w3.org/groups/tf/wcag2ict/participants/) list. +The list of liaisons can be found in the [WCAG2ICT participants](https://www.w3.org/groups/tf/wcag2ict/participants/) list. ## Communication From b6459c72493307387b75c8d4eff1a03a700e3405 Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 7 Jan 2025 12:46:07 -0600 Subject: [PATCH 10/12] Update pages/about/groups/task-forces/wcag2ict/work-statement.md --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index d08a01e43fa..9e145f11432 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -26,7 +26,7 @@ The WCAG2ICT Task Force is a task force of the [Accessibility Guidelines Working This work statement was [approved by the AG WG on @@insert date approved here@@](https://lists.w3.org/Archives/Public/w3c-wai-gl/2022AprJun/0280.html). The task force is active. -The work statement describes which of the WCAG2ICT Phase 1 objectives have been completed and what are the Phase 2 objectives for the WCAG2ICT Note. +The work statement describes the WCAG2ICT Phase 1 objectives that have been completed and the updated Phase 2 objectives for the WCAG2ICT Note. NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). From ca384d5f68502128d030e9743a3b2e3147eeadcb Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 7 Jan 2025 13:08:42 -0600 Subject: [PATCH 11/12] Clarify some of the content I added --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index 9e145f11432..f85380cb28d 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -28,7 +28,7 @@ This work statement was [approved by the AG WG on @@insert date approved here@@] The work statement describes the WCAG2ICT Phase 1 objectives that have been completed and the updated Phase 2 objectives for the WCAG2ICT Note. -NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). +NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). The WCAG2ICT Task Force plans to ensure that future AG WG charters include devlopment of this important guidance. ## Objective @@ -36,7 +36,7 @@ The objective of the WCAG2ICT Task Force is to develop documentation describing The WCAG2ICT Phase 1 objectives have been completed by incorporating guidance for WCAG 2.1 and 2.2 guidelines, Level A and AA success criteria, and their associated glossary definitions. WCAG2ICT also added new content that identifies problematic WCAG success criteria when applied to non-Web ICT. The 2024 [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published as a result. -This work statement sets further objectives for Phase 2 of the WCAG2ICT Note updates as there have been concerns with determining which success criteria can (or should) apply for a particular technology as well as the possibility of suggesting normative language changes to some success criteria to make them more directly applicable in non-web contexts. In addition, the task force would like to address misunderstandings of what the WCAG2ICT Note does and does not provide in a brief which we hope will address incorrect assumptions and provide an explanation of problems that the WCAG2ICT Note does not solve. +This work statement sets further objectives for Phase 2 of the WCAG2ICT Note updates as there have been concerns with determining which success criteria can (or should) apply for a particular technology as well as the possibility of suggesting normative language changes to some success criteria to make them more directly applicable in non-web contexts (See the scope of work section for further details and explanation). In addition, the task force would like develop content to address misunderstandings of what the WCAG2ICT Note does and does not provide which we hope will address incorrect assumptions and provide an explanation of problems that the WCAG2ICT Note does not solve; how this content will be delivered (as a separate document, web page, or within the WCAG2ICT Note) will be determined once the key content has been developed. ## Scope of Work @@ -77,7 +77,7 @@ The work is carried out through a series of document drafts, all publicly visibl ## Timeline -The following sections contain rough timelines for the WCAG2ICT work. Actual timelines and project management will be handled outside of this work statement, and will not be maintained herein. +The following sections contain rough timelines for the WCAG2ICT work. Actual timelines and project management are handled outside of this work statement, and will not be maintained herein. A phased delivery of the WCAG2ICT Working Group Note was necessary to provide timely guidance for upcoming regulatory and standards updates, and Phase 1 has concluded. From d27ab7ddf16c9a3a626e3c809dbfdc24a15deaca Mon Sep 17 00:00:00 2001 From: Mary Jo Mueller Date: Tue, 7 Jan 2025 13:59:28 -0600 Subject: [PATCH 12/12] More clarification of the content in the status and overview sections --- pages/about/groups/task-forces/wcag2ict/work-statement.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/pages/about/groups/task-forces/wcag2ict/work-statement.md b/pages/about/groups/task-forces/wcag2ict/work-statement.md index f85380cb28d..ebf3a339caa 100644 --- a/pages/about/groups/task-forces/wcag2ict/work-statement.md +++ b/pages/about/groups/task-forces/wcag2ict/work-statement.md @@ -28,15 +28,17 @@ This work statement was [approved by the AG WG on @@insert date approved here@@] The work statement describes the WCAG2ICT Phase 1 objectives that have been completed and the updated Phase 2 objectives for the WCAG2ICT Note. -NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). The WCAG2ICT Task Force plans to ensure that future AG WG charters include devlopment of this important guidance. +NOTE: This work is mentioned in the [Other Deliverables section of the current AG WG Charter.](https://www.w3.org/2019/12/ag-charter#ig-other-deliverables) The continuation of the work is also included in the [current AG WG Charter](https://www.w3.org/2023/11/ag-charter). The WCAG2ICT Task Force plans to ensure that future AG WG charters include further maintenance of this important guidance. ## Objective 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). -The WCAG2ICT Phase 1 objectives have been completed by incorporating guidance for WCAG 2.1 and 2.2 guidelines, Level A and AA success criteria, and their associated glossary definitions. WCAG2ICT also added new content that identifies problematic WCAG success criteria when applied to non-Web ICT. The 2024 [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published as a result. +The WCAG2ICT Phase 1 objectives have been completed by incorporating guidance for WCAG 2.1 and 2.2 guidelines, Level A and AA success criteria, and their associated glossary definitions. Phase 1 of WCAG2ICT also added new content that identifies problematic WCAG success criteria when applied to non-Web ICT. The 2024 [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) was published as a result. -This work statement sets further objectives for Phase 2 of the WCAG2ICT Note updates as there have been concerns with determining which success criteria can (or should) apply for a particular technology as well as the possibility of suggesting normative language changes to some success criteria to make them more directly applicable in non-web contexts (See the scope of work section for further details and explanation). In addition, the task force would like develop content to address misunderstandings of what the WCAG2ICT Note does and does not provide which we hope will address incorrect assumptions and provide an explanation of problems that the WCAG2ICT Note does not solve; how this content will be delivered (as a separate document, web page, or within the WCAG2ICT Note) will be determined once the key content has been developed. +This work statement sets further objectives for Phase 2 of the WCAG2ICT Note updates as there have been concerns with determining which success criteria can (or should) apply for a particular technology as well as the possibility of suggesting normative language changes to some success criteria to make them more directly applicable in non-web contexts (See the scope of work section for further details and explanation). + +In addition, the task force would like develop content to address misunderstandings of what the WCAG2ICT Note does and does not provide which we hope will address incorrect assumptions and provide an explanation of problems that the WCAG2ICT Note does not solve. How this content will be delivered (as a separate document, web page, or within the WCAG2ICT Note) will be determined once the key content has been developed. ## Scope of Work