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 <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Phil Day <113425927+pday1@users.noreply.github.com>
Co-authored-by: Phil Day <113425927+pday1@users.noreply.github.com>
Co-authored-by: Phil Day <113425927+pday1@users.noreply.github.com>
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.
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
|
@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 <49305434+daniel-montalvo@users.noreply.github.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
|
@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 <maryjom@us.ibm.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
| [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/). |
There was a problem hiding this comment.
I think some of these link targets are outdated:
| *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/). | |
| *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 at a Glance]](https://www.w3.org/WAI/standards-guidelines/wcag/glance/) and [How to Meet WCAG (Quick Reference)](https://www.w3.org/WAI/WCAG22/quickref/). |
|
Pending edits to Word document by Tamsin per Daniel. Mary Jo to review and add comments as applicable in the Word document. |
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/