Biweekly Team Meeting Time Update
The bi-weekly chat meeting time has changed to alternate Thursdays at 15:00 UTC, and the meeting calendar is also updated.
Bug Scrub Schedule for WordPress 6.9
The bug scrub schedule for WordPress 6.9 has been prepared for its upcoming release.
Updates from working groups
@joedolson reported that the admin redesign is officially no longer part of the 6.9 roadmap, so it will not be an immediate concern. This outcome was largely expected.
There will also not be a new default theme in this release cycle, which means design needs are relatively light.
@rianrietveld reported that the WP Knowledge Base is now ready for contributions 🎉. All accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) content from the current handbook has been copied into wpaccessibility.org, and placeholder pages have been created for new content. The How to contribute pages are finished, including information for contributors who don’t work with GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. A tracking issue is available with details on what still needs to be written.
Rian will write the web form documentation herself, as she has permission to use materials written for the Dutch government. Level Level, a Dutch WordPress agency specializing in accessibility, will conduct an official WCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.-EM audit on wpaccessibility.org at the beginning of November, with the goal of having all accessibility issues fixed by then. Contributors are encouraged to pick tasks from the projectboard Wp A11y Docs, but should only contribute on topics they know well, as AI is not yet reliable in accessibility.
For October, @rianrietveld will start writing content on web forms. @aialvi will work on migrating the current handbook to a new GitHub repository on github.com/wordpress. @joedolson and @1fixdotio will focus on the remaining issues in the website itself.
@joedolson reported that we are just under three weeks away from beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 of WordPress 6.9. There are 19 tickets still in the milestone, including five enhancements/features that need to be committed before beta. So far, 25 tickets have been completed for this milestone.
All enhancement and feature tickets were scrubbed on Tuesday and are in good shape, with most looking plausible to complete. However, a few are at risk. Ticket #48655 has had only minimal progress with some initial research, and ticket #49876 has seen no recent involvement from its contributor, meaning significant work is still needed.
Overall, the milestone is in good shape despite these concerns.
@joedolson reported that several major features are in progress that are important for accessibility, including the Icons block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., Tab block, Accordion block, and Block Commenting. He has reviewed the Icons block, Accordion block, and Block Commenting, but has not yet had time to review the Tabs block.
Feedback on the Accordion block and Block Commenting is in good shape. However, the Icons block has been shifting directions frequently, and accessibility feedback has not yet been addressed. Joe plans to review the Tabs block this week and will revisit the Icons block to confirm whether his earlier feedback is still relevant after the changes.
There may be additional issues, but these are the main updates at this stage.
@joedolson reported that testing on ticket #63895 is in progress, but more image sources are needed to ensure thorough results. In particular, images from major stock photo sites such as Shutterstock, Adobe Stock, Getty Images, iStock, and Alamy would be helpful. Contributors who have access to new images from these sources are encouraged to share them with @saj1ad, who is collecting them.
This ticket is not currently set for the 6.9 milestone but could be included if these issues are addressed in time.
@joedolson noted that @amberhinds is working on the theme accessibility ready guide. However, with WP Accessibility Day happening in less than two weeks, it is unlikely that there will be updates on this work until November.
@joedolson also mentioned that it may be difficult for him to attend the next meeting, since Accessibility Day will be ending just as the meeting begins.
NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments on an upcoming agenda.
Thank you, @krupajnanda for the pre-publish review.
Leave a Reply