-
Notifications
You must be signed in to change notification settings - Fork 257
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.
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
Update FAQ to address new SC in non-Web content #393
Comments
Given the (background) work on WCAG2ICT, can this be closed? |
Following up on this. The WCAG2ICT FAQ page states this:
Is that content enough to close this issue? |
well, there's the underlying problem that WCAG2ICT should have been updated to cover the "new" 2.1 SCs, but hasn't ... but as I don't see any movement on that any time soon (and of course then then new upcoming 2.2 SCs) ... |
@patrickhlauke might want to take a peek at today's WG agenda... :) |
Putting aside the lack of momentum on WCAG2ICT and today's agenda, the original comment was that the WG had agreed to address WCAG 2.1 in the WCAG FAQs, which seems to have been done. I've made an issue in the WAI Intro To WCAG repo to update that reference to WCAG 2.2 when it becomes a recommendation. |
agenda items are one thing. seeing it actually updated is another... |
@patrickhlauke it is in the proposed charter as well, momentum is gathering. Regardless of that, it looks like this isn't something we solve in WCAG anyway and Francis has raised it in the appropriate repo, so I'll close this. |
From @michael-n-cooper on April 17, 2018 22:6
#752 asks whether the WCAG 2.1 SC have been reviewed for applicability to non-web content. The WG agreed to address this question in the FAQ. Raising this issue to track separately from the CR comment process.
Copied from original issue: w3c/wcag21#866
The text was updated successfully, but these errors were encountered: