REVIEW - WCAG 2 proposed changes (due by Feb 6)

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.

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 >4 +1 votes (activating the 👍 emoji) for substantive or errata changes
  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 editorial errata changes (changes that alter informative language in a normative document)
·        Amend definition of motion animation to *not* exclude blurring #4040<https://github.com/w3c/wcag/pull/4040>
·        Harmonise spelling for "breakpoint" #4165<https://github.com/w3c/wcag/pull/4165>
Proposed substantive changes (changes that meaningfully add or alter existing non-normative guidance)
·        Update text-spacing.html #4125<https://github.com/w3c/wcag/pull/4125>
·        Suggested additional note for focus-not-obscured #4104<https://github.com/w3c/wcag/pull/4104>
·        Move H28 from sufficient to advisory in 3.1.4 Abbreviations SC #4195<https://github.com/w3c/wcag/pull/4195>
Proposed editorial changes (small improvements to language intended to clarify existing guidance)
·        Updated 2.5.8 Target Size (Minimum) Understanding Doc to add more clarity to the User agent control bit in Exceptions #4196<https://github.com/w3c/wcag/pull/4196>
Proposed responses to issues (for which we are not going to create a PR)

None this cycle.

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

None this cycle.

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>