micro photography of leaves

Adobe set to acquire Figma

If you’re a designer or UI specialist in the WordPress world, chances are you already know about the Adobe/Figma deal. A $20 Billion dollar deal in cash and stock – 40 times Figma revenue – shocked us and launched more memes, probably using Photoshop, than we’ve in the tech space since…well about 4 months ago.

4 Years ago, Figma donated an organizational membership to WordPress.org. Will you continue to use Figma? Tweet at us.

In Mullenweg’s recent WCUS address, he snuck in the mention of Automattic’s new cloud service – wp.cloud.

It looks to be infrastructure for cloud providers wanting to serve up some WordPress hosting, leveraging .com’s sprawling CDN & other technology. Products like Jetpack already use .com’s CDN as part of their services, as I’m sure other products like VideoPress do. 

I reached out to Jesse Friedman, who leads the wp.cloud initiative, for an interview. Here’s a sneak peek of that, which airs next week – subscribe so you don’t miss it!

Hosting news continues with WP Engine jumping into the WordPress flavor hosting with a new WooCommerce offering. While Siteground surprises us with their Easy Digital Downloads speciality hosting.

Next up (listen to the podcast for more): Michelle Frechette with the Community Minute & Amber Hinds with the Accessibility Minute!

Community Minute Transcript
Hi! It's Michelle Frechette with your WordPress Community Minute!

It's been almost two weeks since WordCamp US, and I continue to reflect on my (and others') experiences there.

Ultimately, it was an amazing time. I got to see people I hadn't seen in person in years, and I got to see people in person I'd only ever seen on a screen before.

I loved it! 

But if you've seen my tweets and my posts recently, you also know that it was a bit of an accessibility nightmare for me, as someone who uses a mobility device. The response to the noise I've made has been overwhelmingly positive. But I don't want the attention we give to issues that some of us in the community encounter to fade away.

So here's your reminder.

The WordPress community is a community for ALL WordPress users. Not just the ones that are most convenient, have the biggest platforms or followings, are the nicest or most fun, or are in any other way influential.

Remember to be inclusive of everyone. Underrepresented WordPress users have just as much to offer as anyone else, and you might find their perspectives anywhere on the scale from refreshing to downright eye opening.

So next time you have an opportunity to interact with - or more importantly, to include - someone from an underrepresented group, lean in, make friends, and learn from one another.

You never know how much better our community can be when we include everyone. 
Accessibility Minute

Hi, this is Amber Hinds from Equalize Digital and this is your WordPress Accessibility minute.

In celebration of Deaf Awareness month and we’re talking about how to make your website accessible to people who are d/Deaf and hard of hearing. In a previous segment I covered the importance of having accurate captions on your videos. The second way you can ensure accessibility for the d/Deaf community to include transcripts.

Transcripts are written text of spoken audio and important sounds. You most frequently see transcripts published with podcast episodes. If you go to the WP Minute web page for this episode you can see an example of a transcript for what you’re hearing right now.  

Transcripts allow people who can’t listen to audio – whether they can’t hear, don’t have speakers attached to their desktop computer (that’s more common than you might think!), or are sitting in a public space and forgot their headphones. No matter what, transcripts allow people to still have access to the content. 

Most of us know that podcasts and other audio need transcripts. But here’s something you might not realize: videos – even captioned videos – need transcripts too.

People who are Deaf-Blind can’t read captions on videos because they can’t see them. If you have videos on your website and want to allow the video content to be easily translatable into a refreshable Braille display so that Deaf-Blind people can access your videos too, you need a transcript.

Transcripts should be positioned immediately after the video or audio file under a heading of “transcript” so that it is easy for people to find them. You can put them into an accordion if you don’t want them visible on the page – as long as your accordion can be opened and closed with a keyboard only (no mouse required). It’s also acceptable to place a link to a transcript on another page so long as that link is clearly labled. Something like: “Read transcript for episode 123.”

Generally, though, I recommend that transcripts live on the same page as your audio and video content .

Here’s why:

Transcripts make the user experience better for everyone. They allow listeners or watchers (and you!) to more easily refer back to a snippet from the middle of an episode, because having all the text on the page makes your content searchable. 

Along these same lines, providing full transcripts on the page with your podcast episodes or videos will increase the keywords on the page and help your content rank better in search engines. With how competitive the SEO game is, adding a transcript is an easy way to get ahead.

This Deaf Awareness Month think about the content on your website or social media channels. Are you providing captions and transcripts? If not, now’s the time to start!

Thanks for listening and feel free to reach out if you have any questions about this WordPress Accessibility Minute or how you can make your website more accessible.

Links you shouldn’t miss

There’s a handful of other links you shouldn’t miss this week. These links should help you stay informed around the moving and shaking of WordPress:

Matt Mullenweg WCUS Address

This is a direct recording of his livestream session. If you missed it or want to hear the audience Q&A round, click to tune in.

Why WordPress and Wix will Always Be Worlds Apart

The WP Minute’s Eric Karkovack, breaks down a detailed comparison on how much WordPress & Wix differ. 

Help Test WordPress 6.1

The WordPress 6.1 Beta is out! Remember, don’t complain…explain…your issues by testing the latest version before it’s released. 

From the grab bag

Some of these links might interest you – dive in!

Thanks to all of the members who shared these links today: 

  • Eric Karkovack
  • Daniel Shutzsmith
  • Raquel Landefeld
  • Cameron Jones
  • Birgit Pauli-Hack
  • Michelle Frechette
  • Angela Bowman

Consider Supporting The WP Minute

If you want to support me, my team, and all of those that contribute – head on over to buymeacoffee.com/mattreport.

Buy us a digital coffee for as little as $5 OR better yet! Join our community of WordPress newsies, get access to our Slack server, private podcast, behind the scenes on how the news is made, and get your voice heard on the podcast.

✨ Thanks to MasterWP and Underrepresented in Tech for supporting The WP Minute! Support them because they support us. ✨

That’s it for today’s episode, if you enjoyed please share it on your social media, leave us a review on Apple Podcasts or Podchaser. Don’t forget to share share share this episode with others and jump on the mailing list 👇

Thanks for subscribing.

✨ Thanks to MasterWP and Underrepresented in Tech for supporting The WP Minute! Support them because they support us. ✨

Consider Supporting The WP Minute

The WP Minute is an experiment in community journalism for WordPress. If you want to support me, my team, and all of those that contribute – head on over to buymeacoffee.com/mattreport.

Buy us a digital coffee for as little as $5 OR better yet! Join our community of WordPress newsies, get access to our Slack server, private podcast, behind the scenes on how the news is made, and get your voice heard on the podcast.

Join The Newsletter

Get your favorite 5 minutes of WordPress news for busy professionals every week — 100% Free! Join the WP Minute Newsletter below 👇

This field is hidden when viewing the form
This field is for validation purposes and should be left unchanged.

Similar Posts