January 26, 2021

Accessibility Team Meeting Notes: December 4, 2020

Sponsored

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.

Nomination of the working groups’ referents

In previous meetings, it was proposed and agreed to create working groups inside the team to better address the various aspects of WordPress accessibility. Ideally, each team should have a referent; their role would be:

  • keep track of what the group is working on
  • report about it during weekly meetings
  • ask for the team’s help to solve specific issues

Some contributors already volunteered as referent for a working group:

The teams who still need a referent are:

  • editor
  • general
  • meta
  • themes

After some discussion, the team agreed that, until someone decide to volunteer, teams that don’t have a referent yet will start without one and will fill the role later.

Result of the extra bug-scrub focused on 5.7 release

On Tuesday, December 1st, an extra bug-scrub focused on preparing the 5.7 release took place: you can find the full transcript on the #accessibility Slack channel. @sabernhardt, who facilitated the bug scrub, reported quickly about the results.

  • Ticket #45925: the good-first-bug label was added and @danfarrow became the owner
  • Ticket #32510: needs some research and testing
  • Ticket #45141: needs testing from a regular keyboard user (@alexstine volunteered)
  • Ticket #42780: will need testing after an external library update
  • Ticket #49696: needs exploration

All contributors are invited to have a look at these tickets, add their thoughts and check if they can be solved in the next release

Open floor

@ryokuhi drove attention to a couple of topics that were raised the week before the meeting and that would benefit from some attention by accessibility contributors:

#meeting-notes

Sponsored