This meeting takes place every Friday at 14:00 UTC (currently 7:00am PT, 10: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.
List of Slack users to ping 10 minutes before the meeting:
@Ravi, @shaal, @Quynh, @yoroy, @sahil, @ckrina, @lauriii, @Regu.pl, @simohell, @AaronMcHale, @anmolgoyal74, @worldlinemine, @Pallavi Singh, @Gareth - (the_g_bomb), @mgifford
This list gets copied to the issue for the next meeting. If that has already happened, then go to that issue to add/remove yourself to/from the list.
Recording of this week's meeting: https://www.youtube.com/watch?v=2eIvoRG3GNE
Rough transcript of this week's meeting: Drupal Usability Meeting - 2026-09-11.txt
We discussed the following issue:
NR and RTBC issues marked Needs usability review.
The group is actively tracking progress on these issues:
- #2860419: [Meta] Appearance page is too long and confusing
- #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. - For an overall summary of the problem space see the videos in #3534039: Drupal Usability Meeting 2025-07-11 and #3535491: Drupal Usability Meeting 2025-07-18
- @AaronMcHale: Issue could use some guidance.
- #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
- #3262935: Link field validation constraints don't give enough detail
- #3619387: Indicate on forms sidebar toggle button that sidebar has child element errors
- #3618760: Tables can have too much horizontal whitespace
Remaining tasks
-
Add issue credits for the participants. -
Add the issue(s) we discussed to the issue summary and as related issues. -
Add a rough transcript. -
Add a link to the recording on YouTube. -
Comment on the issue(s) we discussed.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Drupal Usability Meeting - 2026-09-11.txt | 54.81 KB | benjifisher |
Comments
Comment #2
kentr commentedIf you have a chance, #3619387: Indicate on forms sidebar toggle button that sidebar has child element errors could use another look.
I don't think I can make the meeting, but I think I fixed the problem that @rkoller had last time with not seeing the error indicator. It looks like it was due to caching.
Comment #3
kentr commentedI'd like to propose #3604037: Indicate that grouping elements have child element errors for UX and a11y also.
Even though it's technically postponed, that's only until the direction becomes clearer.
I'm working on it behind the scenes and updated it today. I think it's in a state that would benefit from a UX review to help determine direction.
I've tested it on Edge and Safari locally, and partially in the Tugboat preview for the MR (excepting the standard details that requires the
form_testmodule, which I don't know how to install in Tugboat).Feel free to abort if you have any problems with it.
Comment #4
mgiffordI added two issues that came up from the accessibility side.
Comment #5
mgiffordComment #6
benjifisherComment #7
benjifisherComment #8
mgiffordSo we talked about #3619387: Indicate on forms sidebar toggle button that sidebar has child element errors how are ideas taken from the text transcript above and brought into the issue queue we talked about? Sorry, I really should come to more of these meetings.
Comment #9
kentr commented@mgifford,
I fixed at least one of them: The vertical alignment of the new error icon.
I also moved the red error border below the focus outline, which may take care of some of the focus outline discussion that was specifically related to this new error styling.
I'll add a comment with screenshots on #3604037: Indicate that grouping elements have child element errors for UX and a11y.
Comment #10
benjifisher@mgifford:
That is the responsibility of the people attending the meeting (and me, whether or not I attend). I am afraid we are not prompt enough about getting that done. It is one of the items listed under "Remaining tasks", and I do not mark one of these meeting issues as fixed until it gets done.
Comment #11
rkollerComment #12
benjifisher@kentr reviewed the recording and followed up on the issue: see the comments from 2026-09-22.