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

The following email outlines 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)

  1.  Remove technique H59 #2970<>
  2.  Add section on symbolic text characters to 1.4.11 understanding #2067<>
  3.  Add two notes/clarifications to 2.1.1/2.1.3 understanding #1642<>
  4.  Add anti-aliasing note to 1.4.11 #3560<>
  5.  Update accessible-authentication-minimum.html #3309<>

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

  1.  Tweak bypass blocks understanding #1713<>
  2.  Add clarification that change of color still needs sufficient 3:1 ratio, darken focused star #3568<>
  3.  clarifying name, role, value #2207<>

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)
1.     Incorrect links #3639<>
How to participate in future task force work

  *   Attend Friday call<>
  *   Participate asynchronously in github discussions<>
  *   Self-assign issues on the project board<>
  *   Subscribe to Listserv:<>

Completed changes

A table showing all merged changes by date <>

Received on Wednesday, 31 January 2024 06:57:03 UTC