These are the weekly notes for the Accessibility Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and the meeting’s agenda here.
Updates from the working groups
Only groups that provided updates are shown below.
General
@ryokuhi reported a few statistics for Trac tickets collected at the time of the meeting.
- There were 13 tickets in the Awaiting Review queue, all of them reviewed at least once.
- There were 16 tickets already milestoned for the next major release (6.2), with no timeline for the release set yet.
Gutenberg
@alexstine asked to have a look to the Pull Request to move the Post or Page title to the top toolbar and to the related issue, which he isn’t convinced about.
Meta
Before the meeting, @alexstine asked to watch Meta ticket 6608.
Open floor
@bph asked for accessibility feedback on the usage of the title field of the Code Block (which is added by a plugin) in the WordPress Developer Blog. Full discussion on the topic can be found on Slack, and a summary of the discussion is available on @bph‘s personal blog. The team suggested changes to the plugin itself, to improve its accessibility. When the new implementation of the block is ready, the topic will be discussed again during a meeting. If you want to add something to the conversation, feel free to drop a line in the #core-dev-blog channel on Slack.
@joesimpsonjr, who is part of the Lead Team for WordCamp US 2023 and the Community Summit, invited Make WordPress Accessible Team contributors to share topics for discussion at the Community summit, an event that will provide a valuable opportunity to hold in-person discussions on important topics across contributor teams and community-wide. To suggest possible topics, you can use the form on the Community Summit website.
As already announced, @ryokuhi is stepping down from his role as Accessibility Team Rep. As such, a Call for Team Reps was opened: if you want to candidate yourself or if you have a name for a possible Team Rep, write it in the comments to that post.
Update 9 December 2022: A link to the summary of the discussion about the Code Block from @bph‘s blog was added.