Accessibility Team Meeting Notes: August 21, 2020


These are the weekly notes for the Accessibility Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Vote to change the day and time of the team’s weekly meeting

Following a first round of voting to change the day and time of the team’s weekly meeting and the tie between moving the meeting to Tuesday, and keeping it on Friday, the team decided to hold a second poll to break the tie. The vote was closed at 17:30 UTC during the meeting and the results were:

  • Tuesday, 15:00 UTC: 42.9% of votes;
  • Friday, 15:00 UTC: 57.1% of votes.

As such, the team’s choice is to keep the meeting on the current day and time. A review of such decision can take place again in the future, but possibily not before six months.

Call for Team’s goals for the 5.6 release

You can find more details about this point in a self-contained post to be published soon on the Make website.

Request for collaboration on Gutenberg and Full Site Editing

@annezazu reached out to the channel asking for collaboration from the Accessibility Team on two projects.

Discussion about adding user-editable aria-labels to links in Gutenberg

The Team discussed an issue in the Gutenberg repository allowing users to add aria-labels to links. After a short discussion, the Team agreed that, while having multiple links and buttons with the same text can be harmful for users, using an aria-label attribute is almost surely not the best solution. @alexstine volunteered to sum up the Team’s position and to add a comment to the issue about aria-labels before closing it.

Discussion about communicating expanded/collapsed state in Gutenberg

Next, the team discussed another Gutenberg issue about the expanded/collapsed state of the “More options” button not being communicated to screen readers. Given that the bug was reported after testing on an iPod touch and while the team recognized that the screen reader expanded/collapsed state is not communicated in iOS, after a short discussion the team decided to ask for more information to the reporter, given that the actual implementation works as expected. @nrqsnchz volunteered to write a comment on the issue about expanded/collapsed state.

Discussion about adding a screen reader announcement to the last Gutenberg block in a list

Finally, the issue with the proposal to add an announcement for screen readers when a user reaches the last Gutenberg block in a list was introduced. Given the little time left for discussion, but the great impact this improvement could have on the UX for blind users, the Team decided to keep an eye on the issue and rediscuss it in the future.

#meeting-notes