[wp-trac] [WordPress Trac] #53785: Block Styles dropdown should use 'Default' instead of 'Not set'

WordPress Trac noreply at wordpress.org
Fri Jul 30 17:53:38 UTC 2021


#53785: Block Styles dropdown should use 'Default' instead of 'Not set'
--------------------------+------------------------------
 Reporter:  BjornW        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Editor        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  ui-copy
--------------------------+------------------------------
Changes (by ryokuhi):

 * focuses:  accessibility, ui-copy => ui-copy


Comment:

 Hello @BjornW,
 We checked this ticket today during the accessibility team's bug-scrub.

 We had a look at the problem, but we don't think it's an accessibility
 issue.
 The two controls you refer to are in fact different, so they don't have to
 follow [https://www.w3.org/WAI/WCAG21/quickref/#consistent-identification
 WCAG 3.2.4].
 The figures representing the different styles are used to select the style
 of the current block. The dropdown menu, on the other side, is used to set
 the style that will be used when the same block will be added again in the
 same post or page.
 You can check this if you try to add an image block (I'm using the Twenty
 Twenty-One default theme): this block has four styles, including a Default
 one, but in the dropdown you'll see five options, including both the "Not
 Set" option and the "Default" one. As the "Default" style is also a style,
 it's possibly different from "Not Set".

 The paragraph block doesn't have a "Default" style, so, when you add a new
 block style for this block, the "Default" style is automatically created
 (I haven't tested this, it's my guess).
 I see two possibilities.
 * The "Default" style should be also added to the dropdown menu (together
 with the "Not set" option).
 * The "Default" style and the "Not set" ones are duplicates, in which case
 this issue should be addressed also in other blocks.

 For now, as we don't consider this as an accessibility issue, I'm removing
 the accessibility focus from this ticket. Feel free to add it back in case
 you think that we should review it again.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53785#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list