Skip to content
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

Closed
michael-n-cooper opened this issue Jun 29, 2018 · 7 comments
Closed

Update FAQ to address new SC in non-Web content #393

michael-n-cooper opened this issue Jun 29, 2018 · 7 comments
Assignees
Labels

Comments

@michael-n-cooper
Copy link
Member

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

@alastc
Copy link
Contributor

alastc commented Apr 24, 2019

Given the (background) work on WCAG2ICT, can this be closed?

@fstrr
Copy link
Contributor

fstrr commented May 10, 2022

Following up on this. The WCAG2ICT FAQ page states this:

"Note: WCAG2ICT is still relevant for later versions of WCAG 2. For example, WCAG 2.1 does not change the requirements of WCAG 2.0 that are addressed in WCAG2ICT; WCAG 2.1 adds additional requirements. W3C may update WCAG2ICT in the future to add the additional requirements from later versions of WCAG 2."

Is that content enough to close this issue?

@fstrr fstrr self-assigned this May 10, 2022
@patrickhlauke
Copy link
Member

patrickhlauke commented May 10, 2022

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) ...

@awkawk
Copy link
Member

awkawk commented May 10, 2022

@patrickhlauke might want to take a peek at today's WG agenda... :)

@fstrr
Copy link
Contributor

fstrr commented May 10, 2022

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.

@patrickhlauke
Copy link
Member

@patrickhlauke might want to take a peek at today's WG agenda... :)

agenda items are one thing. seeing it actually updated is another...

@alastc
Copy link
Contributor

alastc commented May 11, 2022

@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.

@alastc alastc closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants