-
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
Expand/clarify "single pointer" definition #809
Conversation
0f6d8b4
to
eb22310
Compare
were there any particular problems/objections to this being updated in 2.2? |
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.
No issues with content from me. But structurally, our style for definitions (for better or worse, it's what was decided for WCAG 2) is that the definition should in principle be able to be dropped into the spec in place of the term and still make sense. This applies to the first para of the definition, which should be a phrase, with no starting cap or ending punctuation. Subsequent paras can provide additional information. This is just a moving words around problem but I don't have a strong enough suggestion to propose.
Structurally, the note should be <p class="note">
instead of starting with the term "Note:", that will cause respec to format it consistently.
so would switching the sentence around work, i.e. starting the definition with |
@michael-n-cooper sorry, coming back to this a bit late, but I think I made the changes you mentioned to the actual format (first sentence being "drop-in-able", and use of @alastc any chance this small tweak here can still be considered for 2.1 errata? |
…finition based on @michael-n-cooper 's feedback, changed the first sentence to be "able to be dropped into the spec in place of the term and still make sense", hopefully. added the distinction to / mention of multitouch in contrast to single pointer interaction avoiding repetition, removed the reference to Pointer Events spec from my original PR from the single pointer definiton as that's already covered in the definition for "pointer input", but made sure to make the cross-reference to that from the "single pointer" definition actually a link (which I think gets automagically turned into the correct link to the definiton?)
f15d00c
to
7c7a6e8
Compare
ping @alastc (while i'm going through my PR left hanging open for ages) |
Ping @alastc again |
https://www.w3.org/2021/07/06-ag-minutes.html#item04 There were objections to such a large change as an errata. Kept the normative to editorial and used the other content in the pointer-gestures understanding.
Agreed in meeting, will need to CFC for the editorial errata. |
@alastc any more movement on this? |
Coming up to the three year anniversary of this pull request...are there any objections to it? if not...any chance it might at some point be merged? @alastc |
party time |
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]>
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)
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)
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)
Closes #749