-
Notifications
You must be signed in to change notification settings - Fork 320
link directly to new supplemental guidance #2296
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
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Discussed on backlog call, add to CFC. |
Discussed on TF call 11/8, might be OBE. @kfranqueiro will check in again with @shawna-slh |
Co-authored-by: Mike Gower <[email protected]>
/me looks up OBE ... officer (of the Order) of the British Empire / Order of the British Empire ... out-of-body experience ... overcome / overtaken by events After revision this PR now:
Neither are dangerously wrong if not fixed. I happily leave it to others to determine the appropriateness for this change or not. :) fyi brief history: we planned to do something like 'supplemental guidance' but didn't know if we would end up calling it that. the link used to go to a section in WCAG 2 Overview that explained that some kind of supplemental guidance was coming. after it existed and when we updated WCAG 2 Overview and The WCAG 2 Documents, that was changed. (to be honest, we forgot about the link from WCAG) |
related comment that gets hidden in resolved thread:
Should we create a new issue for fixing that sentence structure? Or should I just let it go? (I'm fine doing either.) |
@shawna-slh If you want to fix it, create a new issue, otherwise you can just let it go :) |
One probably minor problem is that the link promises more than the page linked to can hold. There is, for example, currently no low vision guidance. May suggest adapting the link text. |
I don't think this is worth publishing an errata for. Don't forget that this link will forever be in use in all the thousands of copies that exist of WCAG, including the W3C's own translations of WCAG. |
just fyi, we are pursuing updates of WCAG translations when appropriate |
Discussed on TF call 11/22 and all parties satisfied that we have correct link and that this can be included with republication. |
In the context of this PR, we agreed that this is non-normative and so can be addressed through errata; in fact, that it does not require a republication or CFC process. |
Moving to Errata for CFC, since that is our defined column for errata, but note that this does not need to go to CFC. It is non-normative. Intend to hold it in that column until we resolve the errata and publishing cadence with Faciltators. |
<!-- This comment and the below content is programmatically generated. You may add a comma-separated list of anchors you'd like a direct link to below (e.g. #idl-serializers, #idl-sequence): Don't remove this comment or modify anything below this line. If you don't want a preview generated for this pull request, just replace the whole of this comment's content by "no preview" and remove what's below. --> *** <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/2296.html" title="Last updated on Nov 9, 2024, 2:26 PM UTC (1e590d8)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/2296/84d1219...1e590d8.html" title="Last updated on Nov 9, 2024, 2:26 PM UTC (1e590d8)">Diff</a> --------- Co-authored-by: Mike Gower <[email protected]> Co-authored-by: Kenneth G. Franqueiro <[email protected]> (cherry picked from commit 80ba129)
<!-- This comment and the below content is programmatically generated. You may add a comma-separated list of anchors you'd like a direct link to below (e.g. #idl-serializers, #idl-sequence): Don't remove this comment or modify anything below this line. If you don't want a preview generated for this pull request, just replace the whole of this comment's content by "no preview" and remove what's below. --> *** <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/2296.html" title="Last updated on Nov 9, 2024, 2:26 PM UTC (1e590d8)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/2296/84d1219...1e590d8.html" title="Last updated on Nov 9, 2024, 2:26 PM UTC (1e590d8)">Diff</a> --------- Co-authored-by: Mike Gower <[email protected]> Co-authored-by: Kenneth G. Franqueiro <[email protected]> (cherry picked from commit 80ba129)
This PR adds four changes to the list of errata for WCAG 2.2 and 2.1 TR documents. The changes are from: #4256, #4040, #4165, and #2296. Three of the changes are to notes and examples in the specification, which are non-normative according to the [5.1 Interpreting Normative Requirements](https://www.w3.org/TR/WCAG22/#interpreting-normative-requirements). One of the changes is a normative change, restricted to correcting the alphabetical order for the list of defined terms. As such, it falls under [Changes that do not functionally affect interpretation of the document](https://www.w3.org/policies/process/#correction-classes). Previews: [2.1](https://deploy-preview-4370--wcag2.netlify.app/errata/21#since-current), [2.2](https://deploy-preview-4370--wcag2.netlify.app/errata/22#since-current) --------- Co-authored-by: Kenneth G. Franqueiro <[email protected]>
Preview | Diff