Drupal Usability Meeting 2023-06-09

The group is actively tracking progress on:

• #3318110: [meta] Reorganize Block items in the administration menu

Issues brought forward from the previous meeting:

• #2860419: [Meta] Appearance page is too long and confusing
• #2035079: [PP-1] Figure out what to do with the install/uninstall modules page with notes:
  • #3307567: Drupal Usability Meeting 2022-09-09: started discussing the proposed options but ran out of time, possibly splitting the confirm form into its own issue (we may want to look at that for both modules and themes, standard pattern, consider implications of project browser), worth considering parity with Drush (and other extension/package managers).
  • #3310096: Drupal Usability Meeting 2022-09-23: @simohell presented the various proposals, but we again ran out of time to have a in-depth discussion, using the drop-button pattern on the module page for the existing links + Uninstall was suggested.
• #2569785: Placement of batch progress messages with notes:
  • #3322499: Drupal Usability Meeting 2022-11-25: We started looking at the issue but ran out of time.
• #2985168: [PP-1] Allow media items to be edited in a modal when using the field widget with notes:
  • @AaronMcHale: Issue could use some guidance.
    In comment #109 the issue was marked as postponed for needing input from UX, accessibility and media initiative. Apparently there are some outstanding UX/accessibility questions (but I'm not sure what they are). This was echoed in comment #111.
    Comment #144 is asking what is needed to move the issue along (the postponed state seems to be causing some delays/confusion as to how to proceed).
    Perhaps we can at least take a look at what the issue is doing and provide some recommendations/guidance on how it could be implemented.
• #3272325: Password suggestions are hidden from screenreaders
• #3325445: [Policy] Remove tour module from core with notes:
  • @xjm tagged for review and sign off from the usability group before it can go ahead, noting that Tour is seen as a usability module and the core committers were not able to reach a consensus.
• #3278377: Creating a new workspace should also switch to it
• #2704931: Provide Drupal root path on file system admin form
• #463106: Improve search settings help text
• #3309016: Add image preload option to help boost actual and perceived performance
• #2881892: UX: Hide entity ID in autocomplete widget
• #2980952: Wrong message on cancelling account with e-mail confirmation request with notes:
  • Reviewed at #3244123: Drupal Usability Meeting 2021-10-22 and we made a recommendation (in comment #13), but there was a good point made in comment #17 so in #18 I tagged it again for review.
• #3163197: Allow hiding configured blocks in layout builder
• #2916876: Add visibility control conditions to blocks within Layout Builder

#3247064: Error message presented when a BrokenPostRequestException is fired on AJAX submission can be misleading
#2619328: A required boolean field behaves differently depending on the widget
#2619328: A required boolean field behaves differently depending on the widget

Would be nice to see if these are indeed needing usability.

#3262935: Link field validation constraints don't give enough detail

Was the third I meant to add.

Some of these may not even need usability reviews but I don’t think I can make the call

FYI #3325445: [Policy] Remove tour module from core can be removed from the carry over group.

FYI #3325445: [Policy] Remove tour module from core can be removed from the carry over group.

Thanks for flagging, I've removed this from the list in #3365687: Drupal Usability Meeting 2023-06-16.

replaced the slack link with the direct link to the video on youtube to remove the gate

Added a comment to the issue based on todays discussion when we've revisited the issue a third time: #256287-88: Give roles a description value. I'll set this issue to fixed now since video and transcript are in place as well.