Re: WCAG 2 proposed changes (review by 26 January)

Hi Murata-san,

The email that Patrick sends out every 2 weeks is a summary of recent activity. It is a chance for the whole group to see what updates are proposed or recently added. (It used to be sent my Michael Gower, if you look at the archives.)

Normative changes (more than small errata) have been out of scope for the task force, but we discussed changing that for the new charter in the meeting on the 13th:
https://www.w3.org/2026/01/13-ag-minutes.html#145a


That would allow the task force to work on normative updates for internationalisation.

We will be updating the group with changes to the charter soon.

Also, you may be interested in the informative work going on in the WCAG 2 task force, such as:
"Add new failure technique for non-semantic ruby annotation<https://github.com/w3c/wcag/pull/4829> #4829” (based on the Ruby issue<https://github.com/w3c/wcag/issues/4746> you raised at TPAC)
Oh, looking at the comments, I can see that you’ve already looked at this!

Kind regards,

-Alastair


From: 村田真 <founder@info-a11y.jp>
Date: Saturday, 17 January 2026 at 04:34
To: Patrick H. Lauke <redux@splintered.co.uk>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: WCAG 2 proposed changes (review by 26 January)

You don't often get email from founder@info-a11y.jp. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Patrick,

2026年1月13日(火) 4:43 Patrick H. Lauke <redux@splintered.co.uk<mailto:redux@splintered.co.uk>>:
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.

Thank you for the update.

I understand that this review cycle is limited to non-normative updates to WCAG 2.
Could you clarify where and how normative changes to WCAG 2.2 are expected to be handled,
especially for issues that cannot be resolved at the non-normative level (e.g. internationalization-related issues)?

Regard,
Makoto





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

* remove reference to td elements with scope attributes
https://github.com/w3c/wcag/pull/4785

* G82: Change "the" to "interactive" in title
https://github.com/w3c/wcag/pull/4764

* 3.3.2 - Form control labels using non-text content
https://github.com/w3c/wcag/pull/4626

* 3.1.2 Language of Parts - Computed acc name clarification + ambiguous
example https://github.com/w3c/wcag/pull/4423

* Expand title of H54 https://github.com/w3c/wcag/pull/4812




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

* Re-phrased Example 1 description for F33 technique
https://github.com/w3c/wcag/pull/4758

* Updated "A document collection" example since obsolete - SC 2.4.2
https://github.com/w3c/wcag/pull/4631
* Add "text" to the ARIA8 requirement description
https://github.com/w3c/wcag/pull/4811




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

* SC 2.4.4 Link Purpose (In Context) and multiple links with identical
link text https://github.com/w3c/wcag/issues/4762#issuecomment-3571108286




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

* Chore: code cleanup https://github.com/w3c/wcag/pull/4847




# 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 is available.
https://github.com/orgs/w3c/projects/56/views/7



--
Patrick H. Lauke

* https://www.splintered.co.uk/

* https://github.com/patrickhlauke

* https://mastodon.social/@patrick_h_lauke