REVIEW - WCAG 2 proposed changes (due by Jan 29)

The following email outlines the updates proposed and implemented by the WCAG 2 Task Force. It provides a two-week window for Working Group members to review WCAG 2 updates, and consists of changes in three categories.

How to provide feedback

For proposed substantive or editorial changes:

  1.  Give a thumbs up on the pull request description to agree. (We are looking for >4)
  2.  Or provide feedback in the Conversation to request changes

Based on feedback, those changes will be merged or brought back for another review.


For proposed draft responses to issues, give a thumbs up or comment.

If you spot a problem with an implemented bug fix, open a new issue.

Proposed substantive changes (changes that meaningfully add or alter existing non-normative guidance)

  *   SC 3.3.7 Accessible authentication and CAPTCHA challenge#3198<https://github.com/w3c/wcag/issues/3198>
  *   Tweaks/additions to Understanding Pointer Gestures #910<https://github.com/w3c/wcag/pull/910>
  *   Add two notes/clarifications to 2.1.1/2.1.3 understanding #1642<https://github.com/w3c/wcag/pull/1642>
  *   Fixed Benefits and Examples in the 1.4.10 Reflow Understanding Document for consistency with other SC #3608<https://github.com/w3c/wcag/pull/3608>

Proposed editorial changes (small improvements to language intended to clarify existing guidance)

  *   Understanding document 1.4.10: examples instead of benefits#3428<https://github.com/w3c/wcag/issues/3428>
  *   Tweak section headings understanding wording #2036<https://github.com/w3c/wcag/pull/2036>
  *   Tweak 1.4.10 Reflow understanding intent #1816<https://github.com/w3c/wcag/pull/1816>
  *   ARIA9 change "label" to "name" when it refers to accessible name #1823<https://github.com/w3c/wcag/pull/1823>

Proposed responses to issues (for which we are not going to create a PR)
·         Removal of SC 3.2.7: Visible Controls from WCAG 2.2.#3587<https://github.com/w3c/wcag/issues/3587>
Implemented bug fixes (trivial editorial corrections such as typos and broken links)

  *   Broken link/need for updated reference on Understanding: Non-text contrast#3561<https://github.com/w3c/wcag/issues/3561>

How to participate in future task force work

  *   Attend Friday call<https://www.w3.org/events/meetings/385f6830-c5cf-4d9d-b479-75192aaeec03/20231201T110000/>
  *   Participate asynchronously in github discussions<https://github.com/w3c/wcag/discussions>
  *   Self-assign issues on the project board<https://github.com/orgs/w3c/projects/56/views/1>
  *   Subscribe to Listserv:  public-wcag2-issues@w3.org<mailto:public-wcag2-issues@w3.org>

Completed changes

A table showing all merged changes by date <https://github.com/orgs/w3c/projects/56/views/7>