Yesterday we hold a meeting with the proposed agenda. The recap of the meeting is below and you can read the meeting transcript in the slack archives (a Slack account is required).
Weekly Updates
- Suspended themes they have security issues.
- In the past seven days
- 359 tickets were opened
- 387 tickets were closed:
- 347 tickets were made live.
- 13 new Themes were made live.
- 334 Theme updates were made live.
- 10 more were approved but are waiting to be made live.
- 39 tickets were not-approved.
- 1 ticket was closed-newer-version-uploaded.
WordCamp Asia 2020 Theme Review Team – How can we make it more fruitful?
The contributor day format is not suitable for reviews. The following suggestions could make it better:
- to work on existing tickets, for example, the tickets of the default themes.
- create a theme together or, better, create a block-based theme and document the issues found in the process, keeping notes to share with the Gutenberg team.
- ask the attendees what they want to do, as there will likely be a range of different experience levels + interests.
- take lots of breaks
- make sure every contributor gets some 1-1 time.
- make sure the wifi connection is stable.
Unfortunately, these ideas will not be used in WordCamp Asia, as it has been canceled due to fear of the spread of the disease caused by the new coronavirus COVID-19. They could be useful, however, for future WordCamps.
Open floor
We continued discussing the difficulty for authors to respect accessibility requirements and what we can do to help. At the moment, we have two requirements:
- Skip links, which are very easy to implement, and
- Keyboard navigation, which is more complicated, but where we have a lot of useful examples. In the post Planning for keyboard navigation, you can find help and resources to improve the implementation of this important feature.
In the meeting, we had a reminder that for accessibility the best thing to do is to use semantic HTML and don’t style much. Browsers are accessible by default but using too much CSS and, especially, JS can mess things up.
Finally, there was also a small discussion about custom controls not being accessible with the keyboard. As the status of the Customizer after the introduction of block-based themes is not known, this discussion seemed unfruitful for the moment.