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.
List of Slack users to ping 10 minutes before the meeting:
@worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Ravi, @shaal, @ckrina, @simohell, @Quynh, @yoroy, @Regu.pl, @Gareth - (the_g_bomb), @sahil, @Pallavi Singh
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=ZmHWUicSHAs
Rough transcript of this week's meeting: Drupal Usability Meeting - 2026-05-08.txt
We discussed the following issue:
- #3023777: datetime_range fields have confusing options for date type setting
- #2915899: [PP-1] Enable the Inline Form Errors module in the Standard install profile
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.
- #2704931: Provide Drupal root path on file system admin form
- #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
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 |
|---|---|---|---|
| #6 | Drupal Usability Meeting - 2026-05-08.txt | 46.23 KB | benjifisher |
Comments
Comment #2
rkollermoving over from the issue for last week: @quiteone raised #3023777: datetime_range fields have confusing options for date type setting for review on the #ux channel on the drupal slack.
Comment #3
rkoller@kentr raised #2915899: [PP-1] Enable the Inline Form Errors module in the Standard install profile over in the #ux channel in the drupal slack asking for an opinion in regard to enabling the inline form errors module in the standard install profile.
Comment #4
rkollerComment #5
rkolleradded a quick comment to the inline form errors issue: #2915899-27: [PP-1] Enable the Inline Form Errors module in the Standard install profile
Comment #6
benjifisherComment #7
benjifisherComment #8
rkollerComment #9
benjifisherI left a comment on #3023777: datetime_range fields have confusing options for date type setting.