On Thursday, October 16, 2025, 15:00 UTC, a team meeting started in #accessibility facilitated by @muddassirnasim. You can read the full transcript or see the meeting agenda.
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
Updates from working groups
Design
No Update
Documentation: @rianrietveld reported that Work on the WP Knowledge Base
- Rian started with (re)writing content about accessible web forms. @GaryJones and @Annelies Verhelst help with reviews. Nothing published yet, all in review at the moment.
- Vyshnavi Kurapati works on improving the search functionality of the website
- Jeffrey Lauwers will look at the design of the website, to give it a more professional and usable look and feel.
Migration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. handbook: @aialvi works on the migration of the current handbook to a new 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/ repo 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)-team-handbook on github.com/wordpress.
General
@joedolson We’re under a week 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. There are now 14 tickets in the milestone, three of which need to be completed before beta 1. 28 tickets have been completed. The three tickets remaining in the milestone are plausible, assuming I can find the time to get through them all.
Gutenberg
@joedolson reported that, 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. has been removed from 6.9, but the Accordion block has been stabilized and Block Comments (now Notes) is in the process of being stabilized. Both of these have been reviewed extensively, but don’t hesitate to keep re-checking. The Tabs Block is still undetermined, but will need additional accessibility review.
Media
@joedolson reported that There’s been good progress on #63895, but could really use more stock photo examples to test. Contact @saj1ad to provide images. (An update from Sajjad would be helpful here regarding whether he’s received any samples yet.)
Themes
@joedolson noted that looking towards having updates on accessibility-ready after WP Accessibility Day. @joedolson will follow up with @alh0319 to move this forward.
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, @joedolson for the pre-publish review.
#accessibility, #meeting-notes
