After the first Release Candidate of WordPress 5.7 was shipped on February 23, the Accessibility Team is looking into setting goals for the next release.
The 5.8 development cycle is yet to be defined: according to the original plan, WordPress 5.8 potential release date would be June 8, 2021, but a discussion about having four major releases in 2021 is ongoing and the release date is yet to be confirmed.
Nevertheless, the Accessibility Team wants to be ready when the release cycle will be announced, so this is a good time to start to collect ideas on possible team’s goals.
As such, we invite you to leave a comment below and propose which accessibility improvements you’d like to see shipped with WordPress 5.8. The discussion to identify major team goals will be held during the next weekly meeting, happening on Friday, March 5, 2021 at 16:00 UTC in the #accessibility channel in the Making WordPress Slack (requires registration).
During the 5.7 release cycle, the team decided to improve its workflow by creating seven working groups, focusing respectively on Design, Documentation, Media, Meta, General, Gutenberg, and Themes. The new team structure helped in moving issues faster, so we’re going to follow the same scheme also for WordPress 5.8. This means that the final choice about goals and targets will be in the hands of each working group, but you’re still invited to share your ideas, take part in the discussion and suggest what to prioritize.
If a certain goal won’t be selected for the 5.8 release, it can always be included in the list that will be created for the 5.9 release.
As the number of releases planned for 2021 is probably going to be reduced, the release cycle may be longer and some larger projects might make it into the list of the release goals. Anyway, if you think that solving a specific issue or adding a new feature may require work that spans over multiple releases, let us know so that we can try to coordinate and help you get the job done.
If you have any questions, feel free to drop them in the comments below or in the #accessibility channel on Slack.