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.

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

30 april meeting #63

Merged
merged 47 commits into from
May 10, 2024
Merged

30 april meeting #63

merged 47 commits into from
May 10, 2024

Conversation

rachaelbradley
Copy link
Contributor

@rachaelbradley rachaelbradley commented Apr 30, 2024

This PR pulls in changes proposed the prior week and discussed at the meeting.

Preview RawGit

Copy link

netlify bot commented Apr 30, 2024

Deploy Preview for wcag3 canceled.

Name Link
🔨 Latest commit 159723d
🔍 Latest deploy log https://app.netlify.com/sites/wcag3/deploys/663e41ce552d9700094c3ad8

rachaelbradley and others added 7 commits April 30, 2024 10:39
Co-authored-by: Matt Garrish <mattgarrish@users.noreply.github.com>
Co-authored-by: Matt Garrish <mattgarrish@users.noreply.github.com>
@rachaelbradley
Copy link
Contributor Author

@detlevhfischer We made many of the changes you suggested and updated the overall editor's note to clarify some of your concerns. There were two items we did not have enough information to make final changes but include proposals below. Please respond here with suggested changes before Monday May 6th.

  1. You asked for something more specific for Pointer cancellation: Pointer cancellation is consistent. The suggested revision in the meeting was "Pointer cancellation techniques are consistent."
  2. You asked about the use case for "Focus retention: A user can focus on a content “area” then resume their view of all content using a limited number of steps". The suggested revision in the meeting was "Focus retention: A user can focus on a content “area,” such as a modal or pop-up, then resume their view of all content using a limited number of steps

@rachaelbradley
Copy link
Contributor Author

rachaelbradley commented Apr 30, 2024

Summary 30 April Meeting

Two decisions that were made at today's meeting:

Per our process, if you have concerns about these decisions please thumbs down this summary before Monday, May 6th and add a comment about your concerns. Use thumbs up to support these decisions.

The sections with new content are the Introduction and Guidelines sections. The editor's note has been changed slightly since the meeting per our discussion.

@detlevhfischer
Copy link

detlevhfischer commented May 2, 2024

@rachaelbradley
Updates to Focus retention and Pointer Cancellation

  • For Focus Retention, the amended text seems a clear improvement.
  • Regarding Pointer Cancellation, the fact that you talk about "Pointer cancellation techniques" (plural) made me wonder whether this does not sit a bit oddly with the ask of consistency.
    However, looking at 2.5.2 Techniques, it is possible that two techniques are supported at the same time, one for case 1, activation of targets on up event, and the other for case 2, cancelling dragging movements, and both are used throughout, i.e., consistently. (The pencilled-in future technique, "Touch events are only triggered when touch is removed from a control" looks to me like a duplicate of G212.)
    So one could flesh this out to cover these two scenarios, but it may be too much detail at the level intended.

@alastc alastc mentioned this pull request May 6, 2024
@wareid
Copy link

wareid commented May 7, 2024

A few pieces of feedback on the introduction and transition into the new outcomes that I hope will aid comprehension once this is in working draft (and the public's hands):

  1. We need to provide a brief overview of the structure of WCAG 3 in the Introduction. This is explained in the Abstract, but I think reiterating it in the Introduction will aid those not familiar with our new terminology in understanding what has been changed. It's also important to point out that we have changed/restructured the Guidelines in this version along with the Outcomes. I would also link to the Guidelines directly, so people also see our callout for feedback.
  2. This part of the introduction: "The final version of WCAG 3 will not include all of these outcomes. Of the Outcomes that are included: The text of the Outcomes will change the text listed in this version," I don't understand this wording and I think it will be confusing for readers not familiar with our work.
  3. In the opening editor's note for Guidelines, we clearly explain what we need from the community, and for research we provide guidance on sending it to us, we should do the same for the feedback.

Otherwise, great work and I'm excited to see a fresh working draft!

@iadawn iadawn merged commit 6690fac into main May 10, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants