You cannot release a product with significant #a11y issues and call it a quality product. You cannot ignore a11y because it gets in your way and call yourself an advocate. @photomatt can continue to play this wrong all he likes, but that still doesn’t make it jazz.

Following is a transcription of what are apparently official comments from Yoast regarding the slated WordPress 5.0 release on Thursday. I’m providing this transcription for those who are using Twitter clients which do not support alternative text, (essentially the blindness-specific Twitter client), as well as for those on Facebook, Micro.blog and Mastodon. The quote reads:

We vehemently disagree with the decision to release WordPress 5.0 on December 6th, and think it’s irresponsible and disrespectful towards the community. However, we’re now going to try and support the community as well as possible and we hope to show everyone that Gutenberg is indeed a huge step forward.

Yoast is one of the largest plugin developers in the WordPress space, and they’ve made no bones about their support for accessibility. This tweet, for example, carries alternative text, and Yoast has made it a point to ensure that the user interfaces for their Search Engine Optimization plugin are as accessible as possible given the current WordPress interface. Joost’s comment is probably as professional as it’s going to get on this score, and know, I’m not counting the “everything-is-awesome” type comments that will inevitably be shared by Matt from Gutenberg’s cheering section in the score. There’s been a lot of chaos around Gutenberg and accessibility, and it’s heartening to know that so many in the WordPress space, including some rather large plugin and theme shops, are fighting alongside traditional accessibility advocates. All of you have my sincerest thanks.