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.

Sign up for GitHub

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

Jump to bottom

correct WCAG 2.1 -> WCAG 2.2 #3585

Closed
shawna-slh opened this issue Dec 5, 2023 · 4 comments · Fixed by #3588
Closed

correct WCAG 2.1 -> WCAG 2.2 #3585

shawna-slh opened this issue Dec 5, 2023 · 4 comments · Fixed by #3588
Assignees
@patrickhlauke
Labels
Editorial Substantive WCAG 2.2

Comments

@shawna-slh
Copy link
Contributor

In https://www.w3.org/WAI/WCAG22/Understanding/refer-to-wcag
@patrickhlauke
Copy link
Member

patrickhlauke commented Dec 5, 2023 •
edited
Loading

Also in most other non-SC-specific understanding docs:

I suspect the cause of this is that the same file may be used to also generate WCAG 2.1's understanding?

I'm fairly sure at some point I suggested just dropping version numbers from those files altogether, so it's a bit more evergreen (i.e. just refer to "WCAG" rather than a specific "WCAG 2.1", "WCAG 2.2", etc unless that number is needed explicitly)

@patrickhlauke
Copy link
Member

related, on https://www.w3.org/WAI/WCAG22/Understanding/about there's a "Change log"

A list of significantly updated Understanding documents since WCAG 2.1 was published:

which is woefully pointless since it only lists one change

Jan 18th 2019: Updated Understanding Non-text contrast, based on the changes from Pull request 550.

as this is clearly not something that will realistically be kept up-to-date, suggest just pulling that entire section

@patrickhlauke patrickhlauke mentioned this issue Dec 5, 2023
Merged
@patrickhlauke
Copy link
Member

For info, filed #3588 (which may or may not be controversial, we'll see)

@patrickhlauke patrickhlauke self-assigned this Dec 22, 2023
@mbgower mbgower mentioned this issue Feb 22, 2024
Merged
@mbgower
Copy link
Contributor

mbgower commented Feb 27, 2024

Removing from project board, since we are now tracking via the PR that resolves.

mbgower added a commit that referenced this issue Mar 11, 2024
@patrickhlauke @mbgower
@dav-idc @sebazai
Update general understanding documents (#3588)
31b1ad3 
* removes the woefully out-of-date (and likely never going to be
maintained) "Change log" from the
https://www.w3.org/WAI/WCAG22/Understanding/about page
* where possible, makes WCAG mentions "versionless" ("WCAG 2" instead of
"WCAG 2.0" / "WCAG 2.1" / "WCAG 2.2")
* <s>where not possible (e.g. links to techniques document), bumps to
2.2</s> EDIT: made techniques document link versionless as well
* <s>change `success criterion`/`success criteria` to `Success
Criterion`/`Success Criteria` (and correct minor instances where the
latter was used as if it were singular - "is the Success Criteria" >
"are the Success Criteria" or "is the Success Criterion")</s> EDIT: as a
result of discussions that came after this PR was made, reverting this
change, and changing any straggler references that did use uppercase
`Success Criteria` to lowercase `success criteria`
* adds `lang` attributes to all documents
* updates some of the links (most prominent: replace the outdated
https://www.w3.org/WAI/GL/WCAG20/TECHS-SUBMIT/ to instead point to the
github repo)

Closes #3585

Note that this change is based on existing non-normative information
under [Background on WCAG
2](https://www.w3.org/TR/WCAG22/#background-on-wcag-2) in the existing
TR, which reads in part:
>Where this document refers to WCAG 2 it is intended to mean any and all
versions of WCAG that start with 2.

---------

Co-authored-by: Mike Gower <[email protected]>
Co-authored-by: David Cox <[email protected]>
Co-authored-by: Sebastian <[email protected]>
kfranqueiro pushed a commit that referenced this issue Nov 19, 2024
@mbgower
Update used-in-an-unusual-or-restricted-way.html (#3707)
eabc5e3 
closes #3487 by making the reference WCAG 2 and not WCAG 2.1.
Similar to effort in #3585 
It is unclear to me if the change needs to be made in the hmtl or in one
of these source files, where the definition also occurs, so citing them
as part of the change /wcag20/sources/wcag2-src.xml
/wcag20/sources/wcag2-src.REC.xml

Note that this change is based on existing non-normative information
under [Background on WCAG
2](https://www.w3.org/TR/WCAG22/#background-on-wcag-2) in the existing
TR, which reads in part:
>Where this document refers to WCAG 2 it is intended to mean any and all
versions of WCAG that start with 2.
kfranqueiro pushed a commit that referenced this issue Dec 18, 2024
@mbgower @kfranqueiro
Update used-in-an-unusual-or-restricted-way.html (#3707)
ba45a19 
closes #3487 by making the reference WCAG 2 and not WCAG 2.1.
Similar to effort in #3585
It is unclear to me if the change needs to be made in the hmtl or in one
of these source files, where the definition also occurs, so citing them
as part of the change /wcag20/sources/wcag2-src.xml
/wcag20/sources/wcag2-src.REC.xml

Note that this change is based on existing non-normative information
under [Background on WCAG
2](https://www.w3.org/TR/WCAG22/#background-on-wcag-2) in the existing
TR, which reads in part:
>Where this document refers to WCAG 2 it is intended to mean any and all
versions of WCAG that start with 2.

(cherry picked from commit eabc5e3)
kfranqueiro pushed a commit that referenced this issue Dec 18, 2024
@mbgower @kfranqueiro
Update used-in-an-unusual-or-restricted-way.html (#3707)
7b1ba3d 
closes #3487 by making the reference WCAG 2 and not WCAG 2.1.
Similar to effort in #3585
It is unclear to me if the change needs to be made in the hmtl or in one
of these source files, where the definition also occurs, so citing them
as part of the change /wcag20/sources/wcag2-src.xml
/wcag20/sources/wcag2-src.REC.xml

Note that this change is based on existing non-normative information
under [Background on WCAG
2](https://www.w3.org/TR/WCAG22/#background-on-wcag-2) in the existing
TR, which reads in part:
>Where this document refers to WCAG 2 it is intended to mean any and all
versions of WCAG that start with 2.

(cherry picked from commit eabc5e3)
kfranqueiro pushed a commit that referenced this issue Dec 19, 2024
@mbgower @kfranqueiro
Update used-in-an-unusual-or-restricted-way.html (#3707)
4aff5c9 
closes #3487 by making the reference WCAG 2 and not WCAG 2.1.
Similar to effort in #3585
It is unclear to me if the change needs to be made in the hmtl or in one
of these source files, where the definition also occurs, so citing them
as part of the change /wcag20/sources/wcag2-src.xml
/wcag20/sources/wcag2-src.REC.xml

Note that this change is based on existing non-normative information
under [Background on WCAG
2](https://www.w3.org/TR/WCAG22/#background-on-wcag-2) in the existing
TR, which reads in part:
>Where this document refers to WCAG 2 it is intended to mean any and all
versions of WCAG that start with 2.

(cherry picked from commit eabc5e3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@patrickhlauke patrickhlauke

Labels
Editorial Substantive WCAG 2.2
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update general understanding documents w3c/wcag
3 participants
@patrickhlauke @shawna-slh @mbgower