Skip to content
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

Proposed updates to the WCAG2ICT work statement #942

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
+47 −33
Open

Proposed updates to the WCAG2ICT work statement #942

Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
05db031
Proposed updates to the WCAG2ICT work statement
maryjom Oct 31, 2024
52dd78c
add "and"
maryjom Oct 31, 2024
fa5789c
Add paragraph markup on note
maryjom Oct 31, 2024
afed7bb
Fix up markdown
maryjom Oct 31, 2024
1875227
In Phase 1, added link to published Note
maryjom Oct 31, 2024
c1d6c41
Incorporate changes discussed in the 21 November meeting
maryjom Nov 21, 2024
6d712c7
Update work-statement.md
maryjom Dec 9, 2024
8ee5128
Fix misspelling
maryjom Dec 10, 2024
894e4b1
Update several sections to consistently reflect the Phase 2 work
maryjom Jan 7, 2025
b6459c7
Update pages/about/groups/task-forces/wcag2ict/work-statement.md
maryjom Jan 7, 2025
ca384d5
Clarify some of the content I added
maryjom Jan 7, 2025
d27ab7d
More clarification of the content in the status and overview sections
maryjom Jan 7, 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
80 changes: 47 additions & 33 deletions pages/about/groups/task-forces/wcag2ict/work-statement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,92 +24,106 @@ 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.

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

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

## Scope of Work

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; and
* address challenges in [Open issues labeled WCAG2ICT](https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+label%3Awcag2ict).
* 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
* 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;
* 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;
* developing a normative standard or any normative requirements.

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

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

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

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

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)
* 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 can be found in the [WCAG2ICT participants](https://www.w3.org/groups/tf/wcag2ict/participants/) list.

## Communication

Expand Down Expand Up @@ -140,7 +154,7 @@ Contact [Daniel Montalvo](mailto:[email protected]) 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:[email protected])
* **Co-facilitators:** [Mary Jo Mueller](mailto:[email protected].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:**
Expand All @@ -150,4 +164,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).
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).