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

2.1 and 2.2 version documents mixed up #1207

Closed
guyhickling opened this issue Jul 12, 2020 · 6 comments
Closed

2.1 and 2.2 version documents mixed up #1207

guyhickling opened this issue Jul 12, 2020 · 6 comments

Comments

@guyhickling
Copy link

A WCAG version document has just been released (10 July) headed WCAG 2.1, and containing only 2.1 references throughout. But it contains the new 2.2 SCs (e.g. Focus Visible Enhanced, and Dragging) - and without the "[new]" flags shown in the genuine 2.2 documents. The URL is https://www.w3.org/WAI/WCAG21/Understanding/. These two streams of work appear to be getting mixed up!

@yatil
Copy link
Contributor

yatil commented Jul 13, 2020

Probably related to #1177 and #1178.

@guyhickling
Copy link
Author

I agree, especially 1178 I imagine. Looks to me like the wrong files have been merged in a GitHub merge? It needs to be untangled before the position gets worse, or there will be documents with the wrong content in them popping up all over the place.

@alastc
Copy link
Contributor

alastc commented Jul 15, 2020

Yep, this is a duplicate, it is in progress, we'll separate before more go in.

@alastc alastc closed this as completed Jul 15, 2020
@guyhickling
Copy link
Author

Alastair, was this due to the work for changing 2.4.7 from AA to A?

@alastc
Copy link
Contributor

alastc commented Jul 16, 2020

That's what highlighted it, but there are other reasons to separate the versions. One being that most people assume we have separate docs between versions anyway!

@patrickhlauke
Copy link
Member

patrickhlauke commented Jul 16, 2020

Also add #1068 to the mix (and this, which was fixed, but caused by the same intermixing problem #1043 (comment))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants