Anh Tran

Accessibility team rep Joe Dolson, speaking on behalf of the team, cited cognitive load and complexity, inconsistent user interface behavior, heavy reliance on keyboard shortcuts, and difficulties with keyboard navigation through blocks, among other concerns about Gutenberg.

This is a big thing! Not only for users who rely on assistive technology, but also for normal users. I’ve been using Gutenberg for months on my personal blog, and I have the similar experience. I think there should be an update on UI/UX for Gutenberg in later releases, to make it easier to use.

At this moment, the big question is: is it good enough for release? I agree with Matt that we still can improve the editor after releasing. The first release can be considered as a MVP. But it has to be good enough for most use cases. Personally, I think it’s not there.

I’m working on making Meta Box plugin to make sure my users have smooth experience when Gutenberg is merged into the core. However, there’s some issues from the Gutenberg that doesn’t make it work, and it might break not only Meta Box but also other custom fields plugin. It’s a bad backward-compatibility and might hurt thousands sites.

I hope the team can focus on backward-compatibility / existing features, to make them work reliably before release. Other fancy things can be updated later.

Name *

Email *

Website:

Topic Title (Maximum Length: 80):

Forum:
— No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor