- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 3 Jun 2026 10:07:12 +0100
- To: public-wcag2-issues@w3.org
Working through our usual board https://github.com/orgs/w3c/projects/56 * Review "For discussion" items * Review "Drafted" items (see below) - either: * Move back to "In progress", with more work to do; or * Move to "Ready for approval", if there is general agreement the issue is sufficiently resolved; or * Leave in "Drafted", if discussion was not concluded satisfactorily. * Review if there are pressing "To do" items * Time permitting, items of interest to participants, including open discussions. For instance: * Check if people working on "In progress" items need help Note: it would be good/helpful if folks could grab a few minutes before the meeting to familiarise themselves with the items at the top of the "Drafted" and "For discussion" columns, as having at least a passing familiarity with the context (rather than looking at these "cold" for the first time in the meeting) may help steer any discussion. Specific issues/PRs we'll try to get to in the meeting: * Add C40 (two-color focus) as sufficient for 1.4.11 Non-text contrast, make sufficient techniques for 1.4.11 situationally specific#5090 https://github.com/w3c/wcag/pull/5090 * Expand 1.4.5 Images of Text benefits #5065 https://github.com/w3c/wcag/pull/5065 * Total rewrite of example for SCR27 #4558 https://github.com/w3c/wcag/pull/4558 * Clarify whether SC 1.3.1 requires grouped links to be in a list structure #1159 https://github.com/w3c/wcag/issues/1159 * Add a non-normative explanation of "proper name" to 3.1.2 Language of Parts understanding #5135 https://github.com/w3c/wcag/pull/5135 * Add "also" to note about flashing content in 2.2.2 Pause, Stop, Hide understanding #5131 https://github.com/w3c/wcag/pull/5131 * Add "also" to Note 1 for 2.2.2 Pause, Stop, Hide #5130 https://github.com/w3c/wcag/pull/5130 Bonus If you're after a fairly low risk activity, there's oodles of unanswered questions in https://github.com/w3c/wcag/discussions?discussions_q=is%3Aopen+is%3Aunanswered ... many of those are very straightforward questions that can be answered fairly easily. Others may, during the course of the discussion, actually surface some problems in understanding/techniques that we can then tackle more directly with issues/PRs. Of course, there's also tons of "To-do" items on our board...if you skim over them and see something that interests you and where you think you can make a good suggestion/PR...feel free to assign yourself and work on them. Meeting information https://www.w3.org/groups/tf/wcag2x-backlog/calendar/ -- 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 Wednesday, 3 June 2026 09:07:33 UTC