WCAG2ICT Task Force request to Update non-web-ict.md #1197
Conversation
Request to update https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/ WCAG2ICT overview page with edits from WCAG2ICT's Explainer work
✅ Deploy Preview for wai-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@maryjom @daniel-montalvo , I've made the request to edit this page per our WCAG2ICT work on the "Explainer" content we developed within the WCAG2ICT Task Force. Happy to edit further. I left this in draft in case either of you want to amend the PR prior to submitting it to WAI. |
|
Yeah thanks for that @ChrisLoiselle good to have this in draft for now -- I do plan to take a look at this and may have some comments. |
|
I think you can commit editorial changes for sure (like the links/formatting ones).
Best regards,
Mary Jo Mueller
IBM Accessibility Standards Program Manager
From: Chris Loiselle ***@***.***>
Date: Thursday, April 10, 2025 at 6:16 AM
To: w3c/wai-website ***@***.***>
Cc: Mary Jo Mueller ***@***.***>, Mention ***@***.***>
Subject: [EXTERNAL] Re: [w3c/wai-website] WCAG2ICT Task Force request to Update non-web-ict.md (PR #1197)
@ maryjom @pday1 I'm happy to commit the proposed / suggested edits that you presented here in your comments and review. Did you want me to go ahead with those or do you want to wait for the meeting to vote to do so? — Reply to this email
@maryjom<https://github.com/maryjom > @pday1<https://github.com/pday1 > I'm happy to commit the proposed / suggested edits that you presented here in your comments and review. Did you want me to go ahead with those or do you want to wait for the meeting to vote to do so?
—
Reply to this email directly, view it on GitHub<#1197 (comment) >, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABM67VBTB42QK7SR6CM7MR32YZHKFAVCNFSM6AAAAAB2UBJQ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJSGQYDIMBRGE >.
You are receiving this because you were mentioned.Message ID: ***@***.***>
[Image removed by sender.]ChrisLoiselle left a comment (w3c/wai-website#1197)<#1197 (comment) >
@maryjom<https://github.com/maryjom > @pday1<https://github.com/pday1 > I'm happy to commit the proposed / suggested edits that you presented here in your comments and review. Did you want me to go ahead with those or do you want to wait for the meeting to vote to do so?
—
Reply to this email directly, view it on GitHub<#1197 (comment) >, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABM67VBTB42QK7SR6CM7MR32YZHKFAVCNFSM6AAAAAB2UBJQ7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJSGQYDIMBRGE >.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
There was a problem hiding this comment.
+1 to @maryjom edits. Also "this document" should probably be "WCAG2ICT" or "this Note".
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Phil Day <[email protected]>
Co-authored-by: Phil Day <[email protected]>
Co-authored-by: Phil Day <[email protected]>
per what was covered in WCAG2ICT meeting on 4/10/25
|
@maryjom @pday1 @daniel-montalvo I believe I caught all additional edit actions in my commit and have accepted your recommendations as mentioned here and in the meeting on 4/10/25. |
| <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 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. |
There was a problem hiding this comment.
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?
| * [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. |
There was a problem hiding this comment.
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..
There was a problem hiding this comment.
Task Force discussed, we want to keep these links. Closed without action.
There was a problem hiding this comment.
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](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. |
There was a problem hiding this comment.
| * 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. | |
| * Legislators and/or regulators) - to inform them how the WCAG2ICT note is being used to influence standards requirements where WCAG is being applied to non-web ICT. |
There was a problem hiding this comment.
- Partial accept - Task force suggested Policy makers (including regulators when making regulations). See Mary Jo's suggestion.
| * 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. | ||
| * 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. |
There was a problem hiding this comment.
Remove link to SDOs, not relevant in this context and phrase is self explanatory.
| * 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. |
There was a problem hiding this comment.
- Accept - Remove link reference on standards org.
- Not accept - We will not change non-web to non-Web per priors on the same subject decision.
There was a problem hiding this comment.
See Mary Jo's edit below.
| 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, 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 |
There was a problem hiding this comment.
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.
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
|
@pday1 @maryjom @daniel-montalvo I've made some of the suggested edits by @daniel-montalvo . I feel that others need conversation from task force due to aspects of suggestions on what was already agreed on in the Google doc explainer. We can talk to this on the call on Thursday. |
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
|
@daniel-montalvo @maryjom @pday1 I've incorporated some, not all of the Daniel and Mary Jo edits from past couple of days. We can explore the rest on the call if need be. |
There was a problem hiding this comment.
I am more than content with current draft which I reviewed. Thanks everyone!
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Mary Jo Mueller <[email protected]>
Co-authored-by: Daniel Montalvo <[email protected]>
Co-authored-by: Mary Jo Mueller <[email protected]>
Request to update https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/ WCAG2ICT overview page with edits from WCAG2ICT's Explainer work
@netlify /standards-guidelines/wcag/non-web-ict/