-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility: WCAG violation by different order of Blocks & Patterns in block inserter in Post- and Site-Editor #47113
Comments
I don't think it is that simple. Patterns are highlighted in the site editor because there you are working mostly on design, as opposed to adding many single blocks. It might still very well be the case that consistency is more important. |
Regarding the WCAG violation question, I'm not sure this actually is a violation; it's debatable whether the site editor and the post editor should really be considered as the same interface. The two interfaces perform different functions, edit different fields, and have a lot of very different features, though the interfaces are similar. However, I do think that consistency and muscle memory play a significant role in making the interface easier to use, and having these tools in a different order in the two editors does not seem beneficial to me. I'm not convinced that the argument "you are working mostly on design in the block editor" is sufficient to merit an otherwise arbitrary change in feature order. |
About same or not the same editor: at least the WordPress promotion advertises it as "same editor for posts and templates" But of course more important is usability. And in my experience I work regularly with the post editor and have automated the tasks using block-inserter with Blocks at first and Patterns in the second tab. And about priority of patterns or blocks: |
@WordPress/gutenberg-design I wanted to highlight this feedback for your consideration, not only for the positioning of the blocks and patterns tab panels, but also for 45722. |
I think that changing the order because we're making assumptions about what users are doing or prioritizing is overstepping; we should offer an interface that is predictable, and that means keeping common items in the same order and location as much as we can. In my opinion, the consistent order should be Blocks > Patterns > Media in both environments. |
I agree. Consistency is key. |
I was going to start on this but found that it has already been solved. The order is the same in both editors. |
NO, it is NOT resolved! When you start with website editor, you are in the regular page editing mode, where the order is Blocks > Patterns But when you change to template editing mode, the order is CHANGED to Patterns > Blocks (even in 6.4 RC 2) |
And that the order changes in the same editor, dependent on the edited content, makes the confusion - obviously - even worse! |
Confirming. If you go to Editor > Pages and select a page, then open the canvas to edit, the order is Blocks / Patterns / Media. If you go to Editor > Templates and select a template, then open the canvas to edit, the order is Patterns / Blocks / Media. Reopening. |
@burnuser Please, do remember to try and be polite when communicating with other contributors here. We're all trying, and being shouted at is not constructive or helpful. |
Just going to add a quick 👍 here. UX should be simplified. Thanks. |
Description
As reported in core https://core.trac.wordpress.org/ticket/57431 and advised to report it here.
(And please don't play "not right located here" tennis!)
Step-by-step reproduction instructions
In the block inserter of the post-editor are tabs ordered: Blocks - Patterns
In the block inserter of the site-editor are tabs ordered: Patterns - Blocks
It is confusing (and very bad UI design) for ALL users, when parts in the - expectable - same user interface change places.
And it is a direct violation of the "Web Content Accessibility Guidelines"
=> "Make Web pages appear and operate in predictable ways"
https://www.w3.org/TR/WCAG21/#consistent-navigation
Screenshots, screen recording, code snippet
No response
Environment info
WP 6.1.1
with and without Gutenberg
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: