Re: WCAG 2.x TF changes and proposed changes

Hi everyone,

Following up on the conversation from Tuesday, the question I had was:

Are there any adjustments to the subject line, or headings / content that mean you’ll pay attention to it?

Also, we haven’t had many (or can’t tell how many) people who have reviewed the updates below.
If you have selected a link and reviewed it, if you have no comments / problems with it then please add a thumbs up to the main description.

Kind regards,

-Alastair


From: Michael Gower
The following email outlines the updates proposed and implemented by the WCAG 2.x Task Force. It provides a two-week window for Working Group members to review WCAG 2.x updates, and consists of changes in four categories, as well as information on how to provide feedback.
Proposed normative change (change that updates the Recommendation)
None this cycle.
Proposed substantive non-normative changes (changes that meaningfully add or alter existing guidance)

  *   1.4.4 Understanding: Remove paragraph about IE 6, tweak subsequent paragraph<https://github.com/w3c/wcag/pull/3559>
  *   Update Focus Obscured (Minimum) to add examples<https://github.com/w3c/wcag/pull/3341>
  *   Rewrite SCR37 as an HTML technique<https://github.com/w3c/wcag/pull/3024>
  *   Re-title and update H63 (Using the scope attribute to associate header cells and data cells in data tables)<https://github.com/w3c/wcag/pull/2515>
  *   Add explicit mention of SPAs and dynamic changes of title to 2.4.2 understanding<https://github.com/w3c/wcag/pull/2107>

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

  *   Fix image presentation in pdf1<https://github.com/w3c/wcag/pull/3505>
  *   The word "hidden" in the normative text of Focus Not Obscured may be confused with technology-specific uses<https://github.com/w3c/wcag/pull/3533>
  *   Remove 'active' altogether from 1.4.11 Understanding<https://github.com/w3c/wcag/pull/1547>
  *   Fix incorrect links to Focus Appearance<https://github.com/w3c/wcag/pull/3557>
  *   Rename 3.3.8 Accessible Authentication (add "(Minimum)")<https://github.com/w3c/wcag/pull/3145>
  *   Understanding 1.4.2: fix link to 1.4.7<https://github.com/w3c/wcag/pull/2316>

Proposed responses to issues (issue 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)

  *   Update input-purposes for syntax highlighting<https://github.com/w3c/wcag/pull/3380> * Normative definition, but only changes presentation
  *   Update relative-luminance.html fix broken links<https://github.com/w3c/wcag/pull/3507> * Normative, but just correcting link
  *   Updating "minimum bounding box" term, so anchor in 2.5.8 Target Size (Minimum) understanding works<https://github.com/w3c/wcag/pull/3492> * Normative, but just anchor fix
  *   Updating "mechanism" term, so anchor in 3.2.6 Consistent Help understanding works<https://github.com/w3c/wcag/pull/3509> * Normative, but just anchor fix
  *   WCAG 2.2 - 2.5.5 Target Size (Enhanced) - broken link in the Understanding of SC 2.5.8: Target Size (Minimum) <https://github.com/w3c/wcag/pull/3494>
  *   Update visual-presentation.html - replace line-length link<https://github.com/w3c/wcag/pull/3442>
  *   Technique G78: Broken link<https://github.com/w3c/wcag/pull/3484>
  *   Fix minor typo error in SC 2.5.8: Target Size (Minimum)<https://github.com/w3c/wcag/pull/3498>
  *   Update name-role-value.html - replace link to obsolete content<https://github.com/w3c/wcag/pull/3525>
  *   Redesign has duplicate "applicability" id attributes on Techniques pages<https://github.com/w3c/wcag/pull/3547>
  *   Fixing "1.4.11 Non-text Contrast" link in SC 2.4.13 Focus Appearance Understanding document <https://github.com/w3c/wcag/pull/3528>

How to provide AGWG feedback

For proposed draft responses to issues, give a thumbs up or comment. For proposed substantive or editorial changes:

  1.  Give a thumbs up on the pull request description to agree
  2.  Or provide feedback in the Conversation to request changes

Based on feedback, those changes will be merged or brought back for another review.

Open a new issue if you spot a problem with an implemented bug fix.

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>