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.
Is there a better date and time for the Accessibility Team Meeting?
@joedolson mentioned something he heard a lot at contributor day: “I’d like to contribute, but I can’t make the meetings”. May be addressed with a meeting change but suggested thinking about a better way to handle asynchronous communication. Also mentioned getting the agenda up early enough to have teams confirm their contribution, attendance to meetings, and team updates happening faster.
Karen J Radley mentioned possibly picking a second day of the week for meetings and alternating (possibly Fridays).
How can the Accessibility Team help get more contributors involved?
Joe Dolson mentioned that would be very helpful if each working group point person could keep a list of potential areas people can get involved in,things they don’t have time or knowledge to themselves, but that are available tasks would ge useful.
Great opportunity for some accessibility testing.
Item added so we (as a team) make sure somebody is aware of it and can follow up.
Status update from WCUS 2022 Event/Contributor Day.
Brief look back at the events from WordCamp US and Contributor Day.
-
@joesimpsonjr mention the gratification of seeing so many Accessibility talks at a WordCamp and at WCUS. Kudos to @Alexstine , Joe Dolson and other other speakers for sharing…
-
Three tables of volunteers at Contributor Day, which some have said was “the most attended they’d ever seen at a WordCamp Contributor Day.”
@joedolson reported that great progress was made on building out a site to test block output, but it’s definitely not finished! I’m hoping that people will continue to work on it:
- The site is here, and it’s still open: https://blocks.joedolson.com/
- You can read up on the goals here: https://blocks.joedolson.com/goals/
- And if anybody wants to help out, you can register an account here: https://blocks.joedolson.com/wp-login.php?action=register, then ping me on Slack to activate your account.
The project has already exposed some oddities in various blocks and has been productive.
@joedolson mentioned that some of the feedback I’ve seen about the physical space is concerning, and hope that National Harbor has better physical accessibility. @joesimpsonjr mentioned that he’ll be on the Lead team for 2023 and will advocate for eliminating issues mentioned regarding San Diego’s venue.
Open Floor and Quick Team Updates
Only groups that provided updates are shown below.
Documentation
@joedolson mentioned there was a change to the documentation on the media block to remove some ableist language. And he made changes to the Get Involved doc to simplify language and add myself as the media group contact.
General
We’re moving towards 6.1 Beta 1, and a lot of outstanding accessibility tickets are either recently committed or just about ready to go. Should finish those off soon per Joe Dolson.
Meta
A regression was introduced in the accessibility of the adminbar as customized for the WordPress.org network, flagged by @alexstine and reported in Github by me. @ryelle is handling it. Call for accessibility feedback from openverse previously mentioned.
Themes
Twenty TwentyTwo now has the accessibility-ready tag per prior discussion. Major focus now is on building out testing reliability for blocks so that theme accessibility is reliably maintained.
** Thanks to everyone who attended, including first-timers interested in contributing to the accessibility of WordPress. We’ll see you for the next weekly bug scrub.