WCAG 2 proposed changes (review by Nov 17)

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 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)

  *   Add change log notes for removal of 4.1.1 #4668<https://github.com/w3c/wcag/pull/4668>

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

  *   Add section on native browser form validation to 3.3.1 understanding #4431<https://github.com/w3c/wcag/pull/4431>

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

  *   Lowercase “Kanji” #4696<https://github.com/w3c/wcag/pull/4696>

  *
Update re-authenticating.html #4714<https://github.com/w3c/wcag/pull/4714>
  *
Update error-identification.html #4694<https://github.com/w3c/wcag/pull/4694>
  *
Addresses the 1.2.8 exception in the 1.2 Time-based Media guideline #4533<https://github.com/w3c/wcag/pull/4533>

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

  *   Techniques may fail both 1.4.1 Use of Color and 1.3.1 Info and Relationships to convey HTML element names and attributes #4193<https://github.com/w3c/wcag/issues/4193#issuecomment-3476335363>

Implemented bug fixes (already incorporated trivial editorial and technical 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/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.