WordPress.org

Make WordPress Core

Opened 4 months ago

Last modified 3 months ago

#53269 new defect (bug)

Reusable Blocks container is not accessible when it's the first top block

Reported by: Giorgio25b Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.7.2
Component: General Keywords: needs-patch 2nd-opinion reporter-feedback
Focuses: ui, accessibility, css Cc:

Description

The Reusable Blocks container is not accessible when it's the first top block and the mouse over won't highlight the wrapping container (.block-editor-block-contextual-toolbar-wrapper) and the block details:
https://griccardi.com/wordpress-images/block-editor-block-contextual-toolbar-wrapper.png.

Pressing the Tab key will highlight it, as well creating an empty <p> block as first element on top will allow for the mouse over.

Here a clumsy screen-cast to prove my point:
https://griccardi.com/wordpress-images/block-editor-block-contextual-toolbar-wrapper.mov

Not sure this helps, but this ticket here seems kind of related:
https://core.trac.wordpress.org/ticket/52918

Change History (6)

This ticket was mentioned in Slack in #accessibility by ryokuhi. View the logs.


4 months ago

#2 @ryokuhi
4 months ago

  • Keywords reporter-feedback added

Hello @Giorgio25b, and thanks for reporting this issue.
We checked this ticket today during the weekly Accessibility Team's bug-scrub, we have a few difficulties in understanding how we can help.
Could you please add the following details?

  • Do you use the Gutenberg plugin? If yes, which version?
  • Are you still able to reproduce the issue when using the default theme (Twenty Twenty-One) and after disabling all plugins (excluding Gutenberg, if installed)?
  • What should be the expected behaviour?
  • Can you add a list of instructions to follow to replicate the issue?

After we are able to reproduce the issue, we'll report it upstream to the Gutenberg GitHub repository, where it'll be solved.

Last edited 4 months ago by ryokuhi (previous) (diff)

This ticket was mentioned in Slack in #accessibility by ryokuhi. View the logs.


3 months ago

#4 @ryokuhi
3 months ago

Hello again, @Giorgio25b.
We're waiting for your input regarding this issue.
If you can get back to us with any additional information by next week, we'll decide how to push this issue forward, otherwise we'll close this ticket until we get extra information.

#5 @Giorgio25b
3 months ago

@ryokuhi Hello,
I just tested again on 2 different installations:
WP 5.7.2 with latest Gutenberg plugin version 10.8.2 installed and WP 5.8 Beta 01 with nightly build and Gutenberg plugin activated. Both environments are using WP2021 theme latest build.
I confirm the previous findings and issues, but with a slightly improved situation
I'll try to explain the expected behaviour and what is happening in reality:
On an empty new post if the first block is a re-usable block and the convert to regular block button is not pressed right away, it will not be possible to retrieve the convert to regular block btn anymore.

  • Create a reusable block: title+text or title+img
  • Create a new post
  • Add reusable block right away
  • Do NOT press convert to regular blocks
  • Add another block below
  • Try to scroll up and mouseover to retrieve the convert to regular blocks btn
  • Now, with latest Gutenberg plugin version, pressing tab on the keyboard from the post title activates the convert to regular blocks btn.
  • Mouseover still does not allow it.

I understand this is an edge scenario, but less skilled users (clients of mine) are not able to grasp an easy solution because they'd expect to just mouseover and get a consistent behaviuor regardless of the reusable block position within the post content.

Hope this helps!

This ticket was mentioned in Slack in #accessibility by ryokuhi. View the logs.


3 months ago

Note: See TracTickets for help on using tickets.