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

“Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary #1758

Closed
yatil opened this issue Apr 21, 2021 · 4 comments · Fixed by #1777
Closed

“Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary #1758

yatil opened this issue Apr 21, 2021 · 4 comments · Fixed by #1777
Assignees
@DavidMacDonald
Labels
Errata Erratum to a Recommendation Survey - Added WCAG 2.1 WCAG 2.2
Projects
WCAG 2.2

Comments

@yatil
Copy link
Contributor

yatil commented Apr 21, 2021 •
edited

In the second note in the “accessibility supported” glossary definition in WCAG 2.1, the following text is used (links omitted):

Web technologies can be used in ways that are not accessibility supported as long as they are not relied upon and the page as a whole meets the conformance requirements, including Conformance Criterion 4 and Conformance Criterion 5, are met.

“Conformance Criterion 4” and “Conformance Criterion 5” are linked to the sections “5.2.4” and “5.2.5”. The intro text of section 5.2 says (emphasis mine):

In order for a Web page to conform to WCAG 2.1, all of the following conformance requirements must be satisfied:

I think the wording in the note in the “accessibility supported” glossary definition must be “conformance requirements” instead of “conformance criteria”, as “conformance criteria” is not used anywhere else in the document.
@bruce-usab
Copy link
Contributor

bruce-usab commented Apr 21, 2021 •
edited

That is a good catch! Is this another erratum? I had been wondered why the anchors/id are #cc1 and not #cr1. I walked the drafts back, and the first time the conformance gets it's own heading, it was requirements and not criteria: https://www.w3.org/TR/2007/WD-WCAG20-20070517

@yatil yatil changed the title “Conformance Criterion” instead of “Conformance Requirement” in the WCAG 2.1 Glossary “Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary Apr 22, 2021
@alastc alastc added the WCAG 2.0 label May 3, 2021
@alastc alastc mentioned this issue May 3, 2021
Merged
@alastc
Copy link
Contributor

alastc commented May 3, 2021

I guess the heading was updated but the links weren't. Created #1777 to address.

@alastc alastc added the ErratumRaised Potential erratum for a Recommendation label May 3, 2021
@yatil
Copy link
Contributor Author

yatil commented May 4, 2021

Thanks @alastc! As the links are using “Requirement” in WCAG 2.0, I think this should be tagged with “WCAG 2.1” instead.

Also, when can we expect to see this in the errata document? I ask for a hypothetical translation to a hypothetical language that I speak and that hypothetically would love to add this change to the hypothetical Candidate Authorized Translation, hypothetically speaking.

@alastc alastc added this to To do in WCAG 2.2 via automation Oct 22, 2021
@DavidMacDonald DavidMacDonald self-assigned this Nov 19, 2021
@DavidMacDonald
Copy link
Contributor

DavidMacDonald commented Nov 19, 2021 •
edited

Proposed Response

Yes, this is a valid point and we will change the text of the note in the glossary of accessibility supported

to Conformance Requirement 4 and 5

Web technologies can be used in ways that are not accessibility supported as long as they are not relied upon and the page as a whole meets the conformance requirements, including Conformance Requirement 4 and Conformance Requirement 5, are met.

This is editorial with no change in the meaning of the definition.
Criteria and Requirement could be used interchangeably with no change to the meaning. Its a low impact change that only the most ardent followers of WCAG would notice.

NOTE: I could live with it changing in 2.1 OR 2.2. Whichever takes the less time and energy of the group.
There appears to already be a branch with the change created by Alastair

https://github.com/w3c/wcag/blob/Issue1758-conformance-requirements/guidelines/terms/20/accessibility-supported.html

There is a pull request
#1777

@alastc alastc moved this from To do to To Survey in WCAG 2.2 Dec 3, 2021
WCAG 2.2 automation moved this from To Survey to Done Jan 4, 2022
@alastc alastc added Errata Erratum to a Recommendation and removed ErratumRaised Potential erratum for a Recommendation labels Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DavidMacDonald DavidMacDonald

Labels
Errata Erratum to a Recommendation Survey - Added WCAG 2.1 WCAG 2.2
Projects
WCAG 2.2
  
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Conformance requirements, not criteria w3c/wcag
4 participants
@yatil @alastc @DavidMacDonald @bruce-usab