- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 15 Jan 2026 20:27:55 +0000
- 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 - 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 Meeting information https://www.w3.org/groups/tf/wcag2x-backlog/calendar/ Note one tiny change to process that I'd like to trial: for changes that are effectively just under-the-hood / technical (that Ken does for the most part), I wonder if it makes sense to still mark them as being part of WCAG 2.x backlog, but to then move them straight to "Ready for approval" when ready (and then before the next AGWG message, merge them) - i.e. no need to even discuss them in our group, unless the author feels it's something that could do with a second opinion. For this week, there's 4 already in "Ready for approval" of that nature. Suggest that members of the TF skim over these before the meeting, and bring up anything that they think might be controversial/need a bit more discussion first. -- Patrick H. Lauke * https://www.splintered.co.uk/ * https://github.com/patrickhlauke * https://mastodon.social/@patrick_h_lauke
Received on Thursday, 15 January 2026 20:28:03 UTC