The Drupal Core Accessibility Topic Maintainers will be holding regular office hours, at least once a month. During this time, we will be available to answer questions and review projects, live and in real time, with you.

Note that this event represents office hours that are good for North America, though we tried to find a time that might work for the most international range of times possible. We will also try to set up additional office hours that are geared towards other timezones if this will be useful.

Agenda

Agenda is first come, first serve and set by attendees. Suggest topics or issues in the comments on this issue.

Inspiration:

Attendees

List of Slack users to ping 10 minutes before the meeting:
- @jmstair
- Nick M (ll66382)

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.

Wrap-Up

Recording/transcript/notes: Won't be included for this meeting

Issues discussed: See notes in comment

Remaining tasks

  • Add issue credits for the participants.
  • Add the issue(s) we discussed to the issue summary and as related issues.
  • Add recording/transcript/notes.
  • Comment on the issue(s) we discussed.

Comments

jmstair created an issue. See original summary.

jmstair’s picture

jmstair
She or They
commented
Parent issue: #3618581: Drupal Accessibility Office Hours 2026-08-20 » #3618579: Drupal Accessibility Office Hours
jmstair’s picture

jmstair
She or They
commented

Low priority: Discuss admin things for this meeting like:

  • Is the huddle working? Better than Hangout?
  • Can we get slackbot set up to send reminders like the UX group does?
  • Next steps for coordinating credits for documentation work
ll66382’s picture

ll66382 commented
Issue summary: View changes

Added me to notifiees.

jmstair’s picture

jmstair
She or They
commented
Issue summary: View changes

Attendees

  • Jeanette S
  • Kent R
  • Nick M
  • Mike G
  • John J

Action Items

  • Mike and Jeanette to meet with organizer for UX meetings to apply some of their processes to these accessibility office hours
  • Continue to test and collect feedback and ideas on the best tool(s) to use for the office hours meeting
  • Determine how to keep track of non-code contributions and document that approach

Notes

How to be helpful

  • Look for issues that need review and walk through the process from needs review to RTBC, often things are missing like screenshots and tests. Can script testing.
  • If you're a book learner, a great place to learn about contributing in general is drupal.org/community/contributor-guide/reference-information/quick-info
  • We just updated this accessibility-specific page: https://www.drupal.org/docs/getting-started/accessibility/contributing-t...
  • Look at older issues that are getting less movement
  • Test more with forced colors mode, dark mode, and mobile and add screenshots
  • Though there are a lot of issues with AI, it's possible to use to make the first step easier, especially for issues that are not getting attention. Making sure you're not putting burden on others to review code generated with AI and disclosing appropriately https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett...
  • Check issue queue and pick small things
  • Not necessarily pick one and see to the end. Can pick 4-5 issues and engage a little bit which may encourage others to engage with those.

Meeting structure moving forward

  • Question on recording or transcript for meetings
  • Raised accessibility concerns
  • Raised privacy concerns
  • Raised concerns on single-point-of-failure if using meeting platform "owned" by one participant
  • No decisions at this point, still considering options

Issues mentioned

  • Improve the accessibility of focus outlines - needs review #3618140
  • Indicate that grouping elements #2848507 - gitlab comments
  • Forms sidebar #3619127
  • Page title elipsis accessiblity issue #3623836
  • Labels for contextual links are redundant #3623711
  • Improve #3506333
  • Meta issue admin theme #3585823

Testing suite

  • Drupal going through transition
  • Historically used Nightwatch and PHP Unit
  • Nightwatch is being discontinued
  • Moving to Playwright but scripts haven't been converted yet
  • guidepup.dev - screen reader automation library for testing
  • playwright mcp - more flexibility in recording tests and pass along
  • Unit tests built into core
  • Should be building tests to validate that we're retesting fixed issues and not introducing regressions
  • CMS may use something else

Need to validate if Gin issues have been fixed in Drupal Admin Theme

  • Create a new ticket for Drupal Admin Theme if it's still an issue (and make sure the issues are linked)
  • If fixed in admin theme, comment on gin issue that it's fixed in the Drupal Admin Theme
jmstair’s picture

jmstair
She or They
commented
Status: Active » Fixed

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.