Accessibility Team Meeting Notes: January 18th

Meeting notes on Slack

Update on WP Campus Gutenberg Audit

Tenon LLC will conduct the accessibility audit of the Block Editor. It expects to take 4 weeks. The vendor will also be able to submit issues and possibly pull requests to the Gutenberg Github repository.

@bamadesigner and @bdeconinck are going to share an update of the process at WPCampus Online on January 31.

Audit expected timeline:

  • Wednesday, January 9: Project kickoff meeting
  • Thursday, January 31: Progress update at WPCampus Online
  • Late February: Audit report released

Update on automated testing projects

The team created a GitHub project to track ideas and progress on these projects. WordPress automated accessibility testing project.

These tasks are handled on #accessibility-testing slack channel.

An important pull request have recently been merged.

Future release(s) goals and triage/milestoning to help accessibility focused tickets to land in 5.1.x or 5.2

A lot of 5.1 accessibility tickets where moved to 5.2 or Future Release. The team will have to clean-up the awaiting review queue as soon as possible and then scrub the future release report.

@afercia and @audrasjb to scrub the awaiting review queue (even outside official bug-scrub sessions) to help in speeding up the process.

Block Editor updates and planning

Gutenberg 4.8 is going to land in WP 5.1, scheduled for February 21th. And one of the Gutenberg phase 2 focuses is porting Widgets to Blocks.

Also, there is a Research Team doing user testing. The plan is to expand that to more tester. Help is welcome in Research Team Slack channel: #research.

To substantially improve Gutenberg accessibility, usability testing sessions should include persons with accessibility needs:

  • screen reader user
  • speech input user
  • low vision user who uses magnification software
  • switch input user

@karmatosed to co-ordinate with the Research Team to get their input, and to publish a call for tester in Make/Design (cross-posted in Make/Accessibility).

Individual availability for the incoming months

For now, @afercia made a great effort on Gutenberg phase 1, to raise and follow GitHub issues and pull requests. The Accessibility Team needs more people with accessibility and React skills to help during Gutenberg phase 2.

  • @ryanshoover can help to recruit on specific issues.
  • @vossisboss and @samikeijonen are currently learning React.
  • @ryelle to help out with specific tasks she can be pointed to.

Efforts should be made to ease following and giving feedback on any new development that impacts accessibility, starting with creating properly labelled issues on GitHub.

The agenda item wasn’t fully covered during the meeting. The Accessibility Team will address this as the first item on the next meeting agenda.