Re: WCAG 2 proposed changes (review by 23 February)

Just a small follow-up to the email from last week: I forgot to add a 
direct link to the second "Proposed sustantive changes" pull request. 
For completeness, this should have been:

* Better clarify the "Supported Interface" exception for motion in 
understanding https://github.com/w3c/wcag/pull/4813

Thanks to Bruce Bailey for pointing that out the other day, and 
apologies if that caused any confusion.

P

On 09/02/2026 23:23, Patrick H. Lauke wrote:
> 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 clarification about intermediate steps (on the way to 200%) for 
> resize text https://github.com/w3c/wcag/pull/4839
> * Better clarify the "Supported Interface" exception for motion in 
> understanding
> 
> 
> 
> # Proposed editorial changes (small improvements to language intended to 
> clarify existing guidance)
> 
> * Update links in Understanding SC 4.1.3 https://github.com/w3c/wcag/ 
> pull/4258
> 
> 
> 
> # Proposed responses to issues (for which we are not going to create a PR)
> 
> * What does nested according to the specification mean in SC 4.1.1 
> https://github.com/w3c/wcag/issues/978
> * Applicability of map markings to SC 1.4.11 https://github.com/w3c/ 
> wcag/issues/2025
> 
> 
> 
> # Implemented bug fixes (already incorporated trivial editorial and 
> technical corrections such as typos and broken links)
> 
> * fix: typo on bypass blocks https://github.com/w3c/wcag/pull/4912
> * Remove broken link from C29 https://github.com/w3c/wcag/pull/3700
> * Update broken link to working link in G102 https://github.com/w3c/ 
> wcag/pull/3703
> * Change “Success Criterion” case from title to sentence in technique 
> template partials https://github.com/w3c/wcag/pull/4900
> 
> 
> 
> 
> # 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.
> 
> 
> 
> # 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://flickr.com/photos/redux/
* https://mastodon.social/@patrick_h_lauke

Received on Monday, 16 February 2026 21:28:45 UTC