This meeting takes place every Friday at 14:00 UTC (currently 6:00am PT, 9:00am ET). See Time.is to see what that is in your timezone.

The meetings are held using Zoom, and a link is posted in the #ux Slack channel 10 minutes before the meeting. Agenda is first come, first serve and set by attendees. Use the Needs usability review issue tag for issues that need review and/or suggest issues in comments here.

ping:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina, @simohell, @gauravvv, @penyaskito

Go to the issue for the next meeting to add/remove yourself to/from the list.

Recording of this week's meeting: https://youtu.be/cUPrk2L4i2U

Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-02-10.txt

We discussed the following issue:

NR and RTBC issues marked Needs usability review.

Comments

AaronMcHale created an issue. See original summary.

aaronmchale’s picture

The group is actively tracking progress on:

Issues brought forward from the previous meeting:

rkoller’s picture

i have two more issues for the list. @smustgrave brought up #2985887: Make core's structure descriptions more consistent 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 #3318558: Adjust the block terminology in Layout Builder to align with block and block_content changes) which is currently missing in the proposed resolution. the second issue is #3278377: Creating a new workspace should also switch to it. it is about when creating a new work space that it should be switched to it.

benjifisher’s picture

Issue summary: View changes
benjifisher’s picture

xjm’s picture

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.

simohell’s picture

I went to check what was part of #3081500: Accessibility bugs with vertical tabs 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?

benjifisher’s picture

jidrone’s picture

schlaukopf’s picture

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

benjifisher’s picture

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

Since the meeting, #3265616: Re-word "An illegal choice has been detected" message to remove legality suggestion has already been fixed. I just added a comment to #3157304: PHPUnit database connection is not properly decoded asking for clarification, and I removed the "Needs usability review" tag.

Todo: link to the recording.

benjifisher’s picture

Issue summary: View changes
Status: Needs work » Fixed

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

Status: Fixed » Closed (fixed)

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