REVIEW - WCAG 2 proposed changes (due by May 20)

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.

**Proposed normative change

In addition to the non-normative changes in the sections below, the Task Force has identified a normative change for the Working Group. This is listed here to initiate a normative review process. It will be added to an upcoming call, and if the attending working group members are in general agreement, it will go through a CFC process.

  *   Remove periods from end of definitions #4359<https://github.com/w3c/wcag/pull/4359>

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)

  *   Remove the confusing "not necessarily limited" part of the 1.3.4 Orientation note and expand #4349<https://github.com/w3c/wcag/pull/4349>
  *   Update understanding conformance and technique G73 to remove mention of longdesc #4365<https://github.com/w3c/wcag/pull/4365>

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

  *   Add link to NIST SP 800-63B 2nd public draft to 3.3.8 / 3.3.9 understanding #4351<https://github.com/w3c/wcag/pull/4351>

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

  *   Some editorial updates to Understanding SC 2.5.3 #4335<https://github.com/w3c/wcag/pull/4335>

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)

  *   SC 1.4.3 - Contrast minimum - note on evaluation success criterion using px - misleading px value#4337.<https://github.com/mbgower>
  *   Extra whitespace in 5.3.2 Optional Components of a Conformance Claim #4357<https://github.com/w3c/wcag/pull/4357>

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.