WCAG 2.2 issues

Hi everyone,

We have a fair few issues coming in, and it would really help to distribute these around the group.

I think it would help to focus on particular issues at a time, you'll see in the surveys for our next meeting that it focuses on Redundant Entry & Focus Appearance.

Other SCs include, in order of number of open issues:


  *   Findable help: https://github.com/w3c/wcag/labels/3.2.6%20Findable%20help

  *   Accessible authentication: https://github.com/w3c/wcag/labels/3.3.7%20Accessible%20Authentication


  *   Fixed reference points: https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+label%3A%222.4.13+Fixed+reference+points%22

  *   Hidden controls: https://github.com/w3c/wcag/labels/3.2.7%20Hidden%20controls

  *   Pointer target spacing: https://github.com/w3c/wcag/labels/2.5.8%20Pointer%20Target%20Spacing
(I think Sukriti has signed up for most of these.)

  *   Dragging: https://github.com/w3c/wcag/labels/2.5.x%20Dragging

Obviously it helps if you are familiar with an SC, so the people who lead each SC may wish to tackle theirs, but anyone can join in.

The general process is to:

  *   Review an issue;
  *   If you are going to tackle it, assign it to yourself (top right);
  *   Propose an update and/or a response;
  *   Add the label 'Survey, read for' when you are done.
An update can be in the form of a pull request, but it could also just be in a comment, e.g. "Let's update the understanding document, 3rd paragraph, to say...". Please do include the exact text so the group can review it.

A response can be proposed as a comment in the github thread, saying "My draft response for group consideration is: ". Or if you are unsure, please to email it to the chairs or the AG group for comment before putting something in the github thread.

Kind regards,

-Alastair

--

nomensa.com / @alastc