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:

Remaining tasks

  1. Add issue credits for the participants.
  2. Add the issue(s) we discussed to the issue summary and as related issues.
  3. Add a rough transcript.
  4. Add a link to the recording on YouTube.
  5. Comment on the issue(s) we discussed.

Comments

benjifisher created an issue. See original summary.

kentr’s picture

If 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.

kentr’s picture

I'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_test module, which I don't know how to install in Tugboat).

Feel free to abort if you have any problems with it.

mgifford’s picture

Issue summary: View changes

I added two issues that came up from the accessibility side.

mgifford’s picture

Issue summary: View changes
benjifisher’s picture

Issue summary: View changes
Status: Active » Needs work
Related issues: +#3604037: Indicate that grouping elements have child element errors for UX and a11y
benjifisher’s picture

Issue summary: View changes
StatusFileSize
new54.81 KB
mgifford’s picture

So 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.

kentr’s picture

@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.

benjifisher’s picture

@mgifford:

... how are ideas taken from the text transcript above and brought into the issue queue we talked about?

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.

rkoller’s picture

Issue summary: View changes
benjifisher’s picture

Issue summary: View changes
Status: Needs work » Fixed

@kentr reviewed the recording and followed up on the issue: see the comments from 2026-09-22.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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