Team meeting October 15, 2018

Transcript meeting in Slack

Agenda for the meeting

  • The future of a11y team: role and goals of the a11y team in the WordPress project, considering the current accessibility coding standards.
  • Decisional process in the a11y team.
  • Role of the a11y team reps.
  • Based on the approved reps role, nominees for the reps
  • The quarterly team updates for wordpress.org news https://wordpress.org/news/
  • Open floor

The future of a11y team: role and goals of the a11y team in the WordPress project, considering the current accessibility coding standards

At WordCamp US 2015 in Philadelphia the a11y team prepared a proposal for accessibility coding standards to be included in WordPress.

These can be found on the accessibility coding standard page. One of the main points is this:

All new or updated code released in WordPress must conform with the WCAG 2.0 guidelines at level AA. 

In the meeting we discussed that an accessibility coding standard is a little different than other coding standards.

  • Not everything can be measured or fixed by automated tools.
  • It involves design and pretty much every other part of the development process.
  • It needs experience outside of code on how users use tools like WordPress.

The team also discussed the wording of the a11y coding standard. Is there a reason to change “must” conform with the WCAG 2.0 guidelines to “should” conform with the WCAG 2.0 guidelines?

Accessibility team decided to keep the current wording  – All new or updated code released in WordPress must conform with the WCAG 2.0 guidelines. This raises a couple of questions.

  • If Gutenberg has issues that violates accessibility coding standard and guidelines, can the release date be changed before issues are solved? In short, the a11y team doesn’t have the power to make that decision.
  • What is the point of having standards if they’re not enforced? We can only recommend the a11y standards, and keep on working to reach that goal.

Decisional process in the a11y team

Meeting agendas, proposals, and decisions should (see what I did there) be published in this blog. We should also vote and document issues that do not have another place for discussion and decision making.

In short, let’s keep the same process as before.

Team representatives (reps)

Team reps is about

  • representing the team
  • speaking on behalf of the team
  • propose the agenda
  • run the meeting
  • write the meeting notes

We were hoping to get two to four volunteers so that the role can rotate every three months. Joe Dolson and JB Audras are interested to take on the team rep role. The team will decide on the new reps in the next meeting.

The quarterly team updates for wordpress.org news

In every three month there are short updates from teams in News site.

  •  What is the team’s one-sentence top priority right now (and what’s the ETA)?
  • What struggles is the team having?
  • What is one thing you are all proud of this quarter?

From this meeting there were no volunteers to write the summary but in general this can be done from summary meeting notes.

Open floor

We all agreed that Rian Rietveld is awesome. There is no way we can fit in her shoes. But hopefully we have shoes of our own.