Change record: Drupal Accessibility office hours
This record explains the proposed revision of Drupal Accessibility (a11y) Office Hours. The page remains at its current URL and continues to describe the existing monthly meeting.
Summary
The existing page has the correct alternating UTC schedule, but it is difficult to scan and does not explain what participants should bring, what the meeting can provide, or where outcomes should be recorded. The revision keeps the page short, makes the Drupal Core calendar authoritative, and adds practical preparation and follow-up guidance.
What was retained
- Office hours take place on the third Thursday of each month.
- The meeting alternates between earlier and later times to include more time zones.
- The current Google Meet, agenda, meeting notes, and Drupal Core calendar links.
- The invitation to ask questions and have Drupal projects reviewed.
- The Drupal Slack
#accessibilitychannel as the asynchronous contact route.
What was updated or added
Verified UTC schedule
The schedule was checked against the public Drupal Core calendar on 28 July 2026. The current recurring events specify 15:00 UTC in even-numbered months and 20:00 UTC in odd-numbered months through December 2026. The revised page uses UTC and directs readers to the calendar for local-time conversion and exceptions.
Meeting purpose
The opening now identifies the work that can be brought to office hours: Drupal core, contributed projects, themes, documentation, and sites. It describes the meeting as a place for questions, barrier discussion, and review without promising a maintainer decision.
Preparation
The revision asks participants to add a linked, scoped agenda item before the meeting. It calls for a short problem description, the people and tasks affected, and the specific decision, test, or review required. This gives volunteers enough context to use the meeting productively.
Participation barriers and sensitive information
The page adds a route for raising barriers created by the meeting format. It also warns against placing credentials, personal information, or other sensitive material in the public agenda.
Durable project record
The revision states that decisions, findings, and test results belong in the relevant Drupal.org issue or project. Google Docs and Slack support the meeting, but they should not become the only record of work that affects the project.
What was removed or corrected
| Existing material | Change and reason |
|---|---|
| “Beginning” and “end” of the North America workday | Replaced with the exact UTC times and month groups. The old labels center one region and are less precise for an international community. |
| A request to ask in Slack to be added to “those calendars” | Removed. The public Drupal Core calendar is linked directly and already contains the recurring events. Slack remains available for questions and schedule coordination. |
| “Live and in real time” | Shortened. A live meeting is already real-time, so the phrase repeats the same information. |
| Speculation that additional office hours may be created for other time zones | Removed. It is not a current commitment or schedule. The page should describe the service that exists. |
| A general instruction to add agenda items | Expanded with the minimum information needed for useful review and a warning not to publish sensitive material. |
| The implication that office hours can provide an immediate project review outcome | Qualified. Office hours are volunteer support and do not replace issue review, testing, maintainer approval, or the Drupal.org project record. |
| The older link path for accessible contribution guidance | Updated to the current page under /docs/getting-started/accessibility/. |
Related index change
The parent Accessibility guide index still describes the meeting as “3rd Thursday of every month at 5pm PT” and mentions a trial time for July. That summary is stale and contradicts the alternating schedule.
Replace it with:
Monthly office hours for Drupal accessibility questions and project review, with alternating UTC meeting times.
What was not changed
The revision retains Google Meet and Google Docs because they are the tools currently used by the organizers. Assessing or replacing those platforms is a separate community process and is outside this documentation edit.