Drupal Usability Meeting 2023-09-01

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
• ✨ 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.
• 🐛 Password suggestions are hidden from screenreaders Active
• ✨ Provide Drupal root path on file system admin form Needs work
• 🐛 UX: Hide entity ID in autocomplete widget Needs work
• ✨ Allow hiding configured blocks in layout builder Needs work
• ✨ Add visibility control conditions to blocks within Layout Builder Needs work
• 🐛 Error message presented when a BrokenPostRequestException is fired on AJAX submission can be misleading Needs work
• 📌 Link field validation constraints don't give enough detail Needs work

Added a comment to the password suggestions are hidden issue: #3272325-11: Password suggestions are hidden from screenreaders → and another comment on the show/hide issue: #2293803-213: Replace confirm password field with show/hide functionality → .

In regards of the to be created issue about the password label two questions. First what would be the best component the issue should be filed against - the User system? Or would it be better to split the two things up because i've noticed while writing up it isn't explicitly clear to the user that in step 6 of the Drupal installer an actual account is created. It is sort of implied but not reflected in the microcopy.

The section is called site maintenance account (which is sort of an understatement since it is user 1) then username and password. it isn't articulated anywhere that this account is created with the credentials you choose here.

so i am wonder if it would make sense to create two issues. one for the installer covering the microcopy of the section title plus the labels of the username and password (and maybe the description) and one issue for the password label on the user profile pages?

benjifisher → credited Emma Horrell → .

benjifisher → credited lauriii → .

benjifisher → credited worldlinemine → .

Comments were left on both issues discussed in #4 📌 Drupal Usability Meeting 2023-09-01 Needs work , a transcript was added in #10 📌 Drupal Usability Meeting 2023-09-01 Needs work and the recording of the meeting added to the issue summary. The only thing left is the open question in #4 📌 Drupal Usability Meeting 2023-09-01 Needs work :

In regards of the to be created issue about the password label two questions. First what would be the best component the issue should be filed against - the User system? Or would it be better to split the two things up because i've noticed while writing up it isn't explicitly clear to the user that in step 6 of the Drupal installer an actual account is created. It is sort of implied but not reflected in the microcopy.

The section is called site maintenance account (which is sort of an understatement since it is user 1) then username and password. it isn't articulated anywhere that this account is created with the credentials you choose here.

so i am wonder if it would make sense to create two issues. one for the installer covering the microcopy of the section title plus the labels of the username and password (and maybe the description) and one issue for the password label on the user profile pages?

any thoughts on the open question in #11 📌 Drupal Usability Meeting 2023-09-01 Needs work ?

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