WCAG 2 proposed changes (review by Dec 1)

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 non-normative WCAG 2 updates, and consists of changes in several categories.

Due to the concentration on discussions at TPAC, we are only listing a few changes in this batch (along with FYIs for a bug fix and an issue where we have already responded in the negative).

How to provide feedback on the following changes

For proposed substantive or editorial changes:

  1.  Give a thumbs up on the Pull Request description to agree. We are looking for at least four +1 votes (activating the 👍 emoji) for substantive or errata changes.

  2.  Or provide feedback in the conversation thread 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 editorial errata changes (changes that do not meaningfully alter informative language in a normative document)

None this cycle.

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

  *   Aria2 as advisory technique for 3.3.2 and 3.3.1 #4666<https://github.com/w3c/wcag/pull/4666>

  *   Target Size techniques update #4685<https://github.com/w3c/wcag/pull/4685>

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

  *   Audio Description: Incorporate association suggestions from #4509 review #4680<https://github.com/w3c/wcag/pull/4680>

Proposed responses to issues (for which we are not going to create a PR)

  *   Use term "natural language" instead of "human language" in glossary?<https://github.com/w3c/wcag/issues/2639#issuecomment-3507102294>

#2639<https://github.com/w3c/wcag/issues/2639#issuecomment-3507102294>

Implemented bug fixes (already incorporated trivial editorial and technical corrections such as typos and broken links)

  *   Trim doubled spaces from technique title/h1 content #4745<https://github.com/w3c/wcag/pull/4745>

How to participate in future task force work

  *   Attend Friday call<https://www.w3.org/groups/tf/wcag2x-backlog/calendar/>.
  *   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> is available.