-
Notifications
You must be signed in to change notification settings - Fork 272
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
Sync WCAG-2.1 branch contents with its change log and errata #4179
base: WCAG-2.1
Are you sure you want to change the base?
Conversation
9e192a8
to
81a1f60
Compare
81a1f60
to
294b24d
Compare
Thanks for including updates to the Change Log section, @kfranqueiro |
This reverts commit b24abad. This was not properly replicated - it updated the wrong file
Sibling PR to #3518 <!-- 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/3756.html" title="Last updated on Mar 23, 2024, 4:00 PM UTC (cff6720)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3756/bf44269...cff6720.html" title="Last updated on Mar 23, 2024, 4:00 PM UTC (cff6720)">Diff</a> (cherry picked from commit 67f8420)
…sting tablets AREN'T mobile devices (#3776) This removes the weird ambiguity of "why list tablets separately from mobile devices" and closes #3750 Co-authored-by: Mike Gower <[email protected]> (cherry picked from commit 378d4bf)
Style changes to normative documents made to ensure consistency as part of the republishing of WCAG 2.2 - Ensures all normative occurrences of "web page" are two words and lower case. - Ensures all normative occurrences of "website" are a single word, not capitalized. - Ensures all normative occurrences of "success criterion/criteria" that do not specify SCs by name, are lower case - Ensures all normative occurrences of "web content" and other uses of "web" are lower case <!-- 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/4080.html" title="Last updated on Oct 4, 2024, 3:14 PM UTC (571cf14)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/4080/bf4b123...571cf14.html" title="Last updated on Oct 4, 2024, 3:14 PM UTC (571cf14)">Diff</a> --------- Co-authored-by: Alastair Campbell <[email protected]> (cherry picked from commit a2c3cb3)
…ization (#3038) Co-authored-by: Francis Storr <[email protected]> Co-authored-by: Kenneth G. Franqueiro <[email protected]> Co-authored-by: Mike Gower <[email protected]> (cherry picked from commit 1b2d567)
- Fix year reference preceding latest change log list - Capitalize change log list items
The definition for "single pointer" has had issues for a long time, as it mixes the idea of what a pointer *is* with the action(s) *performed* using a pointer. I originally tried to fix this, but there was no appetite for it once 2.1 was released. However, with 2.2 and the new 2.5.7 Dragging Movement SC, the broken definition is causing actual misunderstandings/illogical non-sequiturs. See #749 (comment) and the recent #3535 where this is once again causing a non-sequitur Closes #3535 (this is effectively a follow-up to #809 which had disambiguated things, but the definition had since been changed further/again to reintroduce the ambiguous wording we have at this point which confuses input with action) This would be applied to WCAG 2.1 and 2.2, unless there is a decision to only apply it to 2.2. EDIT: Also closes #394 <!-- 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/3536.html" title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3536/afbf9ee...6c36df1.html" title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Diff</a> --------- Co-authored-by: Alastair Campbell <[email protected]> (cherry picked from commit a9dbe11)
…ointer interactions (#4070) Follow-up to #3536 (comment) to potentially address concerns by @WilcoFiers @dbjorge Tries to more clearly differentiate "input" as in the *modality* from the gestures/interactions that are the *result* of using a particular input *modality* <!-- 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/4070.html" title="Last updated on Sep 20, 2024, 8:10 PM UTC (a79bb49)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/4070/4213bf6...a79bb49.html" title="Last updated on Sep 20, 2024, 8:10 PM UTC (a79bb49)">Diff</a> --------- Co-authored-by: Alastair Campbell <[email protected]> Co-authored-by: Mike Gower <[email protected]> (cherry picked from commit b9cf8f8)
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)
#3362) closes #3361 updates the term example to mention "list item" instead of "list" to be more accurate to what the intent of that likely was trying to convey. Additionally, links to the HTML term of 'paragraph', which I would submit could resolve issues such as #2109 <!-- 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/3362.html" title="Last updated on Aug 25, 2023, 7:14 PM UTC (44450fb)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3362/6b2b211...44450fb.html" title="Last updated on Aug 25, 2023, 7:14 PM UTC (44450fb)">Diff</a> (cherry picked from commit 3d88e14)
294b24d
to
eda56be
Compare
✅ Deploy Preview for wcag21 ready!
To edit notification comments on pull requests, go to your Netlify site 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.
Nice! I had to educate myself about data-*
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.
This data attribute is respec-specific: https://respec.org/docs/#data-lt
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.
Thanks Ken!
Reviewed on backlog call 2/21. |
Reminder: when the time comes to merge, we might want to consider a rebase merge for this rather than a squash merge, to retain the cherry-picking breadcrumb trail.
Background
The 2024-12-12 republication of WCAG 2.1 added a new set of entries to the change log; however, most of these changes were never backported to the
WCAG-2.1
branch, and therefore did not make it into the republication. In addition, there were several other errata intended to be common between 2.1 and 2.2 which were neither backported nor referenced in the new change log.Changes
This branch includes a few sets of changes as a starting point for review and discussion; here's a breakdown. It may be easier to review these on a commit-by-commit basis rather than attempting to view the full diff at once.
main
(applied against pointer-input rather than single-pointer)guidelines
. I can backport this for consistency if we would like, in which case Update references to HTML autofill/autocomplete #2486 should likely come with it?w=1
to the commit's URL or choose "Hide whitespace" from the cog menu in the sidebar)All backports were performed with
git cherry-pick -x
to include information on the originating commit.Preview
Diff (between the December republication of 2.1 and this branch as of 2025-01-30)