- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 14 Apr 2026 01:17:33 +0100
- To: WCAG2 Backlog <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 figure caption numbering to techniques #5062 https://github.com/w3c/wcag/pull/5062 * Add banner to top of techniques pages, tweak boxout content about techniques #5002 https://github.com/w3c/wcag/pull/5002 * Expand 2.1.2 understanding to make it more ... understandable #4726 https://github.com/w3c/wcag/pull/4726 * Add extra note to pause-stop-hide understanding about multiple instances #4817 https://github.com/w3c/wcag/pull/4817 * Update normative wording of 4.1.3 and definition of "status message" #4952 https://github.com/w3c/wcag/pull/4952 (again) * Update F3 "using CSS to include images that convey [...] information" #4814 https://github.com/w3c/wcag/pull/4814 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 Tuesday, 14 April 2026 00:17:46 UTC