Drupal Usability Meeting 2023-02-10

The group is actively tracking progress on:

• 🌱 [meta] Reorganize Block items in the administration menu Active

Issues brought forward from the previous meeting:

• ✨ [Meta] Appearance page is too long and confusing Active
• 📌 [PP-3] Figure out what to do with the install/uninstall modules page Postponed 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.
• 🐛 Placement of batch progress messages Active with notes:
  • #3322499: Drupal Usability Meeting 2022-11-25 → : We started looking at the issue but ran out of time.
• 🐛 Accessibility bugs with vertical tabs Needs work
• ✨ Allow media items to be edited in a modal when using the field widget Postponed 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.
• ✨ Allow blocks to be configured to show/hide on 200/403/404 response pages Fixed : see comment #3335028-6: Drupal Usability Meeting 2023-01-27 → for more details on what a review should address.
• 🐛 Password suggestions are hidden from screenreaders Active
• 🌱 [Policy] Remove tour module from core Fixed 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.

i have two more issues for the list. @smustgrave brought up 📌 Make core's structure descriptions more consistent Closed: won't fix in Slack today. it is about making the descriptions for child menu items for Core's structure menu item more consistent. i've already spotted a few nitpicks but i think it would be beneficial to have some word smithing in a group context. plus the suggested pattern should be applied to the (custom) block type menu item as well (ref 📌 Adjust the block terminology in Layout Builder to align with block and block_content changes Active ) which is currently missing in the proposed resolution. the second issue is 📌 Creating a new workspace should also switch to it Needs work . it is about when creating a new work space that it should be switched to it.

@xjm requested a review of 📌 Re-word "An illegal choice has been detected" message to remove legality suggestion Fixed .

I will probably be asleep during the meeting, but I summarized the change I recommend in comment #27 and the "why" is in $24 of #3265616-24: Re-word "An illegal choice has been detected" message to remove legality suggestion → .

I went to check what was part of 🐛 Accessibility bugs with vertical tabs Needs work was tagged for usability, as I recall taking a look of that in either accessibility or usability before and didn't see it being tagged "needs usability review" any more. Did we maybe finish with that so that accessibility remains or were some of use supposed to tag it for usability but didn't?

@smustgrave asked for a review of 🐛 Can't run tests if password contains / Needs work .

Discussed 📌 Re-word "An illegal choice has been detected" message to remove legality suggestion Fixed , I will update the issue.

I totally forgot to comment, but it was a pleasure to be part of that meeting.

I am adding a rough transcript, links to the issues we discussed, and issue credits.

Since the meeting, 📌 Re-word "An illegal choice has been detected" message to remove legality suggestion Fixed has already been fixed. I just added a comment to 🐛 Can't run tests if password contains / Needs work asking for clarification, and I removed the "Needs usability review" tag.

Todo: link to the recording.

I am adding a link to the recording: all done.

Automatically closed - issue fixed for 2 weeks with no activity.