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

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://youtu.be/Axkq3Cp4Ums

Rough transcript of this week's meeting: Drupal Usability Meeting - 2025-06-20.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.
CommentFileSizeAuthor
#3 Drupal Usability Meeting - 2025-06-20.txt30.07 KBbenjifisher

Comments

benjifisher created an issue. See original summary.

benjifisher credited rkoller.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Status: Active » Needs work
StatusFileSize
new Drupal Usability Meeting - 2025-06-20.txt30.07 KB
benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
rkoller’s picture

rkoller
he/him
Primary language German
Location Nürnberg, Germany
commented
Issue summary: View changes
Status: Needs work » Fixed

This week, instead of discussing a particular issue, we have taken a general look at the skipto module. I wanted to get some feedback about its general direction. After there is no issue to comment on I use the comment here to provide a summary. These are the three issues that got created:

#3531391: Make the skipTo module configurable on a per user basis
#3531379: Add a percentage suffix to the position option
#3531377: Remove main-only option from heading checkbox list and add radio buttons instead

The other detail about making div and nav lower case will be covered in the already existing #3516073: Improve the microcopy on the settings page. The rest of the raised issues will get issues upstream at https://github.com/skipto-landmarks-headings/page-script-5 :

  • If the focus is moved from the last available heading to the about skipto.js the focus outline remains on the last heading
  • the form of the landmark regions is hard to read due to the front loading of the landmark type and its potentially redundant nature - several landmark regions starting with for example Navigation: in a row
  • the indendation based on the heading level makes the heading list very hard to read - and the heading level is already communicated by the number

Status: Fixed » Closed (fixed)

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