Proposed updates to the WCAG2ICT work statement #942
Conversation
This is to update the work statement for phase 2 work remaining.
✅ Deploy Preview for wai-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Hi @maryjom I read through this and it reads well. I won't approve until we talk through it on the upcoming task force call.
@ChrisLoiselle This extra markup is handled by the W3C website rendering/processing as it was already in the file and then appears on the rendered page as the table of contents at the top of the page. I don't know how to get a view that is the rendered content in my branch. |
|
|
||
| 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 |
There was a problem hiding this comment.
I am of the opinion that line 55 should be moved to in scope! (But maybe soften "determination" to "recommendation"?
| @@ -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. | |||
There was a problem hiding this comment.
"due to regulatory schedule needs" seems a bit overstated. Did any regulators/legislators make the ask?
I think it could be "due to the importance of having this updated guidance available in advance of pending regulation".
There was a problem hiding this comment.
This exact statement was in the original work statement and left unchanged, just changing to add in the date of what was already done.
There was a problem hiding this comment.
I am okay with original language.
This is to update the work statement for phase 2 work remaining.