Update on the WordPress Accessibility Day
The project kickoff meeting took place on Tuesday, December 17th. The meeting summary is available.
Proposed date for the next WordPress Accessibility Day meeting is Tuesday 14 January 2020 at 16:00 UTC in the #accessibility-events Slack channel. If you would like to propose another meeting date, please comment in the meeting summary post.
Update on the Gutenberg focus handling research work
Last month, the accessibility team made some testing on how Gutenberg handles focus on the various blocks. Thanks @enrique, @markdubois, @vicent, @gziolo, @audrasjb and @joedolson for their contribution.
@joedolson completed the focus handling tests & written up observations on it in a document.
Next steps:
- Publish the summary on Make/Accessibility
- Open related issues on Gutenberg GitHub repository
WordCamp Asia – contributor day
WordCamp Asia will host a contributor day and plan to set up an Accessibility table. All accessibility team members who plan to attend the WordCamp are welcome to volunteer to lead the table. Please comment below if you are interested.
Accessibility team goals for WordPress 5.4
@audrasjb: It would be great to define a primary focus for the team, for the next major release, WordPress 5.4. It’s not mandatory to have a main focus, but with 5.3 the primary goal of the team was the Admin CSS changes and it was quite effective.
@sabernhardt added one goal would be fixing more issues from the Gutenberg audit (maybe not primary focus though).
@nataliemac asked if it’s possible for accessible color schemes to be a focus for 5.4.
Accessible color schemes is a very nice project but it will probably have to wait for 5.5 in August, as 5.4 development must to be almost completed in 4 week. The idea is to plan major goals for 5.5 in the next few weeks and to focus on smaller tasks (Trac tickets and Gutenberg issues) for 5.4.
This Trac report can be used to pick up small focuses for 5.4. On Gutenberg side, that would be nice to address a couple of issues from the audit.