Update WCAG2ICT versions section #1717
Conversation
✅ Deploy Preview for wai-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
remibetin
left a comment
remibetin
left a comment
There was a problem hiding this comment.
Thanks @daniel-montalvo. I've added a comment with a suggestion.
remibetin
left a comment
remibetin
left a comment
There was a problem hiding this comment.
LGTM. I'm adding @shawna-slh as a reviewer for approval before publication.
daniel-montalvo
force-pushed
the
wcag2ict-overview-updates
branch
from
c250236 to
0cac2cd
Compare
remibetin
left a comment
remibetin
left a comment
There was a problem hiding this comment.
@shawna-slh @daniel-montalvo I've added new suggestions that do not specify the publication dates. I've also added the type of document.
|
|
||
| ### WCAG2ICT versions | ||
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) — published on 15 November 2024, updated on 21 August 2025, 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/) — first published on 15 November 2024, covers WCAG 2.0, 2.1, and 2.2. This document is actively maintained. |
There was a problem hiding this comment.
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) — first published on 15 November 2024, covers WCAG 2.0, 2.1, and 2.2. This document is actively maintained. | |
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) – W3C Group Note](https://www.w3.org/TR/wcag2ict-22/) covers WCAG 2.0, 2.1, and 2.2 and is periodically updated – for all versions, see the [publication history](https://www.w3.org/standards/history/wcag2ict-22/)) |
There was a problem hiding this comment.
Thanks @remibetin
Not quite sure about "periodically updated" without giving a reason why. The update cadence may decline after these updates. there is a couple of things I'd like to address plus there's also the AA success criteria but, after that, there's not much plan.
Why not relate this more directly to "if WCAG itself is updated then we need to keep this in sync?
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) — first published on 15 November 2024, covers WCAG 2.0, 2.1, and 2.2. This document is actively maintained. | |
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) — first published on 15 November 2024, covers WCAG 2.0, 2.1, and 2.2. This document is expected to evolve alongside WCAG 2 |
There was a problem hiding this comment.
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) — first published on 15 November 2024, covers WCAG 2.0, 2.1, and 2.2. This document is actively maintained. | |
| * [Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/) covers WCAG 2.0, 2.1, and 2.2 and is expected to evolve alongside WCAG 2 – for all versions, see the [publication history](https://www.w3.org/standards/history/wcag2ict-22/) |
Why not relate this more directly to "if WCAG itself is updated then we need to keep this in sync?
👍
@daniel-montalvo A slightly different suggestion that removes the date, uses only one sentence and adds a link to the publication history
Co-authored-by: Rémi Bétin <[email protected]>
@netlify /