WCAG 2 proposed changes (review by Oct 30)

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)

None this cycle.

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

  *   Add notes to 2.4.3 understanding to try and address static content receiving focus and what does/doesn't constitute a focus order failure #1643<https://github.com/w3c/wcag/pull/1643>

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

  *   Visual presentation: Improve wording of techniques instructions #4681<https://github.com/w3c/wcag/pull/4681>

  *
Tweak inline code and preformatted blocks #4683<https://github.com/w3c/wcag/pull/4683>
  *
Incorporate suggestions from restoration of Target Size (Enhanced) Understanding #4589<https://github.com/w3c/wcag/pull/4589>
  *
Deduplicate entries under "This technique relates to" #4644<https://github.com/w3c/wcag/pull/4644>
  *
Rephrase inline code elements #4623<https://github.com/w3c/wcag/pull/4623>
  *
Replace raster images with SVG in Understanding SC 1.4.11: Non-Text Contrast #4573<https://github.com/w3c/wcag/pull/4573>

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

  *   Clarification: Is a + / – button a sufficient accessible alternative for pinch zoom if users can't control the zoom focus area? (WCAG 2.5.1) #4692<https://github.com/w3c/wcag/issues/4692#issuecomment-3412535990>

  *
Update F3 #1035<https://github.com/w3c/wcag/pull/1035#issuecomment-3099357479>

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

  *   fix: spacing in pronunciation.html #4645<https://github.com/w3c/wcag/pull/4645>

  *
Update understanding conformance partial 3rd party section id #4657<https://github.com/w3c/wcag/pull/4657>
  *
fix pause, stop, hide link #4662<https://github.com/w3c/wcag/pull/4662>

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.