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 find the meeting’s agenda here.
Team involvement at WordCamp US 2022 Contributor Day
WordCamp US is happening in person in San Diego, California, with Contributor Day on Sunday, September 11th. The organizing team reached out to all the teams for Table Leads for the event and
shared a post containing specific information.
@joedolson and @joesimpsonjr will be both attending. @alexstine will maybe spend a short time there, but not the entire day.
A short discussion followed about possible activities and issues that might arise.
Activities during Contributor Day revolve mainly around sharing accessibility information with contributors, and helping them understand what is needed to get started. @joedolson suggested focusing on mechanisms and learning, as this is more effective than fixing problems or resolving issues during the event.
Contributor Days are difficult to handle, because it’s hard to predict who will show up: both new and experienced contributors might attend, and they have completely different needs. Having more than one person to run things allow to have different processes for people with various levels of knowledge and skills.
If you’re interested in taking a role during WordCamp US Contributor Day, need more details, or want to propose a possible activity, reach out to @joesimpsonjr on Slack. A rough agenda will be discussed through direct messages with people involved or during next meeting.
Updates from the working groups
Only groups that provided updates are shown below.
General
@ryokuhi reported that since last meeting the Team has been focusing on the 21 tickets milestoned for 6.1. The last bug scrub was very productive, with at least a couple of tickets almost ready for commit.
Gutenberg
During the last bug scrub, the Team reviewed again the ticket about adding the accessibility-ready label to the Twenty Twenty-Two theme. Until there’s a mechanism to get a complete list of all blocks and variations for testing, it will be really difficult to close it.
If such a list would be available, part of WordCamp US Contributor Day could maybe be dedicated to testing block output (also) using assistive technologies.
@alexstine has been working through a significant change to keyboard navigation in Gutenberg Pull Request 41645: it still has a few bugs, but would benefit from some testing.
Media
@joedolson has been short on time to work on media, and hopes to make significant progress next week. There wasn’t a lot of feedback on open issues, anyway.
Open floor
@ryokuhi reported that the Call for Team Reps had been written and reviewed, and it was published after the meeting.
@joesimpsonjr and @joedolson shared the Call for Speakers for WordPress Accessibility Day, inviting contributors to apply and share.