-
Notifications
You must be signed in to change notification settings - Fork 266
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
WCAG 2.2 errata for "used in an unusual or restricted way" definition #3487
Comments
@rscano can you please clarify what you wish addressed? The current definition for up-event in both wcag 2.1 and 2.2 reads:
I don't understand what your "gig" comment refers to. |
If you follow the link, you see that there is an example... and inside example there is WCAG 2.1 instead of WCAG 2.2 (or, better, use WCAG 2 directly). |
Oh, you are talking about the definition for "used in an unusual or restricted way", not for up-event. |
closes #3487 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
Upps.. sorry yes wrong ref sorry :) |
Removing from project board since we are now tracking the PR there. |
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)
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)
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)
Example refer to WCAG 2.1 instead of WCAG 2.2.
The term "gig" means something different if it occurs in a discussion of music concerts
than it does in article about computer hard drive space, but the appropriate definition
can be determined from context. By contrast, the word "text" is used in a very specific
way in WCAG 2.1, so a definition is supplied in the glossary.
The text was updated successfully, but these errors were encountered: